locked
Windows update encountered an unknown error Code 800B0100 - Server 2008 Enterprise SP1. Service pack 2 installation doesn't start also. RRS feed

  • Question

  • On an 2008 enterprise server 64 bit, windows update failed with the code 800B0100 and the server manager gives Error in Roles nad Features.
    Installation of SP2 stops with message telling that SP1 has to be installed first (already installed).
    On running the Windows6.0-KB947821-v5-x64 System Update Readiness Tool the log files show:

    =================================
    Checking System Update Readiness.
    Binary Version 6.0.6002.22202
    Package Version 6.0
    2009-12-23 08:48

    Checking Windows Servicing Packages

    Checking Package Manifests and Catalogs

    Checking Package Watchlist

    Checking Component Watchlist

    Checking Packages
    (f) CBS MUM Missing 0x00000002 servicing\packages\WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.4.7600.226.mum  
    (f) CBS MUM Missing 0x00000002 servicing\packages\WUClient-SelfUpdate-Aux~31bf3856ad364e35~amd64~~7.4.7600.226.mum  

    Checking Component Store

    Summary:
    Seconds executed: 308
     Found 2 errors
      CBS MUM Missing Total count: 2

    Unavailable repair files:
     servicing\packages\WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.4.7600.226.mum
     servicing\packages\WUClient-SelfUpdate-Aux~31bf3856ad364e35~amd64~~7.4.7600.226.mum
     servicing\packages\WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.4.7600.226.cat
     servicing\packages\WUClient-SelfUpdate-Aux~31bf3856ad364e35~amd64~~7.4.7600.226.cat
    -------------------------------
    I found that this problem is related to corrupted files but i didn't find any working link to download these files.
    The published links in the similar topics are not available any more.


    Tuesday, December 29, 2009 2:59 AM

Answers

All replies

  • Hi,

     

    Please download the hotfix.zip file from the following site. Extract it and copy the files to C:\Windows\servicing\Packages to replace the old files.

     

    https://sftus.one.microsoft.com/choosetransfer.aspx?key=4a384a99-a1b1-4c8c-be00-de42065cd49f

     

    Password: {{VemIg]D0O7

     

    Hope it helps.

     

    Tim Quan - MSFT

     

    Tuesday, December 29, 2009 7:30 AM
  • Thank you Tim.

    I downloaded these files and i copied them acording your instruction.
    I had to take ownership to copy these files.
    Now Server manager doesn't have Errors in Roles and Features.
    In Add/Remove programs Windows shows all updates (before they were only these 3 related to Net 3.5)
    Running the Windows6.0-KB947821-v5-x64 System Update Readiness Tool doesn't show errors.

    Windows update started working but it came with new Error code - 80070020.
    I tried to install SP2 and it finished fine.
    After restart I tried again Windows update and i got same Error code - 80070020.

    I followed the article http://support.microsoft.com/kb/883825 
    I am working remotely and i can't start server in safe mode only.
    I restarted server in clean boot (In Msconfig - Under Selective Startup,  the Load startup items check box is cleared and in the Services tab, after hiding  All Microsoft services I clicked Disable all for rest of the services.).
    I disabled Windows firewall in all 3 profiles.
    Symantec Endpoint protection (only Antivirus and Antispyware) is off.

    Windows updated started working, one update was installed and after that it showed the message:
    "Install new Windows Update Software
    To check for updates,  you must first install an update for Windows update...."
    I clicked Install now and i got again:
    "Windows could not search for new updates.... Code 80070020 Windows update encountered an unknown error."
    I restarted server one more time and i tried again windows update - same error.
    Please advice.
    Thank you.
    Wednesday, December 30, 2009 2:36 AM
  • Hi,

     

    Please also uncheck all the boxes under the Startup tab in msconfig.

     

    If the issue persists, let’s rename Windows Update Temporary folders:

     

    1. Click Start, in Start Search item, type: "notepad" (without quotes) and press Enter.

    2. Copy the following commands and then paste them into the opened Notepad window:

     

    net stop wuauserv

    net stop Cryptsvc

    cd /d %windir%\SoftwareDistribution

    rd /s /q DataStore

    ren %windir%\system32\catroot2 catroot2.old

    net start wuauserv

    net start Cryptsvc

     

    3. After pasting the above commands, please close the Notepad window. Choose Save when you are prompted to save the file. Type "register.bat" as the file name and choose Desktop from the left panel as the location.

    4. Refer to the Desktop and right click the register.bat file, then choose Run as administrator.

    5. You will see a DOS-like window processing.

     

    Test the issue again.

     

    If the issue still occurs, please help me collect the following information for further research:

     

    Screenshot

    =======

    1. When the error message appears, press Print Screen (Pr Scrn) (next to the F12 button) to capture a screen shot.

    2. From Start, go to Run, type "MSPAINT" (without the quotation marks) in the Open box, and then click OK.

    3. Use Ctrl + V to paste the screen shot to the canvas.

    4. From the File menu, go to Save and save as a JPG file.

     

    WindowsUpdate.log

    ============

    1. Click Start->Run, type: %windir% and press OK.

    2. Locate a file named "WindowsUpdate.log".

     

    System Information

    =============

    1. Click Start, go to Run, type in "MSINFO32" and press Enter to start System Information.

    2. On the popup window, on the menu bar, click File, and click Save to save it as an NFO file, such as system.nfo.

     

    Please upload the above files to

    https://sftus.one.microsoft.com/choosetransfer.aspx?key=5a54e6a8-bf3f-4ea1-a8e6-5a7a4b55371a

     

    Password: 4Xd*)3aMn%%@FK]o

     

    Tim Quan - MSFT

     

    Wednesday, December 30, 2009 7:38 AM
  • I have this exact same issue, it seems like it's hard to resolve this issue, but it looks like it has something to do with permissions, although i changed them back to the TrustedInstaller user.

    http://social.technet.microsoft.com/Forums/en-US/winservermanager/thread/b4f793bb-9225-40d9-b1df-4ffadcba3263?prof=required&ppud=4
    and
    http://social.technet.microsoft.com/Forums/en-US/winservermanager/thread/22094f08-9482-4600-a338-443c50a8777c?prof=required&ppud=4
    Wednesday, December 30, 2009 2:00 PM
  • Thank you Tim.

    After execution of Register.bat I got another Error code - 80071A90.
    I tried again Windows update and i got the old Error code - 80070020.
    I uploaded two screenshots for both Error codes, WindowsUpdate.log and system.nfo.
    I tried to use Register.bat without firewall and with disabled Symantec client - same Error codes.
    I did Clean boot, no firewall, use Register.bat, start Windows update - same Error codes.
    I see Missterunderstood has similar problem.
    FYI if this could help: My second domain controller is same version of Win 2008 but it has only SP1. Windows update stops at KB955430 with Error code 80071A90 and if i try again with Error code 80070020. It looks like SP2 doesn't change too much the Windows update game.
    Thanks again.

    Thursday, December 31, 2009 1:34 AM
  • I have a similar issue as well:

    =================================
    Checking System Update Readiness.
    Binary Version 6.0.6002.22202
    Package Version 6.0
    2009-12-31 17:03

    Checking Windows Servicing Packages

    Checking Package Manifests and Catalogs

    Checking Package Watchlist

    Checking Component Watchlist

    Checking Packages
    (f) CBS MUM Missing 0x00000002 servicing\packages\WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.4.7600.226.mum  
    (f) CBS MUM Missing 0x00000002 servicing\packages\WUClient-SelfUpdate-Core~31bf3856ad364e35~x86~~7.4.7600.226.mum  

    Checking Component Store
    (f) CSI Catalog Corrupt 0x800B0003 winsxs\Catalogs\b6204bece70030898f1f19cf61f0fe173e7e0c33880c090e3174b6e93cfb3852.cat microsoft-w...deployment_31bf3856ad364e35_7.4.7600.226_c2c51d03e34cf294 
    (f) CSI Catalog Corrupt 0x800B0003 winsxs\Catalogs\d26936642e73b7d74fcf4e9a99ba3c148b2cac7345df00ade3b2cebc6d9d33b7.cat microsoft-w...deployment_31bf3856ad364e35_7.4.7600.226_3f47314b6f3e4f53 
    (f) CSI Catalog Corrupt 0x800B0003 winsxs\Catalogs\7f6e5fb058fca24bde50daed7bef30ded473619c66c6f4cfc4aa0b7147e16a01.cat microsoft-w..anguagepack_31bf3856ad364e35_7.4.7600.226_87c0f05279aa5f8d 
    (f) CSI Catalog Corrupt 0x800B0003 winsxs\Catalogs\2ecdea0a49addf0a24be3524837804aa683f8e25cf1e138603314cd037c03984.cat microsoft-w..anguagepack_31bf3856ad364e35_7.4.7600.226_07f591faa9b0a436 

    Summary:
    Seconds executed: 2225
     Found 6 errors
      CSI Catalog Corrupt Total count: 4
      CBS MUM Missing Total count: 2

    Unavailable repair files:
     servicing\packages\WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.4.7600.226.mum
     servicing\packages\WUClient-SelfUpdate-Core~31bf3856ad364e35~x86~~7.4.7600.226.mum
     servicing\packages\WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.4.7600.226.cat
     servicing\packages\WUClient-SelfUpdate-Core~31bf3856ad364e35~x86~~7.4.7600.226.cat

    Friday, January 1, 2010 6:23 PM
  • Hi Promenet,

     

    Thank you for sending me the files.

     

    This issue seems to be caused by improper proxy entries.

     

    I suggest using the following steps to remove the proxy server entries from the WinHTTP proxy configuration:

     

    1. Click Start, and then type cmd in the Start Search box. 

     

    2. Right-click cmd.exe in the Programs list, and then click Run as administrator .

     

    Note If you are prompted for an administrator password or confirmation, type the password or click Continue. 

     

    3. Type the following command and then press Enter:

     

    netsh winhttp show proxy

     

    Note The proxy setting is listed next to Proxy Server . If there is no proxy server, Direct Access <no proxy server> is shown in the Command Prompt window. 

     

    4. To remove the listed proxy setting, type the following command and then press Enter:

     

    netsh winhttp reset proxy 

     

    5. Go back to the Windows Update or Microsoft Update site and try to download and install the updates again. 

     

    If the issue persists, please let me know whether your domain uses WSUS to dispatch updates.

    Hope it helps.

     

    Tim Quan - MSFT

    Monday, January 4, 2010 3:43 AM
  • I have a similar issue as well:

    =================================
    Checking System Update Readiness.
    Binary Version 6.0.6002.22202
    Package Version 6.0
    2009-12-31 17:03

    Checking Windows Servicing Packages

    Checking Package Manifests and Catalogs

    Checking Package Watchlist

    Checking Component Watchlist

    Checking Packages
    (f) CBS MUM Missing 0x00000002 servicing\packages\WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.4.7600.226.mum  
    (f) CBS MUM Missing 0x00000002 servicing\packages\WUClient-SelfUpdate-Core~31bf3856ad364e35~x86~~7.4.7600.226.mum  

    Checking Component Store
    (f) CSI Catalog Corrupt 0x800B0003 winsxs\Catalogs\b6204bece70030898f1f19cf61f0fe173e7e0c33880c090e3174b6e93cfb3852.cat microsoft-w...deployment_31bf3856ad364e35_7.4.7600.226_c2c51d03e34cf294 
    (f) CSI Catalog Corrupt 0x800B0003 winsxs\Catalogs\d26936642e73b7d74fcf4e9a99ba3c148b2cac7345df00ade3b2cebc6d9d33b7.cat microsoft-w...deployment_31bf3856ad364e35_7.4.7600.226_3f47314b6f3e4f53 
    (f) CSI Catalog Corrupt 0x800B0003 winsxs\Catalogs\7f6e5fb058fca24bde50daed7bef30ded473619c66c6f4cfc4aa0b7147e16a01.cat microsoft-w..anguagepack_31bf3856ad364e35_7.4.7600.226_87c0f05279aa5f8d 
    (f) CSI Catalog Corrupt 0x800B0003 winsxs\Catalogs\2ecdea0a49addf0a24be3524837804aa683f8e25cf1e138603314cd037c03984.cat microsoft-w..anguagepack_31bf3856ad364e35_7.4.7600.226_07f591faa9b0a436 

    Summary:
    Seconds executed: 2225
     Found 6 errors
      CSI Catalog Corrupt Total count: 4
      CBS MUM Missing Total count: 2

    Unavailable repair files:
     servicing\packages\WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.4.7600.226.mum
     servicing\packages\WUClient-SelfUpdate-Core~31bf3856ad364e35~x86~~7.4.7600.226.mum
     servicing\packages\WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.4.7600.226.cat
     servicing\packages\WUClient-SelfUpdate-Core~31bf3856ad364e35~x86~~7.4.7600.226.cat


    Please post a new thread to avoid confusitons.
    Monday, January 4, 2010 6:30 AM
  • Happy and Successful New Year Tim!

    Thank you for your advice.

     

    There is no proxy server. This was the output:

    “C:\Users\administrator.BCS>netsh winhttp reset proxy

      Current WinHTTP proxy settings:

           Direct access (no proxy server).”

     

    I used “netsh winhttp reset proxy” just in case but windows update still is cycling between:

    "Install new Windows Update Software
    To check for updates,  you must first install an update for Windows update...."

    and if I click Install now i am getting again:
    "Windows could not search for new updates.... Code 80070020 Windows update encountered an unknown error."

    I am checking now if there is WSUS server in the network and I will let you know.

    Thanks.

     

    01-07-2010
    There was WSUS server in the network. According the admin it was maybe not configured properly and he stopped the server yesterday (01-06-20010).
    Thanks

    Wednesday, January 6, 2010 9:15 PM
  • 01-11-2010
    Hi Tim,
    The 2 DC servers that have same issue with Windows update are not clients of WSUS (and they have never been).
    Stopping WSUS server and restarting our "sick" 2008 servers doesn't change the game – we are getting same errors.
    Thanks

    Tuesday, January 12, 2010 3:19 AM
  • Hi Tim,

     

    I have the same issue. However, when it followed the link to download the hotfix.zip. It says incorrect Password..

     

    Please help me with the same.

    Awaiting Reply,

     

    Regards,

    Vicky.

    Wednesday, June 2, 2010 8:07 AM
  • Vicky,

    If you still have this problem, see the second post in this thread. 

    http://social.technet.microsoft.com/Forums/en-US/itprovistaie/thread/0ce7c1e6-7ef2-48e1-b7c9-c8f1e97c71d5/

    The tdss root killer tool is safe - read the happy testimonies in the second half of that thread.  Be happy

     

    Monday, October 18, 2010 2:00 AM