SFC/Corrupted Files

Page 1 of 4 123 ... LastLast

  1. Posts : 6,618
    W7x64 Pro, SuSe 12.1/** W7 x64 Pro, XP MCE
       #1

    SFC/Corrupted Files


    I ran sfc /scannow, and it said that it found some corrupted files that it could not repair. I went to the CBS.log to see what they are, but the log is so long that I don't know if I found all of them, but here is what I did find:

    Code:
     Found: {l:32 b:CSliVw9WHT8gOyhm0+PBSRLRE3LvS/IeW0laSkVna58=} Expected: {l:32 b:FM7Av19iX/g5qNebSmt8SsDLtwX9GXxrf/hhfGw+NP4=}
    2010-02-21 17:08:11, Info                  CSI    000002e6 [SR] Cannot repair member file [l:16{8}]"uDWM.dll" of Microsoft-Windows-DesktopWindowManager-uDWM, Version = 6.1.7600.16385, 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
    2010-02-21 17:08:11, Info                  CSI    000002e7 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-d..pwindowmanager-udwm_31bf3856ad364e35_6.1.7600.16385_none_e4880f65da28f3d0\uDWM.dll do not match actual file [l:16{8}]"uDWM.dll" :
      Found: {l:32 b:CSliVw9WHT8gOyhm0+PBSRLRE3LvS/IeW0laSkVna58=} Expected: {l:32 b:FM7Av19iX/g5qNebSmt8SsDLtwX9GXxrf/hhfGw+NP4=}
    2010-02-21 17:08:11, Info                  CSI    000002e8 [SR] Cannot repair member file [l:16{8}]"uDWM.dll" of Microsoft-Windows-DesktopWindowManager-uDWM, Version = 6.1.7600.16385, 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
    2010-02-21 17:08:11, Info                  CSI    000002e9 [SR] This component was referenced by [l:190{95}]"Microsoft-Windows-DesktopWindowManager-uDWM-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.uDWM"
    2010-02-21 17:08:11, Info                  CSI    000002ea Hashes for file member \??\C:\Windows\System32\uDWM.dll do not match actual file [l:16{8}]"uDWM.dll" :
      Found: {l:32 b:CSliVw9WHT8gOyhm0+PBSRLRE3LvS/IeW0laSkVna58=} Expected: {l:32 b:FM7Av19iX/g5qNebSmt8SsDLtwX9GXxrf/hhfGw+NP4=}
    2010-02-21 17:08:11, Info                  CSI    000002eb Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-d..pwindowmanager-udwm_31bf3856ad364e35_6.1.7600.16385_none_e4880f65da28f3d0\uDWM.dll do not match actual file [l:16{8}]"uDWM.dll" :
      Found: {l:32 b:CSliVw9WHT8gOyhm0+PBSRLRE3LvS/IeW0laSkVna58=} Expected: {l:32 b:FM7Av19iX/g5qNebSmt8SsDLtwX9GXxrf/hhfGw+NP4=}
    2010-02-21 17:08:11, Info                  CSI    000002ec [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:16{8}]"uDWM.dll"; source file in store is also corrupted
    The obvious question is how to fix them?
      My Computer


  2. Posts : 8,375
    W7 Ultimate x64/W10 Pro x64/W11 Pro Triple Boot - Main PC W7 Remote PC Micro ATX W7 Pro x64/W11 Pro
       #2

    Are you having any problems with Windows in general? The "System File Checker" command there won't fix everything but minor problems with a system file or two damaged or missing.

    For more involved problems with Windows a repair install or full fresh install may be required to correct the more severe problems. If this is an install just seen lately that went on incomplete a full a clean install would be a thought to clean things up. Or if you created a system image when 7 first went on you could restore that.
      My Computers


  3. whs
    Posts : 26,210
    Vista, Windows7, Mint Mate, Zorin, Windows 8
       #3

    Here is how you can deal with the CBS.log data in a more reasonable fashion: (an extract from my blog with credits to Brink who helped find the procedure)

    SFC stores the results in the CBS.log which you find in C:\Windows\Logs\CBS\CBS.log. This is a massive file of approximately 5MB and if you care to see it all, you must send CBS.log to one of your own folders or the desktop from where you can double click on it. It will then open with Notepad. Note: You cannot open it inside the CBS folder. You will get an Access denied message.
    But most likely you are only interested in the part that shows the corrupted files that were fixed – or not fixed. For that you need a significant data reduction. You do that as follows:
    Open another elevated Command Prompt and paste this command into it:

    findstr /c:"[SR]" %windir%\logs\cbs\cbs.log

    This will show all the files you want to see in the Command Prompt window.
    Since that window is not very practical for a detailed study, you want to paste the content into a Notepad, Wordpad or Word file.
    For that you right click on the Command Prompt window (any place is good) and click Select All. Then you right click anywhere in the window. Now this whole text is stored on the clipboard and you can paste it into a document file (e.g. Notepad) where you can analyze it.

    A word of warning: If you have tweaked your system and modified system files, the System File Checker may undo your tweaks.
      My Computer


  4. Posts : 6,618
    W7x64 Pro, SuSe 12.1/** W7 x64 Pro, XP MCE
    Thread Starter
       #4

    Night Hawk,

    Understood, but I'm not inclined to go so far as reinstalling the OS at the moment. I ran SFC as simply a step in diagnosing a problem I posted about with a BSOD here:

    https://www.sevenforums.com/crashes-d...f1000-sys.html
      My Computer


  5. Posts : 28,845
    Win 8 Release candidate 8400
       #5

    seekermeister said:
    I ran sfc /scannow, and it said that it found some corrupted files that it could not repair. I went to the CBS.log to see what they are, but the log is so long that I don't know if I found all of them, but here is what I did find:

    Code:
     Found: {l:32 b:CSliVw9WHT8gOyhm0+PBSRLRE3LvS/IeW0laSkVna58=} Expected: {l:32 b:FM7Av19iX/g5qNebSmt8SsDLtwX9GXxrf/hhfGw+NP4=}
    2010-02-21 17:08:11, Info                  CSI    000002e6 [SR] Cannot repair member file [l:16{8}]"uDWM.dll" of Microsoft-Windows-DesktopWindowManager-uDWM, Version = 6.1.7600.16385, 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
    2010-02-21 17:08:11, Info                  CSI    000002e7 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-d..pwindowmanager-udwm_31bf3856ad364e35_6.1.7600.16385_none_e4880f65da28f3d0\uDWM.dll do not match actual file [l:16{8}]"uDWM.dll" :
      Found: {l:32 b:CSliVw9WHT8gOyhm0+PBSRLRE3LvS/IeW0laSkVna58=} Expected: {l:32 b:FM7Av19iX/g5qNebSmt8SsDLtwX9GXxrf/hhfGw+NP4=}
    2010-02-21 17:08:11, Info                  CSI    000002e8 [SR] Cannot repair member file [l:16{8}]"uDWM.dll" of Microsoft-Windows-DesktopWindowManager-uDWM, Version = 6.1.7600.16385, 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
    2010-02-21 17:08:11, Info                  CSI    000002e9 [SR] This component was referenced by [l:190{95}]"Microsoft-Windows-DesktopWindowManager-uDWM-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.uDWM"
    2010-02-21 17:08:11, Info                  CSI    000002ea Hashes for file member \??\C:\Windows\System32\uDWM.dll do not match actual file [l:16{8}]"uDWM.dll" :
      Found: {l:32 b:CSliVw9WHT8gOyhm0+PBSRLRE3LvS/IeW0laSkVna58=} Expected: {l:32 b:FM7Av19iX/g5qNebSmt8SsDLtwX9GXxrf/hhfGw+NP4=}
    2010-02-21 17:08:11, Info                  CSI    000002eb Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-d..pwindowmanager-udwm_31bf3856ad364e35_6.1.7600.16385_none_e4880f65da28f3d0\uDWM.dll do not match actual file [l:16{8}]"uDWM.dll" :
      Found: {l:32 b:CSliVw9WHT8gOyhm0+PBSRLRE3LvS/IeW0laSkVna58=} Expected: {l:32 b:FM7Av19iX/g5qNebSmt8SsDLtwX9GXxrf/hhfGw+NP4=}
    2010-02-21 17:08:11, Info                  CSI    000002ec [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:16{8}]"uDWM.dll"; source file in store is also corrupted
    The obvious question is how to fix them?

    Repair install, or restore from backup
      My Computer


  6. Posts : 6,618
    W7x64 Pro, SuSe 12.1/** W7 x64 Pro, XP MCE
    Thread Starter
       #6

    whs,

    That interesting, because I didn't have to move the CBS.log anywhere to view it. That string did produce a much longer list that I posted, but if I'm reading it correctly the majority are items that it did repair. It appears that the unrepaired items are the same as I posted above.
      My Computer


  7. Posts : 6,618
    W7x64 Pro, SuSe 12.1/** W7 x64 Pro, XP MCE
    Thread Starter
       #7

    zigzag3143 said:
    Repair install, or restore from backup
    Okay, it may come to that, but how about just a System Restore? That would be a lot faster and easier for a procrastinating loafer.
      My Computer


  8. whs
    Posts : 26,210
    Vista, Windows7, Mint Mate, Zorin, Windows 8
       #8

    I didn't have to move the CBS.log anywhere to view it
    Hmm, interesting. I always had this "access denied" problem when I wanted to open it at it's original location. But on occasion I will try it on my new laptop.
      My Computer


  9. Posts : 28,845
    Win 8 Release candidate 8400
       #9

    seekermeister said:
    zigzag3143 said:
    Repair install, or restore from backup
    Okay, it may come to that, but how about just a System Restore? That would be a lot faster and easier for a procrastinating loafer.

    Lazy I know Im still running 7100 and it expires in a week. If you have a backup to restore from use it. You may not know when the problems started sneaking in.

    One way to find out is to look in event viewer.


    Let us know if you need help


    Ken
      My Computer


  10. Posts : 6,618
    W7x64 Pro, SuSe 12.1/** W7 x64 Pro, XP MCE
    Thread Starter
       #10

    zigzag3143 said:
    Lazy I know Im still running 7100 and it expires in a week. If you have a backup to restore from use it. You may not know when the problems started sneaking in.

    One way to find out is to look in event viewer.


    Let us know if you need help


    Ken
    If this is some kind of creeping crud, it might be in the backup images also. I have found the Event Viewer somewhat clumsy with the changes since XP, but I'll try anyway.
      My Computer


 
Page 1 of 4 123 ... LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 00:47.
Find Us