The Dism /Online /Cleanup-Image /RestoreHealth just found corrupt files. I may be right where I was.
Endless Corrupt Files and Troubleshooting.
Yesterday my SFC /Scannow command, run from Powershell Admin found corrupt files it was unable to fix. I expected The Dism /Online /Cleanup-Image /Restorehealth command to take care of it. Instead it reported "error 0x800f0906" and said it lacked the files to repair the problem.
I looked up error 0x800f0906 in a Dism command. It suggested a repair that started and stopped services, a
net stop wuauserv
cd %systemroot%\SoftwareDistribution
ren Download Download.old
net start wuauserv
net stop bits
net start bits
net stop cryptsvc
cd %systemroot%\system32
ren catroot2 catroot2old
net start cryptsvc
It also suggested Windows Update was malfunctioning and that I should fix it from The Troubleshooting screen. I did, and SFC /Scannow came up clean and Dism /Online /Cleanup-Image /RestoreHealth reported error code 0x800f081f instead.
I then used The Dism /Online /Cleanup-Image /StartComponentCleanup and The Dism /Online /Cleanup-Image /StartComponentCleanup /ResetBase Commands. I then used The Dism /Online /Cleanup-Image /ScanHealth Command and it reported "No component store corruption detected." I thought I was in the clear, but Dism /Online /Cleanup-Image /RestoreHealth keeps reporting it found and repaired files and The Troubleshooter keeps reporting it's fixed problems in Windows Update. Probably not the biggest deal in the Windows world but a little unsettling.
Windows for home | Previous Windows versions | Performance and system failures
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
100 answers
Sort by: Most helpful
-
Anonymous
2015-06-23T21:00:06+00:00 -
0x00000000 40,810 Reputation points
2015-06-23T20:14:28+00:00 One more voice in favor the fact that the ISO image for a "clean install" must have all users not retail product owners only
-
Anonymous
2015-06-23T20:11:02+00:00 It was a Seagate tool. I'm not sure what you guys have against ASC, but certain people have accused it of being too aggressive.
-
Anonymous
2015-06-23T20:09:45+00:00 I certainly did run the command right after sfc /SCANNOW in The Recovery Features' Command Prompt X: box.
-
Deleted
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more