New
#11
C:\Windows\Logs\CBS\Checksur.log and ..CheckSUR.persist.log are updated every time the CheckSUR tool is run.
C:\Windows\Logs\CBS\Checksur.log and ..CheckSUR.persist.log are updated every time the CheckSUR tool is run.
As far as can be surmised, I have reset Windows Update according to KB971058 on the MS support site you pointed to.
The commands regsvr32.exe *.dll (which I entered one at a time on a batch file) were half-successful. There were many dlls it could not load or register, and a ton of errors (about 40-50% of the files) came from that. This took a while to do, but not as long as it took to resolve the issue with NOD32 (licensing was messed up, advice from their troubleshooting page seemed to fix it). I am presently doing a scan of C: drive.
Also, "netsh reset winsock" didn't work. I didn't know Windows still used "winsock" in this day and age. :)
NoelDP: while Windows happily installed the Windows Update Readiness tool, I am confused: is this a program that the user actually runs? I can't find it anywhere on C: drive.
Thanks for pointing out the location, NoelDP. I found the log file, for your perusal.
I've seen worse :)
It'll take me a little while to produce the fix protocol - back with a Christmas present later :)
I've uploaded a file - packpk.zip - to my SkyDrive at https://skydrive.live.com/#cid=936736BB8FCEB92F&id=936736BB8FCEB92F%21526
Please download and save it.
Right-click on the downloaded file, and select Extract all…
Extract to the default location - which will create a new folder packpk in the same place.
Open this folder - there should be two folders inside it (Manifests, and Packages)
Copy the content of the Packages folder to the
C:\Windows\Temp\CheckSur\Servicing\Packages
And the content of the manifests folder (.manifest files) into this folder:
C:\Windows\Temp\CheckSur\Winsxs\Manifests
Now run the CheckSUR tool again (it may take a while)
Post the new CheckSUR.log file, and the CheckSUR.persist.log file.
Just run the download again :)
The only reason it says 'installing' is that the tool uses the TrustedInstaller service to do a lot of the work.
I have posted both CheckSUR files, and another output ZIP from SF_Diagnostic_Tool.exe, since there were a few more BSODs to make life interesting. I am beginning to suspect a corrupt HD.
There does seem to be creeping corruption present - the errors found in the new report weren't present in the initial one.
Perhaps you should run a CHKDSK C: /F before doing anything else, and see what the report is (it's a Wininit event in the Applications Event log)
Click on Start > All Programs > Accessories
Right-click on the Command Prompt entry
Select Run as Administrator and accept the UAC prompt - the Elevated Command Prompt window should pop up.
At the Command prompt, type
CHKDSK C: /F
and hit the Enter key.
You will be told that the drive is locked,
and the CHKDSK will run at he next boot - hit the Y key, and then reboot.
The CHKDSK will take a few hours depending on the size of the drive, so be patient!
After the CHKDSK has run, Windows should boot normally (possibly after a second auto-reboot) -
Then Open Event Viewer
navigate to Windows Logs\Application
Look there for a Wininit event - the details can be copied to your response.
What I got when I did that was, at boot, there was a quick screen indicating that CHKDSK is running, but then it quickly booted into Windows. The Event Viewer, looking under Windows Logs\Application tells of no such "wininit" event, up to 15 minutes before I actually booted. Just to be sure, I booted with chkdsk again the second time, but writing down the time (according to Windows) that I rebooted. Looking at the event logs over that time showed no record that I have invoked chkdsk /f c: