Okay, I have been losing my hair over this and would appreciate some help if possible. My issue is that the scannow command will always find errors when I run it if I update windows to 10586.3 (from a clean install of 10586). I am not sure if that has something to do with DISM using image 10.0.10586.0. Should that not be 10.0.10586.3? Anyways, running Dism /Online /Cleanup-Image /CheckHealth tells me its repairable. However, I am having issues making it use the source file (install.esd) to do so. aka "source files could not be found" I have used the following commands with zero luck; This while trying to use my usb install drive with drive letter J: Dism /Online /Cleanup-Image /RestoreHealth /Source:esd:J:\Sources\Install.esd:1 /limitaccess These with the install.esd file copied to my c drive. Dism /Online /Cleanup-Image /RestoreHealth /Source:esd:C:\install.esd:1 Dism /Online /Cleanup-Image /RestoreHealth /Source:esd:C:\install.esd:1 /limitaccess Any ideas? Does sfc even fail for you guys?
Mount the .WIM from an ISO first, and use the commands here Use the /RestoreHealth argument to repair the image. For example, to repair an offline image using a mounted image as a repair source, at a command prompt, type the following command: Dism /Image:C:\offline /Cleanup-Image /RestoreHealth /Source:c:\test\mount\windows Or to repair an online image using some of your own sources instead of Windows Update, type: Dism /Online /Cleanup-Image /RestoreHealth /Source:c:\test\mount\windows /LimitAccess Source https://technet.microsoft.com/en-GB/library/hh824869.aspx Mount .WIM https://technet.microsoft.com/en-GB/library/hh824814.aspx?f=255&MSPPError=-2147217396
Man, I just did a freakin clean install and its the freakin same. WTF! I don't understand what is going on. All I do in an offline install, install chipset, mei and NVidia drivers. I then reconnect to the web and run updates, with one always failing (Samsung printer driver 3) and the two that install are the .3 update (KB3105211) and flash (KB3103688). Nothing wrong with pc and original windows 10 passes sfc and so does win 8.1 Does it pass the scan on yours? Edit- this is also a brand new usb stick with a newly made installation
10 RTM did the same after a clean install, I run LTSB so I don't get this update, and mine passes fine Don't worry about it unless something is broken
Yeah I've wasted enough time with this heap of an os. Everything works fine and nothing in event logs so screw it. Many thanks for all the help
Most likely your install.esd is corrupt - it happened to me with 10586.0, I checked the hashes and they were different. I fixed it by re-downloading the install.esd, checking the hashes are correct and then using ESD Decrypter to turn it back into an install.wim so that DISM would see the source file. I then copied the install.wim to a folder on C drive called wim and ran the dism commmand; Code: Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:C:\wim\install.wim:1 /limitaccess I then ran sfc /scannow and it came up clean.
I downloaded the ISO from Microsoft, mounted it, adjusted the location and used the command above and it worked fine. Code: [==========================100.0%==========================] The restore operation completed successfully. The operation completed successfully. Thanks!
Nah it passes if i run it first thing after installation. Its after the update that it happens. Too lazy to worry about but thanks for the info
scannow still fails. Looking through the cbs log i just see duplicate ownership errors, nothing else but I may have missed something. If anyone is bored enough they can have a peek. I'll try the above eventually i guess https://onedrive.live.com/redir?resid=3159F11A0686D7D9!132
Download the required ISO from Microsoft. https://www.microsoft.com/en-us/software-download/techbench Mount it within Windows. Run command prompt (Admin) and enter Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:M:\sources\install.wim:1 /limitaccess change "M" to the drive letter that was assigned to the mounted ISO.
Bravo! :banana: This worked perfect on my son's PC after the recent update. Simple instructions that worked.