none
Windows Update Error 800B0001

    Question

  • We are currently running SCCM 2007 and FEP 2010 and are currently receiving the follwoing error when attempting to check for update managed by the Admin. Both machines are Windows 7 x86.

    I have tried the following steps:

     ~ FixIt

     ~ Readiness Tool

     ~ Re-register WinTrust.dll

    All other clients in the environment are working fine and I have also veriefied that the two machines are in fact recieving all policies.

    HELP!

    Monday, June 25, 2012 3:08 PM

All replies

  • Same here, running W7 Enterprise x64.
    Monday, June 25, 2012 3:57 PM
  • Well, as far as I can tell, Microsoft does not have a standalone installer which means that it cannot be diwtributed to clients in an Enterprise environment as part of the monthly patch proccess.
    Monday, June 25, 2012 7:08 PM
  • Hi,

     

    Please check whether you have tried steps in this article Windows Update error 800B0001

     

    Also try to rename the 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
    ren %windir%\system32\catroot2 catroot2.old
    ren %windir%\SoftwareDistribution sold.old
    net start CryptSvc
    net start wuauserv
    pause
     
    3) After pasting the above commands, please close the Notepad window. Choose "Save" when you are prompted to save the file. Type "rename.bat" as the file name and save it to the Desktop.
    4) Return to the Desktop, right click the rename.bat file and choose "Run as administrator".
    5) You will see a DOS-like window processing.
     
    Now try Windows Update to see if the issue has been resolved.
     
    If issue persists, please upload your windowsupdate.log to SkyDrive for further research.
     
    Use SkyDrive to upload collected files and post screen shot/picture.
     
    Hope this helps.

    Vincent Wang

    TechNet Community Support

    Wednesday, June 27, 2012 12:14 PM
    Moderator
  • Hi,

    I was having the same problem, if you have a look in the log file and see the following:

    2012-06-27 15:09:08:385912 6d8 AU #############
    2012-06-27 15:09:08:385912 6d8 AU ## START ##  AU: Search for updates
    2012-06-27 15:09:08:385912 6d8 AU #########
    2012-06-27 15:09:08:388912 6d8 AU <<## SUBMITTED ## AU: Search for updates [CallId = {CC2C9352-0707-4557-8B17-0134F7832B47}]
    2012-06-27 15:09:08:388912 b60 Agent *************
    2012-06-27 15:09:08:388912 b60 Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2012-06-27 15:09:08:388912 b60 Agent *********
    2012-06-27 15:09:08:388912 b60 Agent  * Online = Yes; Ignore download priority = No
    2012-06-27 15:09:08:388 912 b60 Agent  * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
    2012-06-27 15:09:08:388912 b60 Agent  * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2012-06-27 15:09:08:388912 b60 Agent  * Search Scope = {Machine}
    2012-06-27 15:09:08:388912 b60 Setup Checking for agent SelfUpdate
    2012-06-27 15:09:08:389912 b60 Setup Client version: Core: 7.6.7600.256  Aux: 7.6.7600.256
    2012-06-27 15:09:10:683 912 b60 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
    2012-06-27 15:09:10:687912 b60 Misc Microsoft signed: Yes
    2012-06-27 15:09:10:688912 b60 Misc WARNING: Digital Signatures on file C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab are not trusted: Error 0x800b0001
    2012-06-27 15:09:10:688912 b60 Setup WARNING: SelfUpdate check failed to download package information, error = 0x800B0001
    2012-06-27 15:09:10:688912 b60 Setup FATAL: SelfUpdate check failed, err = 0x800B0001
    2012-06-27 15:09:10:688912 b60 Agent  * WARNING: Skipping scan, self-update check returned 0x800B0001
    2012-06-27 15:09:10:689912 b60 Agent  * WARNING: Exit code = 0x800B0001
    2012-06-27 15:09:10:689912 b60 Agent *********
    2012-06-27 15:09:10:689912 b60 Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2012-06-27 15:09:10:689912 b60 Agent *************
    2012-06-27 15:09:10:689912 b60 Agent WARNING: WU client failed Searching for update with error 0x800b0001
    2012-06-27 15:09:10:689912 544 AU >>##  RESUMED  ## AU: Search for updates [CallId = {CC2C9352-0707-4557-8B17-0134F7832B47}]
    2012-06-27 15:09:10:689912 544 AU  # WARNING: Search callback failed, result = 0x800B0001
    2012-06-27 15:09:10:690912 544 AU  # WARNING: Failed to find updates with error code 800B00012012-06-27 15:09:10:690912 544 AU #########2012-06-27 15:09:10:690912 544 AU ##  END  ##  AU: Search for updates [CallId = {CC2C9352-0707-4557-8B17-0134F7832B47}]
    2012-06-27 15:09:10:690912 544 AU #############

    If you do, then download the following service pack and install it on the SCCM/WSUS server (it shall require a restart and your clients will no longer (should no longer) get the message and be able to collect updates.

    http://support.microsoft.com/kb/2720211


    • Edited by jag_nagra Wednesday, June 27, 2012 2:50 PM
    Wednesday, June 27, 2012 2:49 PM
  • I just resolved as similar problem on my network.

    Win7 Enterprise machine deployed with MDT2012 were getting this error when trying to connect to the WSUS server.

    In my case the issue was that the deployed machines were using WU client 7.6.7600.256 (check the file version of c:\windows\system32\wuauclt.exe), which requirwed an update server-side.

    Patching our WSUS server with KB2720211 resolved the issue, although I'd recommend reading up on KB2720211 before doing so in a production environment as there have been reports of issue after this patch. A quick google on this KB should yield some info.

    Can't guarantee this is your issue, but hope it helps.

    Tony

    Wednesday, June 27, 2012 4:27 PM
  • We are currently running SCCM 2007 and FEP 2010 and are currently receiving the follwoing error when attempting to check for update managed by the Admin. Both machines are Windows 7 x86.

    I have tried the following steps:

     ~ FixIt

     ~ Readiness Tool

     ~ Re-register WinTrust.dll

    All other clients in the environment are working fine and I have also veriefied that the two machines are in fact recieving all policies.

    HELP!

    Possibly a duplicate of http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_update/update-error-800b0001-updates-managed-by/02f8c21d-aa8b-48b6-9245-2e7336a75902 

    ~Robear Dyer (PA Bear) ~ MS MVP (IE, Mail, Security, Windows & Update Services) since 2002 ~ Disclaimer: MS MVPs neither represent nor work for Microsoft

    Wednesday, June 27, 2012 7:05 PM
  • Hi all, is there any update information?

    Thursday, July 19, 2012 2:18 AM
  • Hi,

    I'm running 2008 R2 with WSUS, using "customwebsite" port 8530 as I'm running another site on port 80. Client is Win7 Pro x64

    I also had tried everything mentioned here. 

    As with BluntTony_79, I installed update KB2720211 - This solved the issue for me.

    Hope it does the same for you - Please read related issues to this update - http://support.microsoft.com/kb/2720211


    • Edited by BenGad Friday, July 20, 2012 1:27 AM
    Friday, July 20, 2012 1:26 AM
  • Hello

    My setup is similar to BenGad, and the very same solution worked. Applying KB2720211 to the server, solved the problem. No more 800B0001 on Win7 x64 enterprise clients.

    Best Regards,

    Jesper Vindum, Denmark.

    Saturday, August 11, 2012 2:37 PM
  • http://support.microsoft.com/kb/2734608

    go for it !!!

    • Proposed as answer by Chintan Vyas Tuesday, December 04, 2012 4:18 PM
    Monday, December 03, 2012 5:23 PM