cbs.log can't be fixed (and explorer keeps crashing)

The log file appears to be incomplete - it ends at POQ36, whereas a 64-bit machine should get to around 125 (or more).
Please reboot, and then upload a new copy of the CBS.log file
 
NoelDP,

Thank you for your prompt response, and sorry for my own inattentiveness.
Here, I will try to post the correct version, now:
 

Attachments

That's better :)
Code: 
 Line 200129: 2013-11-13 13:19:13, Info                  CSI    0000046b [SR] Repairing 1 components
 Line 200130: 2013-11-13 13:19:13, Info                  CSI    0000046c [SR] Beginning Verify and Repair transaction
 Line 200133: 2013-11-13 13:19:14, Info                  CSI    0000046e [SR] Cannot repair member file [l:22{11}]"PINTLGB.IMD" of Microsoft-Windows-IME-Simplified-Chinese-Core, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

appears to be the only problem found by SFC.

However, there are a number of other errors in the background CBS log, which indicate problems with the system Packages.

Please download and save the CheckSUR tool from System Update Readiness Tool fixes Windows Update errors
(you'll need to look in the details for Windows 7, downloading from the Microsoft Download Center)

Run it - The tool can take anywhere from 5 mins to a couple of hours to run (or 'Install') depending on how much it has to do, and may exit silently - it may appear to freeze for most of that time, but be patient.
The result is logged in the C:\Windows\Logs\CBS\CheckSUR.log file - and an archive …\checksur.persist.log file

Then zip the CheckSUR.log and upload it to your SkyDrive Public folder so I can take a look - post a link in your reply.
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top