A successful result using SFC doesn't guarantee there isn't corrupted component store data.
I would suggest running DISM /Online /Cleanup-Image /StartComponentCleanup prior to /RestoreHealth.
I will post more info when I get to my PC later.
Looking back on my notes, I see that I have only ever done DISM once. That was in June 2015, on Windows 8.1
I will be a bit rusty nowadays. :)
It is past my bedtime so I will sign off now and return tomorrow.
Thank you for your help.
I will try to clarify a few details about using SFC & dism. I'm confident that someone will correct anything that is not accurate.
The SFC utility compares the Windows System files on your PC to a copy stored in the Component store folder, namely C:\Windows\WinSxS. If there is a difference discovered, a corruption notification will be generated. The SFC utility will attempt to make certain that the Windows System files match the reference source from the Component store files.
Should the data stored in the component store be corrupt, SFC will not know any different and will use the corrupted data as a reference to perform the comparison/repair ergo, the SFC results are invalid, in this instance.
There are good reasons to always start with SFC before using the dism repair, although some users prefer to use dism first. Microsoft changed their directive a couple of years ago to suggest using dism first, then SFC. There are some useful related discussions and references in this thread.
What is the correct order of DISM and sfc commands to fix problems?
The dism /online will compare the Component store files on your PC to reference files at Microsoft. Should there be a content difference, a file corruption notification will be generated and depending on the Command line used, the utility will attempt to update the component store files.
As far as I know, that covers the basic functions. It should be apparent from this information that using the SFC utility by itself may not identify or correct all component store corruptions.
My preference is to run SFC first, followed by dism, provided there are no corruptions identified. Should SFC identify and repair corruptions, I would run dism until it shows no corruptions found and then SFC again, also until it runs and shows no corruptions.
I have seen on more than one occasion where using the dism utility will identify corruptions after SFC has found & corrected corruptions. This convinces me of the importance of always using both these utilities together.
Regardless of which order you choose, I would suggest to always run both & finish with SFC unless both utilities indicate no corruptions found (not the same as corruptions found & corrected).
There are several threads on Ten Forums and elsewhere that debate the logic of how to use these utilities. If anyone has further info to add, please speak up. We're all here to learn.
@W10 Tweaker
I ran these, in this order
DISM.exe /Online /Cleanup-Image /StartComponentCleanup
DISM.exe /Online /Cleanup-Image /RestoreHealth
sfc /scannow
No errors were found.
Thanks for your help. I will have to wait and see if the caps lock sound problen is fixed.
You're most welcome and good work, at least we know those checks are completed.
The Clean boot test is very easy provided you keep notes or screen captures showing which apps are enabled or disabled.
You may require to use your PC for awhile afterwards to determine if the problem is still happing or not.
Whenever suits your fancy, just post an update and I'll receive a notification. Cheers,
Michael
Quote