Hmmm, doesn't seem very smooth. I tried with CheckHealth. That was fine. Came back in a few seconds with no problems found. So I tried ScanHealth. After a couple of minutes it indicated 20% done. That was it. No further update. I let it run about 10 more minutes. Showed CPU Memory and Disk about 50% busy. Windows Module Installer was using most of the CPU doing something. But nothing happens. So I killed it. Seems like I should just leave it alone.
It's difficult to leave jobs running for that amount of time. Too often I have to pack up the Laptop and leave on short notice.
But I doubt my system is hosed this early on. Ignorance may be bliss in this case.
Windows 8.1 Pro with Media Center
Intel (R) Core(TM) i7 CPU 920 @ 2.67GHz 2.67GHz
6 GB Ram
64 bit Operating System, x64 based processor
2 Hard drives with 500 as primary
NVIDIA GeFrorce GTX 760 - up to date software in all respects
Kaspersky Pure 3.0 220.127.116.11.2.558 - up to date in all respects
Driver Reviver -to make sure all drivers are current - checked weekly
All Windows Updates are installed and up to date with the exception of BING which I hide and do not install on purpose, and an optional update dealing with the Marvell Raid controller dated 3 -7-2013 which I don't want to update because I don't use RAID with my hard drives.
This is an 2009 Alienware Area-51 x58 desktop which originally came with Windows Vista Home Premium. The Asus P6T Deluxe motherboard and DDR3 133 MHZ memory are about the only original hardware that the system came with. The hard drives, video card, DVD Burner, Hauppage Dual tuner TV card, and OS are all additions/replacements/upgrades over the last 4-ish years.
When I first installed Windows 8.0 Pro within a month of its release I remember after install having a problem installing one of the Windows Updates . . . I don't remember the exact K#, I remember researching it at the time and it seemed quite a few people were having problems of a similar sort with updates that wouldn't install correctly. Anyway . . . I have been trying to troubleshoot and fix this issue since approximately that same time. Not sure if mentioning that fact will even help you.
Every time I reboot the system . . . if I run DISM /Online /Cleanup-Image /RestoreHealth I get the response "The restore operation completed successfully. The component store corruption was repaired." "The operation completed successfully". If I then run SFC /Scannow the result is "Windows Resource Protection did not find any integrity violations". If it is possible please review the copy and pasted info from CBS Log file zipped and tell me if you see any obvious signs that would explain why this recurring corruption occurs.
Hello ChiefMMII, and welcome to Eight Forums.
The "The restore operation completed successfully. The component store corruption was repaired." "The operation completed successfully". message is just a generic message. You will see it every time you run the command below, and doesn't mean that you have any corruption.
Dism /Online /Cleanup-Image /RestoreHealth
If you like, use the command below to check and see if you have any corruption or not instead.
Dism /Online /Cleanup-Image /CheckHealth
Hope this helps,
I'm feeling quite ignorant (in Webster's dictionary definition) right about now . . . I did not know that the response I was getting using "/RestoreHealth" was a default response and not an actual problem response. I did run, as you suggested, /CheckHealth and in fact as you probably suspected received the response "No component store corruption detected".
Thank you for your prompt and accurate response. I'll chalk that up as a good thing . . . I learned something new today, LOL.
You're most welcome ChiefMMII. Don't worry about it. It's a new feature that everyone is getting used to.
The DISM thing showed no error anywhere.
But Repair-WindowsImage -Online -CheckHealth gives error:
Repair-WindowsImage : DismInitialize failed. Error code = 0xc0040009
At line:1 char:1
+ Repair-WindowsImage -Online -CheckHealth
+ CategoryInfo : NotSpecified: ( [Repair-WindowsImage], COMException
+ FullyQualifiedErrorId : Microsoft.Dism.Commands.RepairWindowsImageCommand
Any idea anyone?