eddiez,
I would go ahead and run the restore health command, but if you want to check it first then use the /ScanHealth switch. FWIW, below is a list of the commonly used commands;
1.) Open an
elevated command prompt.
2.) In the elevated command prompt, copy and paste the command below that you want to use.
Available Switch Options:
/CheckHealth - This switch option only checks to see if a component corruption marker is already present in the registry. It is just a quick way to see if corruption currently exists, and to inform you if there is corruption. It
does not fix anything or create a log. This should be finished almost instantaneous.
/ScanHealth - This switch option
does not fix any corruption. It only checks for component store corruption and records that corruption to the log file. This is useful for only logging what, if any, corruption exists. This should take around 5-10 minutes to finish.
/RestoreHealth -
(recommended) This switch option checks for component store corruption, records the corruption to the log file, and
FIXES the image corruption using Windows Update. This should take around 10-15 minutes up to a few hours to finish depending on the level of corruption.
Dism /Online /Cleanup-Image /CheckHealth
Dism /Online /Cleanup-Image /ScanHealth
Dism /Online /Cleanup-Image /RestoreHealth
My experience has been that I could never get SFC clean until DISM was clean. Once DISM reports all is well then move back over to the SFC utility. Also it would help me if you attached the SFCFix.txt file that is generated when you run the SFCFix.exe utility. If you dont already have it you can get it
here.
