Don't see how this was even possible. Never would have even known since its been running great if I did not run this particular command I am going to mention. I am hearing the latest Windows Updates. Specifically optional ones are causing this problem for people. Before doing a system image backup for testing purposes with in Windows 8.1 I was advised to run the following Dism /Online /Cleanup-Image /ScanHealth after it finished. It came up with the component store is repairable. Huh? So, I ran Dism /Online /Cleanup-Image /RestoreHealth and it fixed it. I followed up with a sfc /scannow and it fixed some files. Both now report 100% clean with no errors. Is this and was it a cause for concern? Even though when using google. Its pointing to many people having this issue with Windows Updates being the cause. A particular one can cause it apparently. I cant remember off hand which one. I also have another 8.1 pc with the same issue. But, that one I cannot get it to repair. The machine has always run fine though and continues to do so. Not sure what to do.
When running the Dism /Online /Cleanup-Image /RestoreHealth I get the error 0x800f0906 I tried the following fix. It still would not work.
http://www.thewindowsclub.com/repair-corrupt-windows-image-error-0x800f0906
**EDIT**
False positive. Damn MS!!! http://www.infoworld.com/article/2926179/microsoft-windows/microsoft-confirms-patch-kb-3022345-breaks-sfc-scannow.html
That solves the problem for my machine that has that patch installed. Now I just look at the other machine and it does not have that patch installed. So, something else going on I suppose with that error?
↧