Windows 7 CBS.log corrupted file

[DeathScourge]

Hi, I found this website yesterday due to this article( <--linked), and I am experiencing similar issues to dee_can. I tried to follow the similar instructions to zip my cbs log file, but I also am attaching everything that was included in the log folder. Hopefully this will not be necessary, but one can never be too sure.
I ran CMD as Administrator and performed the "sfc /scannow" command. The log file was the only problem that showed up, and the only file that could not be repaired. I routinely run virus checks and removed one recently. Not sure If that was the result of the initial corrupted file, but hopefully we can get this resolved.

Here are the attached zip files for review. I believe I saw errors, but I don't to risk making things worse than they already are. Like dee_can said "Please let me know if there is any problem with the files I've attached". I am extremely appreciative for your efforts. Sorry for bringing this issue to you and also a Major Thank You for taking up this task.:thumbsup2:

 

[niemiro]

Hello, and welcome to Sysnative :)

Please download and install the System Update Readiness Tool: What is the System Update Readiness Tool?

Save it to a conveient location so we can use it again later - save you a second download :)

Please be patient, it can take an hour or longer for it to complete, but you can use the computer whilst it is running.

Finally, please upload C:\Windows\Logs\CBS\CheckSUR.persist.log

Thank you!

Richard

 

[DeathScourge]

Thank You Richard:grin1:,
I usually dwell at Majorgeeks, but they didn't really seem to have any subjects relating to what I have exactly. Plus your site has helped me before in some issues, but I never really needed to make an account in the past. I should have made an account sooner. Again, thanks.
I just finished installing the System Update Readiness Tool.

Here is the attached CheckSUR.persist.log also followed with the CheckSUR.log:

 

[tom982]

Hi DeathScourge,

I'm just popping in quickly whilst Richard is offline so we can speed things up for you. Looking at your CheckSUR log, it appears that the tool never finished:

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.21645
Package Version 18.0
2013-04-17 16:06

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs
(f)    CBS MUM Corrupt    0x00000000    servicing\Packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum        Expected file name Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~neutral~~10.2.9200.16437.mum does not match the actual file name
(f)    CBS MUM Corrupt    0x00000000    servicing\Packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum        Expected file name Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~neutral~~10.2.9200.16437.mum does not match the actual file name

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store
(f)    CSI Payload File Missing    0x00000000    csc.sys    x86_microsoft-windows-offlinefiles-core_31bf3856ad364e35_6.1.7601.17514_none_a04fb2d2ba296321

Did you cancel it, or did it fail? If you cancelled it can you try running it again please but persevere until it finishes this time, it can take up to a few hours to complete so please be patient, it all depends on what state your computer is in.

Tom

 

[DeathScourge]

There was a power outage when It was running last time, and then when I tried to run it again, then the computer blue-screened.

Afterwards, I ran a Virus scan, and then a malware scan. A Trojan was detected and removed, and I immediately restarted the system. Immediately I repeated the scans afterwards(Everything was clean on the second run).
After that was done, I then ran the sfc /Scannow, and in hopes of nothing gone wrong earlier, that's when I ran into the cbs.log file corruption.

Oh and before contacting you guys earlier today, I ran Error-checking in the properties of the C: partition with "Automatically fix file system errors" followed with "Scan for and attempt recovery of bad sectors". It finished and then rebooted. Immediately after the reboot, I ran the sfc /scannow again afterwards and ran into the cbs.log corrupt file again.




EDIT:
Are you referring to the update readiness tool check.sur after the installation? I went to add the previous check.sur before the installation.

Also, I have not reset the computer as of yet. If need be, I will do so now.

 

[DeathScourge]

Reset my pc just in case the update readiness tool helped change anything in particular. I did undergo an update while that was loading, so hopefully that helps.

 

[niemiro]

Hello :)

Unfortunately, you have many file corruptions. This could indicate a hardware failure, unfortunately. I would like to test for it.

It is imperative that you backup all important data before proceeding. Do not proceed until everything is backed up, and you should ask me if you need any help with this.

If the hard disk is close to death, very occasionally, running a diagnostic scan will push it over the brink. This is why you must backup all data before proceeding.

Please carefully follow these instructions: SeaTools for DOS tutorial

to run Seatools for DOS. Run a Short test and a Long test.

If you have any problems or questions, please do not hesitate to ask :)

Richard

 

[DeathScourge]

sorry, I didn't mean to be away for so long. work has been tying me up. I tried running the sea tools and I am having a bit of a problem. should I try the DOS if I can't get the image to burn on the CD?
edit. typo

 

[DeathScourge]

Sorry for the double post. I managed to get the seatools to run. I ran the short test as well the long test. both have passed.

 

[Belmondo]

Hi, I found this website yesterday due to this article( <--linked), and I am experiencing similar issues to dee_can. I tried to follow the similar instructions to zip my cbs log file, but I also am attaching everything that was included in the log folder. Hopefully this will not be necessary, but one can never be too sure.
I ran CMD as Administrator and performed the "sfc /scannow" command. The log file was the only problem that showed up, and the only file that could not be repaired. I routinely run virus checks and removed one recently. Not sure If that was the result of the initial corrupted file, but hopefully we can get this resolved.

Here are the attached zip files for review. I believe I saw errors, but I don't to risk making things worse than they already are. Like dee_can said "Please let me know if there is any problem with the files I've attached". I am extremely appreciative for your efforts. Sorry for bringing this issue to you and also a Major Thank You for taking up this task.:thumbsup2:

Thank you for your the big help! i like to know how to install it manually can i drag and drop CBS.Log file can you please help me, step by step instruction.... thank you very much! :wave: