CheckSUR file - CBS MUM Corrupt 0x800F0900

Page 1 of 6 123 ... LastLast

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

    CheckSUR file - CBS MUM Corrupt 0x800F0900


    Hi - am new to the forum and am also not very technical but wondered if someone can help.

    I have two problems with my son's laptop running Windows 7 Home Premium 64 bit and not sure if they are both related.

    1. After installing some updates yesterday - he is no longer able to log on as his user - it brings up an error - "unabled to access Group Policy..." and then logs him off. I can log on as admin but it brings up a warning message.

    2. Secondly there is one remaining update that will not install. Brings error code 800B0100. I have reinstalled the System Update manager tool but no change. The update that is trying to be installed is KB2685813.

    The Checksur file says:


    =================================
    Checking System Update Readiness.
    Binary Version 6.1.7601.21645
    Package Version 17.0
    2013-01-13 19:38
    Checking Windows Servicing Packages
    Checking Package Manifests and Catalogs
    (f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_1_for_KB2685813~31bf3856ad364e35~amd64~~6.1.1.11.mum Line 1:
    (f) CBS Catalog Corrupt 0x800B0100 servicing\Packages\Package_1_for_KB2685813~31bf3856ad364e35~amd64~~6.1.1.11.cat
    (f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_8_for_KB2685813~31bf3856ad364e35~amd64~~6.1.1.11.mum Line 1:
    (f) CBS Catalog Corrupt 0x800B0100 servicing\Packages\Package_8_for_KB2685813~31bf3856ad364e35~amd64~~6.1.1.11.cat
    (f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_for_KB2685813_SP1~31bf3856ad364e35~amd64~~6.1.1.11.mum Line 1:
    (f) CBS Catalog Corrupt 0x800B0100 servicing\Packages\Package_for_KB2685813_SP1~31bf3856ad364e35~amd64~~6.1.1.11.cat
    (f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_for_KB2685813~31bf3856ad364e35~amd64~~6.1.1.11.mum Line 1:
    (f) CBS Catalog Corrupt 0x800B0100 servicing\Packages\Package_for_KB2685813~31bf3856ad364e35~amd64~~6.1.1.11.cat
    Checking Package Watchlist
    Checking Component Watchlist
    Checking Packages
    Checking Component Store
    (f) CSI Manifest All Zeros 0x00000000 winsxs\Manifests\amd64_microsoft-windows-d..-usermode.resources_31bf3856ad364e35_6.1.7601.17803_en-us_251461586e43c0e3.manifest amd64_microsoft-windows-d..-usermode.resources_31bf3856ad364e35_6.1.7601.17803_en-us_251461586e43c0e3
    (f) CSI Manifest All Zeros 0x00000000 winsxs\Manifests\amd64_microsoft-windows-d..-usermode.resources_31bf3856ad364e35_6.1.7601.22004_en-us_259ed68f8760ad46.manifest amd64_microsoft-windows-d..-usermode.resources_31bf3856ad364e35_6.1.7601.22004_en-us_259ed68f8760ad46
    (f) CSI Manifest All Zeros 0x00000000 winsxs\Manifests\amd64_microsoft-windows-d..frameworks-usermode_31bf3856ad364e35_6.1.7601.17803_none_fb416b4f0bdbe260.manifest amd64_microsoft-windows-d..frameworks-usermode_31bf3856ad364e35_6.1.7601.17803_none_fb416b4f0bdbe260
    (f) CSI Manifest All Zeros 0x00000000 winsxs\Manifests\amd64_microsoft-windows-d..frameworks-usermode_31bf3856ad364e35_6.1.7601.22004_none_fbcbe08624f8cec3.manifest amd64_microsoft-windows-d..frameworks-usermode_31bf3856ad364e35_6.1.7601.22004_none_fbcbe08624f8cec3
    Summary:
    Seconds executed: 483
    Found 12 errors
    CSI Manifest All Zeros Total count: 4
    CBS MUM Corrupt Total count: 4
    CBS Catalog Corrupt Total count: 4
    Unavailable repair files:
    winsxs\manifests\amd64_microsoft-windows-d..-usermode.resources_31bf3856ad364e35_6.1.7601.17803_en-us_251461586e43c0e3.manifest
    winsxs\manifests\amd64_microsoft-windows-d..-usermode.resources_31bf3856ad364e35_6.1.7601.22004_en-us_259ed68f8760ad46.manifest
    winsxs\manifests\amd64_microsoft-windows-d..frameworks-usermode_31bf3856ad364e35_6.1.7601.17803_none_fb416b4f0bdbe260.manifest
    winsxs\manifests\amd64_microsoft-windows-d..frameworks-usermode_31bf3856ad364e35_6.1.7601.22004_none_fbcbe08624f8cec3.manifest
    servicing\packages\Package_1_for_KB2685813~31bf3856ad364e35~amd64~~6.1.1.11.mum
    servicing\packages\Package_1_for_KB2685813~31bf3856ad364e35~amd64~~6.1.1.11.mum
    servicing\packages\Package_8_for_KB2685813~31bf3856ad364e35~amd64~~6.1.1.11.mum
    servicing\packages\Package_8_for_KB2685813~31bf3856ad364e35~amd64~~6.1.1.11.mum
    servicing\packages\Package_for_KB2685813_SP1~31bf3856ad364e35~amd64~~6.1.1.11.mum
    servicing\packages\Package_for_KB2685813_SP1~31bf3856ad364e35~amd64~~6.1.1.11.mum
    servicing\packages\Package_for_KB2685813~31bf3856ad364e35~amd64~~6.1.1.11.mum
    servicing\packages\Package_for_KB2685813~31bf3856ad364e35~amd64~~6.1.1.11.mum
    servicing\packages\Package_1_for_KB2685813~31bf3856ad364e35~amd64~~6.1.1.11.cat
    servicing\packages\Package_1_for_KB2685813~31bf3856ad364e35~amd64~~6.1.1.11.cat
    servicing\packages\Package_8_for_KB2685813~31bf3856ad364e35~amd64~~6.1.1.11.cat
    servicing\packages\Package_8_for_KB2685813~31bf3856ad364e35~amd64~~6.1.1.11.cat
    servicing\packages\Package_for_KB2685813_SP1~31bf3856ad364e35~amd64~~6.1.1.11.cat
    servicing\packages\Package_for_KB2685813_SP1~31bf3856ad364e35~amd64~~6.1.1.11.cat
    servicing\packages\Package_for_KB2685813~31bf3856ad364e35~amd64~~6.1.1.11.cat
    servicing\packages\Package_for_KB2685813~31bf3856ad364e35~amd64~~6.1.1.11.cat

    Would be grateful for any advice.

    Thanks.
      My Computer


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

    Please follow the instructions in Windows Update Posting Instructions and post the results
      My Computer


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

    Thanks Noel. I've checked the details.

    1. Done
    2. Done
    3. Error Code - 800B0100 (Note - I have already installed a couple of times the Update to Windows Update manager that is a recommended solution for this error)
    4. CBS.log attached.

    Many thanks for your support.
      My Computer


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

    There is no sign of the SFC having run in the CBS log, and there is no CheckSUR log or persist log
    please follow the instructions
      My Computer


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

    That's strange, apologies - I've just re-run and I've attached the CBS log and the CheckSUR log (I had initially cut and pasted the contents into my initial posting) and the CheckSUR.persist file in case that also helps.
      My Computer


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

    Great - it gives us something to work with...
    from the CBS log
    Code:
     Line 9847: 2013-01-14 17:20:35, Info                  CSI    000002f3 [SR] Beginning Verify and Repair transaction
     Line 9852: 2013-01-14 17:20:35, Info                  CSI    000002f6 [SR] Cannot verify component files for Microsoft-Windows-DriverFrameworks-UserMode, Version = 6.1.7601.17803, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
     Line 9857: 2013-01-14 17:20:35, Info                  CSI    000002f9 [SR] Cannot verify component files for Microsoft-Windows-DriverFrameworks-UserMode.Resources, Version = 6.1.7601.17803, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
     Line 9862: 2013-01-14 17:20:35, Info                  CSI    000002fc [SR] Recovered manifest from backup for Microsoft-Windows-DriverFrameworks-UserMode.Resources, Version = 6.1.7601.17803, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
     Line 9869: 2013-01-14 17:20:35, Info                  CSI    000002fe [SR] Repair complete
    From the CheckSUR log.....
    Code:
    Unavailable repair files:
     winsxs\manifests\amd64_microsoft-windows-d..-usermode.resources_31bf3856ad364e35_6.1.7601.17803_en-us_251461586e43c0e3.manifest
     winsxs\manifests\amd64_microsoft-windows-d..-usermode.resources_31bf3856ad364e35_6.1.7601.22004_en-us_259ed68f8760ad46.manifest
     winsxs\manifests\amd64_microsoft-windows-d..frameworks-usermode_31bf3856ad364e35_6.1.7601.17803_none_fb416b4f0bdbe260.manifest
     winsxs\manifests\amd64_microsoft-windows-d..frameworks-usermode_31bf3856ad364e35_6.1.7601.22004_none_fbcbe08624f8cec3.manifest
     servicing\packages\Package_1_for_KB2685813~31bf3856ad364e35~amd64~~6.1.1.11.mum
     servicing\packages\Package_1_for_KB2685813~31bf3856ad364e35~amd64~~6.1.1.11.mum
     servicing\packages\Package_8_for_KB2685813~31bf3856ad364e35~amd64~~6.1.1.11.mum
     servicing\packages\Package_8_for_KB2685813~31bf3856ad364e35~amd64~~6.1.1.11.mum
     servicing\packages\Package_for_KB2685813_SP1~31bf3856ad364e35~amd64~~6.1.1.11.mum
     servicing\packages\Package_for_KB2685813_SP1~31bf3856ad364e35~amd64~~6.1.1.11.mum
     servicing\packages\Package_for_KB2685813~31bf3856ad364e35~amd64~~6.1.1.11.mum
     servicing\packages\Package_for_KB2685813~31bf3856ad364e35~amd64~~6.1.1.11.mum
     servicing\packages\Package_1_for_KB2685813~31bf3856ad364e35~amd64~~6.1.1.11.cat
     servicing\packages\Package_1_for_KB2685813~31bf3856ad364e35~amd64~~6.1.1.11.cat
     servicing\packages\Package_8_for_KB2685813~31bf3856ad364e35~amd64~~6.1.1.11.cat
     servicing\packages\Package_8_for_KB2685813~31bf3856ad364e35~amd64~~6.1.1.11.cat
     servicing\packages\Package_for_KB2685813_SP1~31bf3856ad364e35~amd64~~6.1.1.11.cat
     servicing\packages\Package_for_KB2685813_SP1~31bf3856ad364e35~amd64~~6.1.1.11.cat
     servicing\packages\Package_for_KB2685813~31bf3856ad364e35~amd64~~6.1.1.11.cat
     servicing\packages\Package_for_KB2685813~31bf3856ad364e35~amd64~~6.1.1.11.cat
    Shouldn't be too bad to sort those out - I need to eat first, so it'll be a couple of hours before I can post a fix protocol
    Shout if you don't hear from me in the next 12 hours - it means I got side-tracked!
      My Computer


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

    I've uploaded a file - claxx.zip - to my SkyDrive at https://skydrive.live.com/#cid=936736BB8FCEB92F&id=936736BB8FCEB92F%21526
    Please download and save it.
    Right-click on the downloaded file, and select Extract all…
    Extract to the default location - which will create a new folder claxx in the same place.
    Open this folder - there should be two folders inside it (Manifests, and Packages)

    Copy the content of the Packages folder to the
    C:\Windows\Temp\CheckSur\Servicing\Packages

    And the content of the manifests folder (.manifest files) into this folder:

    C:\Windows\Temp\CheckSur\Winsxs\Manifests

    Now run the CheckSUR tool again (it may take a while)

    Post the new CheckSUR.log file, and the CheckSUR.persist.log file.

    Then run another SFC /SCANNOW and post the new CBS.log file
      My Computer


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

    Noel - thank you for taking on my case - it is probably me but I couldn't see claxx.zip on the link above. Am I looking in wrong place?
      My Computer


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

    Ooops! - looks like I did everything but upload it!
    It should be there now :)
      My Computer


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

    Hi - have just completed the Windows Update Readiness Tool and sfc /scannow. When SFC ran it said it had found some corrupt files that had not been able to be fixed. All three log files should be in the attachment.
    Thanks
    Clare
      My Computer


 
Page 1 of 6 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 02:16.
Find Us