CheckSUR file - CBS MUM Corrupt 0x800F0900

Page 3 of 6 FirstFirst 12345 ... LastLast

  1. Posts : 28
    Windows 7 Home Premium 64 bit
    Thread Starter
       #21

    Here is response

    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation. All rights reserved.
    C:\Users\Admin>
    C:\Users\Admin>DIR C:\Windows\Winsxs\Manifests\amd64_microsoft-windows-d..framew
    orks-usermode_31bf3856ad364e35_6.1.7601.17803_none_fb416b4f0bdbe260.manifest
    Volume in drive C has no label.
    Volume Serial Number is CACA-89AF
    Directory of C:\Windows\Winsxs\Manifests
    15/01/2013 13:32 83,575 amd64_microsoft-windows-d..frameworks-usermo
    de_31bf3856ad364e35_6.1.7601.17803_none_fb416b4f0bdbe260.manifest
    1 File(s) 83,575 bytes
    0 Dir(s) 422,941,413,376 bytes free
    C:\Users\Admin>ICACLS C:\Windows\Winsxs\Manifests\amd64_microsoft-windows-d..fra
    meworks-usermode_31bf3856ad364e35_6.1.7601.17803_none_fb416b4f0bdbe260.manifest
    C:\Windows\Winsxs\Manifests\amd64_microsoft-windows-d..frameworks-usermode_31bf3
    856ad364e35_6.1.7601.17803_none_fb416b4f0bdbe260.manifest NT SERVICE\TrustedInst
    allerF)
    NT AUTHORITY\SYSTEMR
    X)
    BUILTIN\Administrators
    RX)
    BUILTIN\UsersRX)
    Successfully processed 1 files; Failed processing 0 files
    C:\Users\Admin>ATTRIB C:\Windows\Winsxs\Manifests\amd64_microsoft-windows-d..fra
    meworks-usermode_31bf3856ad364e35_6.1.7601.17803_none_fb416b4f0bdbe260.manifest
    A C:\Windows\Winsxs\Manifests\amd64_microsoft-windows-d..frameworks-u
    sermode_31bf3856ad364e35_6.1.7601.17803_none_fb416b4f0bdbe260.manifest
    C:\Users\Admin>DIR C:\Windows\Winsxs\Backup\amd64_microsoft-windows-d..framework
    s-usermode_31bf3856ad364e35_6.1.7601.17803_none_fb416b4f0bdbe260.manifest
    Volume in drive C has no label.
    Volume Serial Number is CACA-89AF
    Directory of C:\Windows\Winsxs\Backup
    File Not Found
    C:\Users\Admin>ICACLS C:\Windows\Winsxs\Backup\amd64_microsoft-windows-d..framew
    orks-usermode_31bf3856ad364e35_6.1.7601.17803_none_fb416b4f0bdbe260.manifest
    C:\Windows\Winsxs\Backup\amd64_microsoft-windows-d..frameworks-usermode_31bf3856
    ad364e35_6.1.7601.17803_none_fb416b4f0bdbe260.manifest: The system cannot find t
    he file specified.
    Successfully processed 0 files; Failed processing 1 files
    C:\Users\Admin>ATTRIB C:\Windows\Winsxs\Backup\amd64_microsoft-windows-d..framew
    orks-usermode_31bf3856ad364e35_6.1.7601.17803_none_fb416b4f0bdbe260.manifest
    File not found - C:\Windows\Winsxs\Backup\amd64_microsoft-windows-d..frameworks-
    usermode_31bf3856ad364e35_6.1.7601.17803_none_fb416b4f0bdbe260.manifest
    C:\Users\Admin>
      My Computer


  2. Posts : 28
    Windows 7 Home Premium 64 bit
    Thread Starter
       #22

    The bit where it comes up with smileys shoud read:

    NT AUTHORITY\SYSTEM : (RX)
    BUILTIN\Administrators : (RX)
    BUILTIN\Users : (RX)
      My Computer


  3. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #23

    It's OK - I can read Smiley :)

    The manifest file is the correct size, at least - but the wrong date. Windows thinks it's corrupted and is attempting to restore it from a non-existent backup! (the question of why CheckSUR didn't spot it remains)
    I think we'll try replacing the file manually, and see what happens.....


    I've uploaded a file - claab.zip - to my SkyDrive at https://skydrive.live.com/#cid=936736BB8FCEB92F&id=936736BB8FCEB92F%21526
    Please download and save it.

    Right-click on the saved file and select Extract all...
    Change the target to C:\ and click on Extract
    This should create a folder C:\claab

    Close all windows (it would be a good idea to print these instructions!)
    Now reboot to the Repair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced Boot Menu, at the top of which should be the option 'Repair my Computer'
    Pick that
    You'll have to log in with your username and password.

    Pick the option to use a Command Prompt
    At the prompt type
    DIR C:\claab
    hit the enter key - if you get a 'Not Found' error try
    DIR D:\claab
    or
    DIR E:\claab


    The drive letter in use when you find the folder will need to be substituted (for<drive>) into the following command...

    XCOPY <drive>:\claab <drive>:\windows\winsxs /y /i /s /v /h

    run the command (it should take almost no time)and when the prompt returns, type
    EXIT
    and hit the Enter key to exit Command Prompt - reboot to Normal Mode Windows.

    Now run SFC /SCANNOW in an Elevated Command Prompt
    then reboot and upload the new CBS.log file to your SkyDrive Public folder, and post a new link




      My Computer


  4. Posts : 28
    Windows 7 Home Premium 64 bit
    Thread Starter
       #24

    OK - ran it again - the drive is D:\claab ....

    Attached is the new CBS.log file .... fingers-crossed!!
      My Computer


  5. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #25

    That doesn't seem to have worked
    Let's try another route....
    Please open a command prompt and run the following command

    COPY C:\claab\Manifests\*.* C:\Windows\Temp\CheckSUR\Winsxs\Manifests

    (You should see one file copied as a response)

    Then run a CheckSUR scan and post the results. (CheckSUR.log)
      My Computer


  6. Posts : 28
    Windows 7 Home Premium 64 bit
    Thread Starter
       #26

    Noel - sorry for the delay - I've been away with work .... just checking I'm not doing anything wrong - running checksur - means re-downloading the file from Microsoft and running (System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821) [November 2012])?
    Thanks
    Clare
      My Computer


  7. Posts : 28
    Windows 7 Home Premium 64 bit
    Thread Starter
       #27

    If so - have managed to run this successfully this time and the CheckSUR logs are attached.
      My Computer


  8. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #28

    Wrong!!


    Sorry about that - I didn't bother reviewing the thread before posting.

    What I should have said was simply to try running another SFC /SCANNOW and posting the new CBS.log file, since the CheckSUR managed to fix the only error it found.
      My Computer


  9. Posts : 28
    Windows 7 Home Premium 64 bit
    Thread Starter
       #29

    ok - just run this sfc /scannow - it ran much more quickly but still suggests it found some corrupt files/not fixed.

    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation. All rights reserved.
    C:\Users\Admin>sfc /scannow
    Beginning system scan. This process will take some time.
    Beginning verification phase of system scan.
    Verification 100% complete.
    Windows Resource Protection found corrupt files but was unable to fix some of th
    em.
    Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example
    C:\Windows\Logs\CBS\CBS.log
    C:\Users\Admin>
      My Computer


  10. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #30

    Interesting - SFC had to replace the main manifest file for the other affected files - so the detection may be off-whack.
    Please run (yet) another SFC /SCANNOW and post the new log
      My Computer


 
Page 3 of 6 FirstFirst 12345 ... 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 09:35.
Find Us