locked
Windows Server 2008 Server manager refresh failed-error 0x800B0100 RRS feed

  • Question

  • Repost of old thread.  looking for files noted in checksur.log     Can anyone post?

    Thanks,

     

    Brad Stedronsky

    Thursday, August 19, 2010 1:48 PM

Answers

  • Can you give a dir of the directory where you downloaded the update and
    are executing the wusa command?
     
    Can you also give the output from the command prompt and the command
    when you try the extract command?
     
     

    -- Mike Burr
    • Marked as answer by BradSted Thursday, August 19, 2010 6:33 PM
    Thursday, August 19, 2010 4:27 PM

All replies


  • =================================
    Checking System Update Readiness.
    Binary Version 6.0.6002.22359
    Package Version 8.0
    2010-08-17 14:59

    Checking Windows Servicing Packages

    Checking Package Manifests and Catalogs

    Checking Package Watchlist

    Checking Component Watchlist

    Checking Packages
    (f) CBS MUM Missing 0x00000002 servicing\Packages\Package_for_KB948881_server_0~31bf3856ad364e35~amd64~~6.0.1.1.mum  
    (f) CBS MUM Missing 0x00000002 servicing\Packages\Package_for_KB948881_server~31bf3856ad364e35~amd64~~6.0.1.1.mum  
    (f) CBS MUM Missing 0x00000002 servicing\Packages\Package_for_KB948881~31bf3856ad364e35~amd64~~6.0.1.1.mum  

    Checking Component Store

    Summary:
    Seconds executed: 407
     Found 3 errors
      CBS MUM Missing Total count: 3

    Unavailable repair files:
     servicing\packages\Package_for_KB948881_server_0~31bf3856ad364e35~amd64~~6.0.1.1.mum
     servicing\packages\Package_for_KB948881_server~31bf3856ad364e35~amd64~~6.0.1.1.mum
     servicing\packages\Package_for_KB948881~31bf3856ad364e35~amd64~~6.0.1.1.mum
     servicing\packages\Package_for_KB948881_server_0~31bf3856ad364e35~amd64~~6.0.1.1.cat
     servicing\packages\Package_for_KB948881_server~31bf3856ad364e35~amd64~~6.0.1.1.cat
     servicing\packages\Package_for_KB948881~31bf3856ad364e35~amd64~~6.0.1.1.cat

    Thursday, August 19, 2010 1:49 PM
  • Hi,
     
    We can recover the files by extracting the update,
     
    32-bit:
    64-bit:
     
    I usually create a local working directory for handling the intermediate
    files and directories. I use c:\servicing
     
    Download the file to the working directory and open an administrative
    command prompt. Extract the files.
     
    c:\servicing>dir
     Volume in drive C has no label.
     Volume Serial Number is 721E-410B
      Directory of c:\servicing
     
    08/19/2010  08:48 AM    <DIR>          .
    08/19/2010  08:48 AM    <DIR>          ..
    08/19/2010  08:48 AM           208,668 Windows6.0-KB948881-x64.msu
                   1 File(s)        208,668 bytes
                   2 Dir(s)  157,932,421,120 bytes free
     
    c:\servicing>wusa Windows6.0-KB948881-x64.msu /extract:c:\servicing\kb948881
     
    *Note that the kb948881 directory will be empty if you do not run as
    administrator*
     
    c:\servicing>cd kb948881
     
    c:\servicing\kb948881>mkdir files
     
    c:\servicing\kb948881>expand -F:* Windows6.0-KB948881-x64.cab files
     
    This will extract all of the files to c:\servicing\kb948881\files
     From here, you can restore the missing .cat and .mum files (these paths
    are relative to %systemroot%, usually C:\Windows),
     
    servicing\packages\Package_for_KB948881_server_0~31bf3856ad364e35~amd64~~6.0.1.1.mum
     servicing\packages\Package_for_KB948881_server~31bf3856ad364e35~amd64~~6.0.1.1.mum
     servicing\packages\Package_for_KB948881~31bf3856ad364e35~amd64~~6.0.1.1.mum
     servicing\packages\Package_for_KB948881_server_0~31bf3856ad364e35~amd64~~6.0.1.1.cat
     servicing\packages\Package_for_KB948881_server~31bf3856ad364e35~amd64~~6.0.1.1.cat
     servicing\packages\Package_for_KB948881~31bf3856ad364e35~amd64~~6.0.1.1.cat
     

    -- Mike Burr
    Thursday, August 19, 2010 2:58 PM
  • Mike, thanks for the assistance

    Having trouble when trying to extract the files from the .msu file...I get a syntax error popup on the wusa command as you had entered.   Is there another way?

    Brad

     

    Thursday, August 19, 2010 3:36 PM
  • Can you give a dir of the directory where you downloaded the update and
    are executing the wusa command?
     
    Can you also give the output from the command prompt and the command
    when you try the extract command?
     
     

    -- Mike Burr
    • Marked as answer by BradSted Thursday, August 19, 2010 6:33 PM
    Thursday, August 19, 2010 4:27 PM
  • I figured it out..thanks for the help!
    Thursday, August 19, 2010 6:34 PM
  • Ok, I'm facing the same issue with my Windows Server 2008 R2 Datacenter Edition.

    I get the error code 0x800B0100 in the Server Manager and it says "Refresh Failed". And also I get this same error code during the Windows Update and it says "Update Failed".

    I'm neither able to add/remove/change any features/roles!

    What do I do?

    I'm sorry I couldn't figure out clearly what solution steps were mentioned above.. :)

    Wednesday, August 25, 2010 11:59 AM
  • Hi,
     
    Can you run the SUR tool and post the output of the
    C:\Windows\Logs\CBS\CheckSUR.log file?
     
     

    -- Mike Burr
    Friday, August 27, 2010 5:25 AM
  • Hi Mike!

    Here is what the CheckSUR.log file has to say:


    =================================
    Checking System Update Readiness.
    Binary Version 6.1.7600.20751
    Package Version 9.0
    2010-08-26 01:16

    Checking Windows Servicing Packages

    Checking Package Manifests and Catalogs
    (f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_2_for_KB978886~31bf3856ad364e35~amd64~~6.1.1.0.mum  Line 1:
    (f) CBS Catalog Corrupt 0x800B0100 servicing\Packages\Package_2_for_KB978886~31bf3856ad364e35~amd64~~6.1.1.0.cat  
    (f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_for_KB978886_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum  Line 1:
    (f) CBS Catalog Corrupt 0x800B0100 servicing\Packages\Package_for_KB978886_RTM~31bf3856ad364e35~amd64~~6.1.1.0.cat  
    (f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_for_KB978886~31bf3856ad364e35~amd64~~6.1.1.0.mum  Line 1:
    (f) CBS Catalog Corrupt 0x800B0100 servicing\Packages\Package_for_KB978886~31bf3856ad364e35~amd64~~6.1.1.0.cat  

    Checking Package Watchlist

    Checking Component Watchlist

    Checking Packages

    Checking Component Store

    Summary:
    Seconds executed: 113
     Found 6 errors
      CBS MUM Corrupt Total count: 3
      CBS Catalog Corrupt Total count: 3

    Unavailable repair files:
     servicing\packages\Package_2_for_KB978886~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_2_for_KB978886~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_for_KB978886_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_for_KB978886_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_for_KB978886~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_for_KB978886~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_2_for_KB978886~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_2_for_KB978886~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_for_KB978886_RTM~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_for_KB978886_RTM~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_for_KB978886~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_for_KB978886~31bf3856ad364e35~amd64~~6.1.1.0.cat

    Looks like some files are corrupt. What do I do now? :)

    Friday, August 27, 2010 7:54 AM
  • Alrighty, I'll eventually publish a blog post on this, but for the meantime we are going to take a high level ~4 step approach,

    1. Identify where we can get the missing files
    2. Extract the relevant update(s) and/or mount the installation media for the base OS
    3. Extract the relevant CAB files that contain the files that are needed
    4. Restore the missing files

    Based on the names of the missing files,

    servicing\packages\Package_2_for_KB978886~31bf3856ad364e35~amd64~~6.1.1.0.mum

    we can quickly see that the missing/corrupt .mum and .cat files came from the KB978886 update.

    It appears that you are running Windows 2008 R2 x64, so I will demonstrate the extraction with this installer,

    http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=a1f95600-34e5-44b3-b2cb-b2b2cbf645cb

    I have created a temporary folder, c:\temp to store my working files throughout this process and have saved the above update there. Next, I have started the command prompt as administrator:

    Start -> search box, type cmd, right click the cmd.exe and select "Run as Administrator"

    Next, here is the command output for me as I enter commands,

    Microsoft Windows [Version 6.1.7600]
    Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

    C:\Windows\system32>cd c:\temp

    c:\temp>wusa Windows6.1-KB978886-x64.msu /extract:c:\temp\kb978886

    c:\temp>cd kb978886

    c:\temp\kb978886>dir
     Volume in drive C has no label.
     Volume Serial Number is 721E-410B

     Directory of c:\temp\kb978886

    08/27/2010  08:40 AM    <DIR>          .
    08/27/2010  08:40 AM    <DIR>          ..
    06/15/2010  04:57 PM               530 Windows6.1-KB978886-x64-pkgProperties.txt

    06/15/2010  04:59 PM         1,009,189 Windows6.1-KB978886-x64.cab
    06/15/2010  04:57 PM               444 Windows6.1-KB978886-x64.xml
    06/15/2010  05:01 PM           162,338 WSUSSCAN.cab
                   4 File(s)      1,172,501 bytes
                   2 Dir(s)  156,675,526,656 bytes free

    c:\temp\kb978886> mkdir files

    c:\temp\kb978886> expand -F:* Windows6.1-KB978886-x64.cab files
    Microsoft (R) File Expansion Utility  Version 6.1.7600.16385
    Copyright (c) Microsoft Corporation. All rights reserved.

    Adding files\update.mum to Extraction Queue
    Adding files\update.cat to Extraction Queue
    Adding files\update-bf.mum to Extraction Queue
    Adding files\update-bf.cat to Extraction Queue
    Adding files\package_2_for_kb978886~31bf3856ad364e35~amd64~~6.1.1.0.cat to Extraction Queue
    Adding files\amd64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7600.20733_none_0fd0b57e990e2079\fwpkclnt.sys to Extraction Queue
    Adding files\amd64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7600.16610_none_0f59b7ad7fe2fcc8\fwpkclnt.sys to Extraction Queue
    Adding files\amd64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7600.16610_none_0f59b7ad7fe2fcc8\tcpip.sys to Extraction Queue
    Adding files\amd64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7600.20733_none_0fd0b57e990e2079\tcpip.sys to Extraction Queue
    Adding files\package_1_for_kb978886~31bf3856ad364e35~amd64~~6.1.1.0.cat to Extraction Queue
    Adding files\package_3_for_kb978886~31bf3856ad364e35~amd64~~6.1.1.0.cat to Extraction Queue
    Adding files\package_for_kb978886_rtm~31bf3856ad364e35~amd64~~6.1.1.0.mum to Extraction Queue
    Adding files\amd64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7600.20733_none_0fd0b57e990e2079.manifest to Extraction Queue
    Adding files\package_2_for_kb978886_bf~31bf3856ad364e35~amd64~~6.1.1.0.mum to Extraction Queue
    Adding files\package_1_for_kb978886_bf~31bf3856ad364e35~amd64~~6.1.1.0.mum to Extraction Queue
    Adding files\package_3_for_kb978886_bf~31bf3856ad364e35~amd64~~6.1.1.0.mum to Extraction Queue
    Adding files\package_for_kb978886_rtm~31bf3856ad364e35~amd64~~6.1.1.0.cat to Extraction Queue
    Adding files\amd64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7600.16610_none_0f59b7ad7fe2fcc8.manifest to Extraction Queue
    Adding files\package_2_for_kb978886_bf~31bf3856ad364e35~amd64~~6.1.1.0.cat to Extraction Queue
    Adding files\package_1_for_kb978886_bf~31bf3856ad364e35~amd64~~6.1.1.0.cat to Extraction Queue
    Adding files\package_3_for_kb978886_bf~31bf3856ad364e35~amd64~~6.1.1.0.cat to Extraction Queue
    Adding files\package_for_kb978886_rtm_bf~31bf3856ad364e35~amd64~~6.1.1.0.mum to Extraction Queue
    Adding files\amd64_48f68e154e2a96cc9002091c8936ab97_31bf3856ad364e35_6.1.7600.20733_none_5976d7d43af5ba65.manifest to Extraction Queue
    Adding files\package_1_for_kb978886~31bf3856ad364e35~amd64~~6.1.1.0.mum to Extraction Queue
    Adding files\package_2_for_kb978886~31bf3856ad364e35~amd64~~6.1.1.0.mum to Extraction Queue
    Adding files\package_for_kb978886_rtm_bf~31bf3856ad364e35~amd64~~6.1.1.0.cat to Extraction Queue
    Adding files\amd64_336fc16a68bca61114642eda02f33f41_31bf3856ad364e35_6.1.7600.16610_none_39eac325001025a8.manifest to Extraction Queue
    Adding files\package_3_for_kb978886~31bf3856ad364e35~amd64~~6.1.1.0.mum to Extraction Queue

    Expanding Files ....
    Progress: 17 out of 28 files
    Expanding Files Complete ...
    28 files total.

    To recap, the commands that I entered,

    cd c:\temp
    wusa Windows6.1-KB978886-x64.msu /extract:c:\temp\kb978886
    cd kb978886
    dir
    mkdir files
    expand -F:* Windows6.1-KB978886-x64.cab files


    If you follow the exact same procedure as I did above, then you will have the files in

    C:\temp\kb978886\files

    From there, you should be able to restore the necessary files back to the following paths,

     servicing\packages\Package_2_for_KB978886~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_2_for_KB978886~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_for_KB978886_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_for_KB978886_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_for_KB978886~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_for_KB978886~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_2_for_KB978886~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_2_for_KB978886~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_for_KB978886_RTM~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_for_KB978886_RTM~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_for_KB978886~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_for_KB978886~31bf3856ad364e35~amd64~~6.1.1.0.cat

    Note that these paths are relative to %systemroot% (usually C:\Windows\), so for me,

    servicing\packages\Package_2_for_KB978886~31bf3856ad364e35~amd64~~6.1.1.0.mum

    is c:\Windows\servicing\packages\Package_2_for_KB978886~31bf3856ad364e35~amd64~~6.1.1.0.mum



    -- Mike Burr
    Friday, August 27, 2010 2:57 PM