Solved Help with cbs.txt - I do not know what how to read this doc

[Spinach]

Would someone please help me decipher this please. I know I have some corrupted files that the system could not fix and I have following the instructions I found in another thread how to move the cbs.log onto the desktop in a txt doc. But I guess I just expected something to jump out off the screen at me and tell me "HEY, HERE, THIS IS THE PROBLEM!" LOL I have no idea what I'm looking at would some one please help me and tell me what the problem is and help how to fix it.


Thanks so much

View attachment 412434

 

[torchwood]

Hi Spinach,

All i can see are a problem with your Epson printer drivers

If your not having printer problems I'd just leave them be.
Otherwise Uninstall/reinstall the Printer and its drivers


Roy

 

[Spinach]

Well, I ran the sfc again and uploaded a screenshot of the the results and the cbs.log. It says that corrupt files were found but could not be fixed.

View attachment 412437

 

[Bree]

Well, I ran the sfc again and uploaded ... the cbs.log. It says that corrupt files were found but could not be fixed....

The CBS.log can be very confusing because it contains a lot more besides the System Repair results. The way to read just those relevant to your sfc /scannow is to filter it for the string "[SR]". See OPTION THREE in the SFC tutorial below.

Your cbs.log has a number of entries like this....

2020-09-13 04:11:50, Info                  CSI    000006bc [SR] Cannot repair member file [l:24{12}]"wiaep003.inf" of wiaep003.inf, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, file is missing

...all saying "[SR] Cannot repair member file <name of a file> in the store, file is missing". You'll need to manually replace the missing files, as described below.

• If SFC could not fix something, then run the command again to see if it may be able to the next time. Sometimes it may take running the sfc /scannow command 3 or more times to completely fix everything that it's able to.
• If not, then download and run the 32-bit (x86) or 64-bit (x64) System Update Readiness Tool for your same installed 32-bit or 64-bit Windows 7, restart the PC afterwards, and try the sfc /scannow command again.
• If still not, then try using OPTION ONE above to run the sfc /scannow command at boot.
• If still not, then you can attempt to run a System Restore using a restore point dated before the bad file occured to fix it. You may need to repeat doing a System Restore until you find a older restore point that may work.
• If still not, then you can use the steps in the TIP box in the OPTION THREE section below to manually replace the files that SFC could not fix if there are not to many fix.
• If there are to many files to manually fix, or you prefer not to use OPTION THREE below, then you could do a repair install without losing anything.

SFC /SCANNOW Command - System File Checker

 

[Spinach]

Alright! Thanks Bree you have been very helpful. I will start the process of repairing those files. I know its going to take me awhile so I'm going to label this has "solved".

Appreciate you people, you all have been very helpful.

 

[Snick]

Spinach

I private messaged you too!

If you run the below tool and post the CheckSUR.log that will be in the CBS folder that will appear on your desktop, I can/will help you with the repair files. I have 450,000+ in my repository.

The tool, if run again after you receive the repair files & place them correctly in your temp folder, installs them and retains security permissions. VERY IMPORTANT. You don't want to copy and paste them EVER!

Chasing down the cat/mum pairs and manifest files, i.e. determining the KB they came from is a real time consuming, frustrating, pain in the A** endeavor!

Download, and run from desktop please AutoSURTx64
Please post the CheckSUR.log from the CBS folder on your desktop when AutoSURTx64 completes.

Snick