Author Topic: sfc /scannow cbs.log  (Read 15050 times)

0 Members and 1 Guest are viewing this topic.

Offline georgejmyersjr

  • Newbie
  • *
  • Join Date: Dec 2011
  • Posts: 3
  • Karma: 0
    • View Profile
sfc /scannow cbs.log
« on: December 12, 2011, 12:15:49 PM »
When I run the sfc program I'm told

Verification 100% complete.
Windows Resource Protection found corrupt files but was unable to fix some of them.
Details are included in the CBS.log windir\Logs\CBS\CBS.log For example C;\Windows\Logs\CBS\CBS.log

I'm not sure if, I do run the program occasionally before I tried Tweaking.com is from what. Could you find a way to fix it too? Also I'm having trouble with the cut and paste, for example from the sfc /scannow DOS window and suspect something blocking the ctrl-c ctrl-v operations though I can force them to work in "copy to note" in Opera or to redirect QuickPaste from ClipCahe Pro. Maybe there's a way to check that this important function, i.e. the clipboard, is intact and/or then repaired?

Offline Shane

  • Lead Developer - Coder
  • Administrator
  • Hero Member
  • *****
  • Join Date: Sep 2011
  • Posts: 9279
  • Location: USA
  • Karma: 138
  • "Knowledge should be shared not hidden."
    • View Profile
    • Tweaking.com
Re: sfc /scannow cbs.log
« Reply #1 on: December 12, 2011, 12:40:50 PM »
Quote
window and suspect something blocking the ctrl-c ctrl-v operations though

Are you able to use it in anything? If not then it sounds like the reg keys for it are messed up.

Quote
Details are included in the CBS.log windir\Logs\CBS\CBS.log For example C;\Windows\Logs\CBS\CBS.log

Did you check the log to see what files it couldn't repair?

Shane

Offline georgejmyersjr

  • Newbie
  • *
  • Join Date: Dec 2011
  • Posts: 3
  • Karma: 0
    • View Profile
Re: sfc /scannow cbs.log
« Reply #2 on: December 12, 2011, 01:14:09 PM »
I'm new to cbs.log and I think at the end of the long file
2011-12-12 14:59:13, Info                  CSI    00000199 [SR] Repairing 2 components
2011-12-12 14:59:13, Info                  CSI    0000019a [SR] Beginning Verify and Repair transaction
2011-12-12 14:59:13, Info                  CSI    0000019b Manifest hash for component [ml:280{140},l:180{90}]"x86_87319525ad25960a5a04b77a73d22b66_31bf3856ad364e35_6.1.7601.17658_none_3672aad1ab0d2714" does not match expected value.
Expected:{l:32 b:0060a94ae72d6d4ba687e01b28cbd12efde2a88a30eba5de04f138a8dfe626c9}
Found:{l:32 b:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855}.
2011-12-12 14:59:13, Info                  CSI    0000019c Unable to load manifest for component [ml:280{140},l:180{90}]"x86_87319525ad25960a5a04b77a73d22b66_31bf3856ad364e35_6.1.7601.17658_none_3672aad1ab0d2714"
2011-12-12 14:59:13, Info                  CSI    0000019d [SR] Cannot verify component files for 87319525ad25960a5a04b77a73d22b66, Version = 6.1.7601.17658, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
2011-12-12 14:59:13, Info                  CSI    0000019e [SR] Cannot repair member file [l:32{16}]"I386\lxkpsrd.dll" of prnlx00x.inf, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), 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
2011-12-12 14:59:13, Info                  CSI    0000019f [SR] Cannot repair member file [l:32{16}]"I386\lxkpsrd.dll" of prnlx00x.inf, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), 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
2011-12-12 14:59:13, Info                  CSI    000001a0 [SR] This component was referenced by [l:182{91}]"Microsoft-Windows-Printer-Drivers-Package~31bf3856ad364e35~x86~~6.1.7601.17514.INF_prnlx00x"
2011-12-12 14:59:13, Info                  CSI    000001a1 Repair results created:
POQ 77 starts:
 
POQ 77 ends.
2011-12-12 14:59:13, Info                  CSI    000001a2 [SR] Repair complete

Appears to be a printer driver file and a Intel cpu id file?

Offline Shane

  • Lead Developer - Coder
  • Administrator
  • Hero Member
  • *****
  • Join Date: Sep 2011
  • Posts: 9279
  • Location: USA
  • Karma: 138
  • "Knowledge should be shared not hidden."
    • View Profile
    • Tweaking.com
Re: sfc /scannow cbs.log
« Reply #3 on: December 12, 2011, 01:18:28 PM »
Looks minor. It only found 2 things. Looks to be drivers installed from windows updates. And it cant find the file again.

But again, looks to be minor :wink:

Shane

Offline georgejmyersjr

  • Newbie
  • *
  • Join Date: Dec 2011
  • Posts: 3
  • Karma: 0
    • View Profile
Re: sfc /scannow cbs.log
« Reply #4 on: December 12, 2011, 01:44:32 PM »
Thanks I don't have a Lexmark printer (Canon) and I read it might have been a virus in another scenario.

Offline Shane

  • Lead Developer - Coder
  • Administrator
  • Hero Member
  • *****
  • Join Date: Sep 2011
  • Posts: 9279
  • Location: USA
  • Karma: 138
  • "Knowledge should be shared not hidden."
    • View Profile
    • Tweaking.com
Re: sfc /scannow cbs.log
« Reply #5 on: December 12, 2011, 07:28:34 PM »
Haven't seen a virus hit the SFC before. But anything is possible :-)

To be safe run a tdsskiller.exe, combofix and malwarebytes scan :wink:

Shane