none
Digital signature on file not trusted: 0x800B0001

    Question

  • Hi.

    I've searched and found numerous issues regarding error 0x800B0001, but none that can help me. Last effort is to post a new question, here.

    I've installed WSUS 3.0 on a new server, which is going to relieve an SBS2008-server of the WSUS task. The server is also going to host SCE, but haven't got to that, yet. Since this is a small organization, I have decided not to migrate settings from the old WSUS, hence start with a clean sleet.

    Everything installed fine, and I have directed all clients to the new WSUS server with GP. However, all clients (except one, actually) shows up as Not reported yet on the status info. Looking into the WindowsUpdate.log I can see

    2012-06-14	11:11:07:929	 824	1358	Agent	*************
    2012-06-14	11:11:07:929	 824	1358	Agent	** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2012-06-14	11:11:07:929	 824	1358	Agent	*********
    2012-06-14	11:11:07:929	 824	1358	Agent	  * Online = Yes; Ignore download priority = No
    2012-06-14	11:11:07:929	 824	1358	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-14	11:11:07:929	 824	1358	Agent	  * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2012-06-14	11:11:07:929	 824	1358	Agent	  * Search Scope = {Machine}
    2012-06-14	11:11:07:929	 824	1358	Setup	Checking for agent SelfUpdate
    2012-06-14	11:11:07:929	 824	1358	Setup	Client version: Core: 7.6.7600.256  Aux: 7.6.7600.256
    2012-06-14	11:11:10:491	 824	1358	Misc	Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
    2012-06-14	11:11:10:493	 824	1358	Misc	 Microsoft signed: Yes
    2012-06-14	11:11:10:493	 824	1358	Misc	WARNING: Digital Signatures on file C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab are not trusted: Error 0x800b0001
    2012-06-14	11:11:10:493	 824	1358	Setup	WARNING: SelfUpdate check failed to download package information, error = 0x800B0001
    2012-06-14	11:11:10:493	 824	1358	Setup	FATAL: SelfUpdate check failed, err = 0x800B0001
    2012-06-14	11:11:10:493	 824	1358	Agent	  * WARNING: Skipping scan, self-update check returned 0x800B0001
    2012-06-14	11:11:10:494	 824	1358	Agent	  * WARNING: Exit code = 0x800B0001
    2012-06-14	11:11:10:494	 824	1358	Agent	*********
    2012-06-14	11:11:10:494	 824	1358	Agent	**  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2012-06-14	11:11:10:494	 824	1358	Agent	*************
    2012-06-14	11:11:10:494	 824	1358	Agent	WARNING: WU client failed Searching for update with error 0x800b0001

    I have enabled SSL on the communications, and when I browse to https://mywsusserver/Selfupdate/wuident.cab, the certificate is trusted. The certificate I use on IIS is signed by the CA on the local domain.

    I have tried to register all DLLs (as suggested by some other posts I have found), and to remove the SoftwareDistribution-catalog entirely to force a redownload of everything. No success.

    Any suggestions is appreciated!

    Best regards,

    Chocolate Eater

    Thursday, June 14, 2012 9:20 AM

Answers

  • Hi folks,

                    Like most of you, I began getting this error recently when trying to install Forefront on client machines. I ran the System Update Readiness Tool, but it found no errors. In the end I followed the link mentioned here: http://blogs.technet.com/b/wsus/archive/2012/06/08/further-hardening-of-wsus-now-available.aspx 

    In step two I applied the KB 2720211 on the WSUS server; listed here:

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

     After restarting the Server, my clients could download their updates again without error. Hope it helps some folks.


    Sys Admin, Rob M

    • Proposed as answer by Edin Smlatic Saturday, June 23, 2012 6:04 PM
    • Marked as answer by Chocolate Eater Saturday, June 23, 2012 7:54 PM
    Wednesday, June 20, 2012 7:53 PM
  • Chocolate Eater,

    Presuming you have just installed WSUS30-KB972455-x86.exe or WSUS30-KB972455-x64.exe on your server, you might want to look at this knowledge base article which talks to an update for those two WSUS installers:

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

    That page offers you a choice of two downloads, one for x86 and one for x64 architecture.  Follow the instructions above the download link area (if you don't use the Network Load Balancing features, not to worry, just pay closer attention to items 2,4,5 and 6).

    As I am somewhat impatient, I elected to force a client update by running ( wuauclt.exe /resetauthorization /detectnow ) on the client to test results.  If this works for you as I hope it does, checking the WindowsUpdate.log file on the client should show you that things are indeed a bit different from your post above.  Wait a bit longer and the client should check in naturally at your WSUS server.  FWIW, you can also just run ( wuauclt.exe /detectnow ) on the client.

    Happy patching.

    The Commerce Company


    Monday, June 18, 2012 6:29 AM

All replies

  • Hi,

    Pls follow the resolution phase explained in http://support.microsoft.com/kb/317541/en-us

    Disabling "Update Root Certificates" in the Windows Components OR specifying the proxy using proxycfg to see whether it works.


    Regards,
    Clarence
    Forum Support
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contacttnmff@microsoft.com.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Friday, June 15, 2012 2:47 AM
    Moderator
  • Chocolate Eater,

    Presuming you have just installed WSUS30-KB972455-x86.exe or WSUS30-KB972455-x64.exe on your server, you might want to look at this knowledge base article which talks to an update for those two WSUS installers:

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

    That page offers you a choice of two downloads, one for x86 and one for x64 architecture.  Follow the instructions above the download link area (if you don't use the Network Load Balancing features, not to worry, just pay closer attention to items 2,4,5 and 6).

    As I am somewhat impatient, I elected to force a client update by running ( wuauclt.exe /resetauthorization /detectnow ) on the client to test results.  If this works for you as I hope it does, checking the WindowsUpdate.log file on the client should show you that things are indeed a bit different from your post above.  Wait a bit longer and the client should check in naturally at your WSUS server.  FWIW, you can also just run ( wuauclt.exe /detectnow ) on the client.

    Happy patching.

    The Commerce Company


    Monday, June 18, 2012 6:29 AM
  • I have same issue.

    I WSUS 3.0 SP2 (Version: 3.2.7600.226) and 300 computers/servers are connected to my WSUS. Everything worked prefectly for two years until now.
    Two clients, Windows XP SP3 and Windows Server 2008 R2 SP1 x64, are reporting Windows Update Client failed to detect with error 0x800b0001 when contacting to WSUS server. If I try to connect to Microsoft Update on the Internet, everything works perfectly.
    All other clients are working properly. Today I made new syncronisation and approve new updates on my testgroup inside WSUS console.

    On XP:
    I tried http://support.microsoft.com/kb/958045, didn't resolve my issue.
    I tried http://support.microsoft.com/kb/317541/en-us didn't reslove my issue

    On W2k8 R2 SP1 x64:
    I tried http://support.microsoft.com/kb/958045, it took time to download and execute System Update Readiness Tool, also didn't helped. Try also method 2 with regsvr32 Wintrust.dll /s, didn't reslove my issue.

    I didn't install http://support.microsoft.com/kb/2720211 on my WSUS

    Any idea what can I do next?


    Monday, June 18, 2012 8:22 AM
  • Same here.  Just started happening today after apply latest updates!  What's going on?  I'm not using SSL on my WSUS server.

    Some systems work, some don't.  Most of my Windows 2008 and 2008 R2 servers fail.
    • Edited by simdoc Tuesday, June 19, 2012 1:53 AM
    Tuesday, June 19, 2012 1:43 AM
  • Similar situation on Windows 7 Starter. Looking into the WindowsUpdate.log I can see

    4fc Setup Determining whether a new setup handler needs to be downloaded
    2012-06-18 20:10:43:006  960 4fc Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\Handler\WuSetupV.exe:
    2012-06-18 20:10:43:037  960 4fc Misc  Microsoft signed: Yes
    2012-06-18 20:10:43:037  960 4fc Misc WARNING: Digital Signatures on file C:\Windows\SoftwareDistribution\SelfUpdate\Handler\WuSetupV.exe are not trusted: Error 0x800b0001
    2012-06-18 20:10:43:037  960 4fc Setup WARNING: Trust verification failed for WuSetupV.exe. It will be deleted and downloaded, error = 0x800B0001
    2012-06-18 20:10:43:037  960 4fc Setup SelfUpdate handler update required: Current version: 7.6.7600.256, required version: 7.6.7600.256
    2012-06-18 20:10:43:037  960 4fc Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.6.7600.256"
    2012-06-18 20:10:43:068  960 4fc Setup Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.6.7600.256" is already installed.
    2012-06-18 20:10:43:068  960 4fc Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256"
    2012-06-18 20:10:43:240  960 4fc Setup Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256" is applicable but is already staged; it will not be downloaded.
    2012-06-18 20:10:43:240  960 4fc Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256"
    2012-06-18 20:10:43:723  960 4fc Setup Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256" is already installed.
    2012-06-18 20:10:43:723  960 4fc Setup SelfUpdate check completed.  SelfUpdate is NOT required.
    2012-06-18 20:10:45:861  960 4fc Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir\7971F918-A847-4430-9279-4A52D1EFE18D\muv4muredir.cab:
    2012-06-18 20:10:45:907  960 4fc Misc  Microsoft signed: Yes
    2012-06-18 20:10:45:907  960 4fc Misc WARNING: Digital Signatures on file C:\Windows\SoftwareDistribution\WuRedir\7971F918-A847-4430-9279-4A52D1EFE18D\muv4muredir.cab are not trusted: Error 0x800b0001
    2012-06-18 20:10:46:048  960 4fc Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir\7971F918-A847-4430-9279-4A52D1EFE18D\muv4muredir.cab:
    2012-06-18 20:10:46:079  960 4fc Misc  Microsoft signed: Yes
    2012-06-18 20:10:46:079  960 4fc PT +++++++++++  PT: Synchronizing server updates  +++++++++++
    2012-06-18 20:10:46:079  960 4fc PT   + ServiceId = {7971F918-A847-4430-9279-4A52D1EFE18D}, Server URL = https://www.update.microsoft.com/v6/ClientWebService/client.asmx
    2012-06-18 20:13:07:433  960 4fc Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir\7971F918-A847-4430-9279-4A52D1EFE18D\muv4muredir.cab:
    2012-06-18 20:13:07:479  960 4fc Misc  Microsoft signed: Yes
    2012-06-18 20:13:07:589  960 4fc Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir\7971F918-A847-4430-9279-4A52D1EFE18D\muv4muredir.cab:
    2012-06-18 20:13:07:620  960 4fc Misc  Microsoft signed: Yes
    2012-06-18 20:13:07:635  960 4fc PT +++++++++++  PT: Synchronizing extended update info  +++++++++++
    2012-06-18 20:13:07:635  960 4fc PT   + ServiceId = {7971F918-A847-4430-9279-4A52D1EFE18D}, Server URL = https://www.update.microsoft.com/v6/ClientWebService/client.asmx
    2012-06-18 20:14:07:071  960 4fc Misc WARNING: Send failed with hr = 80072ee2.
    2012-06-18 20:14:07:071  960 4fc Misc WARNING: SendRequest failed with hr = 80072ee2. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
    2012-06-18 20:14:07:071  960 4fc PT   + Last proxy send request failed with hr = 0x80072EE2, HTTP status code = 0
    2012-06-18 20:14:07:071  960 4fc PT   + Caller provided credentials = No
    2012-06-18 20:14:07:071  960 4fc PT   + Impersonate flags = 0
    2012-06-18 20:14:07:071  960 4fc PT   + Possible authorization schemes used =
    2012-06-18 20:14:07:071  960 4fc PT WARNING: GetExtendedUpdateInfo failure, error = 0x80072EE2, soap client error = 5, soap error code = 0, HTTP status code = 200
    2012-06-18 20:14:07:071  960 4fc PT WARNING: PTError: 0x80072ee2
    2012-06-18 20:14:07:071  960 4fc PT WARNING: GetExtendedUpdateInfo_WithRecovery: 0x80072ee2
    2012-06-18 20:14:08:148  960 4fc PT WARNING: Sync of Extended Info: 0x80072ee2
    2012-06-18 20:14:08:148  960 4fc PT WARNING: SyncServerUpdatesInternal failed : 0x80072ee2
    2012-06-18 20:14:08:195  960 4fc Agent   * WARNING: Exit code = 0x80072EE2
    2012-06-18 20:14:08:195  960 4fc Agent *********
    2012-06-18 20:14:08:195  960 4fc Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2012-06-18 20:14:08:195  960 4fc Agent *************
    2012-06-18 20:14:08:195  960 4fc Agent WARNING: WU client failed Searching for update with error 0x80072ee2
    2012-06-18 20:14:08:319  960 e00 AU >>##  RESUMED  ## AU: Search for updates [CallId = {8A83B3B5-055F-497E-B452-92F64D934BC9}]
    2012-06-18 20:14:08:319  960 e00 AU   # WARNING: Search callback failed, result = 0x80072EE2
    2012-06-18 20:14:08:319  960 e00 AU   # WARNING: Failed to find updates with error code 80072EE2
    2012-06-18 20:14:08:319  960 e00 AU #########
    2012-06-18 20:14:08:319  960 e00 AU ##  END  ##  AU: Search for updates [CallId = {8A83B3B5-055F-497E-B452-92F64D934BC9}]

    Tuesday, June 19, 2012 4:30 AM
  • Similar situation on Windows 7 Starter. Looking into the WindowsUpdate.log I can see

    4fc Setup Determining whether a new setup handler needs to be downloaded
    2012-06-18 20:10:43:006  960 4fc Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\Handler\WuSetupV.exe:
    2012-06-18 20:10:43:037  960 4fc Misc  Microsoft signed: Yes
    2012-06-18 20:10:43:037  960 4fc Misc WARNING: Digital Signatures on file C:\Windows\SoftwareDistribution\SelfUpdate\Handler\WuSetupV.exe are not trusted: Error 0x800b0001
    2012-06-18 20:10:43:037  960 4fc Setup WARNING: Trust verification failed for WuSetupV.exe. It will be deleted and downloaded, error = 0x800B0001
    2012-06-18 20:10:43:037  960 4fc Setup SelfUpdate handler update required: Current version: 7.6.7600.256, required version: 7.6.7600.256
    2012-06-18 20:10:43:037  960 4fc Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.6.7600.256"
    2012-06-18 20:10:43:068  960 4fc Setup Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.6.7600.256" is already installed.
    2012-06-18 20:10:43:068  960 4fc Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256"
    2012-06-18 20:10:43:240  960 4fc Setup Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256" is applicable but is already staged; it will not be downloaded.
    2012-06-18 20:10:43:240  960 4fc Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256"
    2012-06-18 20:10:43:723  960 4fc Setup Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256" is already installed.
    2012-06-18 20:10:43:723  960 4fc Setup SelfUpdate check completed.  SelfUpdate is NOT required.
    2012-06-18 20:10:45:861  960 4fc Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir\7971F918-A847-4430-9279-4A52D1EFE18D\muv4muredir.cab:
    2012-06-18 20:10:45:907  960 4fc Misc  Microsoft signed: Yes
    2012-06-18 20:10:45:907  960 4fc Misc WARNING: Digital Signatures on file C:\Windows\SoftwareDistribution\WuRedir\7971F918-A847-4430-9279-4A52D1EFE18D\muv4muredir.cab are not trusted: Error 0x800b0001
    2012-06-18 20:10:46:048  960 4fc Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir\7971F918-A847-4430-9279-4A52D1EFE18D\muv4muredir.cab:
    2012-06-18 20:10:46:079  960 4fc Misc  Microsoft signed: Yes
    2012-06-18 20:10:46:079  960 4fc PT +++++++++++  PT: Synchronizing server updates  +++++++++++
    2012-06-18 20:10:46:079  960 4fc PT   + ServiceId = {7971F918-A847-4430-9279-4A52D1EFE18D}, Server URL = https://www.update.microsoft.com/v6/ClientWebService/client.asmx
    2012-06-18 20:13:07:433  960 4fc Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir\7971F918-A847-4430-9279-4A52D1EFE18D\muv4muredir.cab:
    2012-06-18 20:13:07:479  960 4fc Misc  Microsoft signed: Yes
    2012-06-18 20:13:07:589  960 4fc Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir\7971F918-A847-4430-9279-4A52D1EFE18D\muv4muredir.cab:
    2012-06-18 20:13:07:620  960 4fc Misc  Microsoft signed: Yes
    2012-06-18 20:13:07:635  960 4fc PT +++++++++++  PT: Synchronizing extended update info  +++++++++++
    2012-06-18 20:13:07:635  960 4fc PT   + ServiceId = {7971F918-A847-4430-9279-4A52D1EFE18D}, Server URL = https://www.update.microsoft.com/v6/ClientWebService/client.asmx
    2012-06-18 20:14:07:071  960 4fc Misc WARNING: Send failed with hr = 80072ee2.
    2012-06-18 20:14:07:071  960 4fc Misc WARNING: SendRequest failed with hr = 80072ee2. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
    2012-06-18 20:14:07:071  960 4fc PT   + Last proxy send request failed with hr = 0x80072EE2, HTTP status code = 0
    2012-06-18 20:14:07:071  960 4fc PT   + Caller provided credentials = No
    2012-06-18 20:14:07:071  960 4fc PT   + Impersonate flags = 0
    2012-06-18 20:14:07:071  960 4fc PT   + Possible authorization schemes used =
    2012-06-18 20:14:07:071  960 4fc PT WARNING: GetExtendedUpdateInfo failure, error = 0x80072EE2, soap client error = 5, soap error code = 0, HTTP status code = 200
    2012-06-18 20:14:07:071  960 4fc PT WARNING: PTError: 0x80072ee2
    2012-06-18 20:14:07:071  960 4fc PT WARNING: GetExtendedUpdateInfo_WithRecovery: 0x80072ee2
    2012-06-18 20:14:08:148  960 4fc PT WARNING: Sync of Extended Info: 0x80072ee2
    2012-06-18 20:14:08:148  960 4fc PT WARNING: SyncServerUpdatesInternal failed : 0x80072ee2
    2012-06-18 20:14:08:195  960 4fc Agent   * WARNING: Exit code = 0x80072EE2
    2012-06-18 20:14:08:195  960 4fc Agent *********
    2012-06-18 20:14:08:195  960 4fc Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2012-06-18 20:14:08:195  960 4fc Agent *************
    2012-06-18 20:14:08:195  960 4fc Agent WARNING: WU client failed Searching for update with error 0x80072ee2
    2012-06-18 20:14:08:319  960 e00 AU >>##  RESUMED  ## AU: Search for updates [CallId = {8A83B3B5-055F-497E-B452-92F64D934BC9}]
    2012-06-18 20:14:08:319  960 e00 AU   # WARNING: Search callback failed, result = 0x80072EE2
    2012-06-18 20:14:08:319  960 e00 AU   # WARNING: Failed to find updates with error code 80072EE2
    2012-06-18 20:14:08:319  960 e00 AU #########
    2012-06-18 20:14:08:319  960 e00 AU ##  END  ##  AU: Search for updates [CallId = {8A83B3B5-055F-497E-B452-92F64D934BC9}]

    Maybe this problem is a result of the exploit described at

    http://www.f-secure.com/weblog/archives/00002383.html

    which, in part, states that

    Flame creates a local proxy which it uses to intercept traffic to Microsoft Update. This is used to spread Flame to other machines in a local area network.
    The fake update was signed with a certificate linking up to Microsoft root, as the attackers found a way to repurpose Microsoft Terminal Server license certificates. Even this wasn't enough to spoof newer Windows versions, so they did some cutting-edge cryptographic research and came up with a completely new way to create hash collisions, enabling them to spoof the certificate. They still needed a supercomputer though. And they've been doing this silently since 2010.


    Tuesday, June 19, 2012 4:44 AM
  • OK, after a extra days of week-end, I spent quite some time with this issue yesterday and today.

    So far, I have managed to make it work for all clients, but not yet the DC. I will work on that, now.

    In summary, what I did was

    - Uninstall WSUS completely, removing the DB, log files and downloaded files. I realize this is a luxury I have because this is a brand new server.
    - Exclude the server from the WSUS Group Policy. This causes the server to get updates from MS.
    - Completely update the server. 
    - Install WSUS. The installation will fetch updates to WSUS from Microsoft (WSUS installation did not work when enforced by the same GP that would direct clients to this WSUS server, as this update procedure would fail).
    - Completely update the server again. A few new updates was available, amongst them the update CommerceCompany mentioned above.
    - Include the WSUS server in the WSUS Group Policy, again.
    - The clients started reporting quite fast. When this was confirmed, I reenabled SSL.

    For the time being, this seems to be working. I have an issue with the DC not reporting, so I'm running the same strategy of letting it update completely from MS to see if it helps. It's happening now, and I will post the results when I know more.

     

    Tuesday, June 19, 2012 11:45 AM
  • I think I'm going to open a support case with MS and let them solve it before I go through that effort.  I think they broke it, so they can fix it.
    Tuesday, June 19, 2012 1:30 PM
  • Hi.

    I've searched and found numerous issues regarding error 0x800B0001, but none that can help me. Last effort is to post a new question, here.

    Did you install
    Microsoft Security Advisory (2718704)
    Unauthorized Digital Certificates Could Allow Spoofing
    ?

    I think this revocation of the sub CAs breaks WSUS. We have the same situation with our clients.
    My guess is that is why the released the Update for WSUS SP2 and urged everyone to install it.
    To bad this broke our WSUS too, and we just restored it. Only to find out that now the cert chain is broken... *sigh*


    <hgroup></hgroup>

    Tuesday, June 19, 2012 3:17 PM
  • It was installed on my system yesterday and that's when things broke.  You restored the WSUS database or what did you restore?  If so, to what point in time?

    Thanks.

    Tuesday, June 19, 2012 3:30 PM
  • Here is WindowsUpdate.log from my client W2k8R2 SP1:

    2012-06-19	14:29:16:641	 996	1684	AU	Triggering AU detection through DetectNow API
    2012-06-19	14:29:16:641	 996	1684	AU	Triggering Online detection (interactive)
    2012-06-19	14:29:16:641	 996	490	AU	#############
    2012-06-19	14:29:16:641	 996	490	AU	## START ##  AU: Search for updates
    2012-06-19	14:29:16:641	 996	490	AU	#########
    2012-06-19	14:29:16:642	 996	490	AU	<<## SUBMITTED ## AU: Search for updates [CallId = {C4D10BE3-B7EE-47F1-84B5-8CF6A5131D4D}]
    2012-06-19	14:29:16:642	 996	1bc	Agent	*************
    2012-06-19	14:29:16:642	 996	1bc	Agent	** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2012-06-19	14:29:16:642	 996	1bc	Agent	*********
    2012-06-19	14:29:16:642	 996	1bc	Agent	  * Online = Yes; Ignore download priority = No
    2012-06-19	14:29:16:643	 996	1bc	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-19	14:29:16:643	 996	1bc	Agent	  * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2012-06-19	14:29:16:643	 996	1bc	Agent	  * Search Scope = {Machine}
    2012-06-19	14:29:16:643	 996	1bc	Setup	Checking for agent SelfUpdate
    2012-06-19	14:29:16:643	 996	1bc	Setup	Client version: Core: 7.6.7600.256  Aux: 7.6.7600.256
    2012-06-19	14:29:16:697	 996	1bc	Misc	Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
    2012-06-19	14:29:16:702	 996	1bc	Misc	 Microsoft signed: Yes
    2012-06-19	14:29:16:702	 996	1bc	Misc	WARNING: Digital Signatures on file C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab are not trusted: Error 0x800b0001
    2012-06-19	14:29:16:703	 996	1bc	Setup	WARNING: SelfUpdate check failed to download package information, error = 0x800B0001
    2012-06-19	14:29:16:703	 996	1bc	Setup	FATAL: SelfUpdate check failed, err = 0x800B0001
    2012-06-19	14:29:16:703	 996	1bc	Agent	  * WARNING: Skipping scan, self-update check returned 0x800B0001
    2012-06-19	14:29:16:703	 996	1bc	Agent	  * WARNING: Exit code = 0x800B0001
    2012-06-19	14:29:16:703	 996	1bc	Agent	*********
    2012-06-19	14:29:16:703	 996	1bc	Agent	**  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2012-06-19	14:29:16:703	 996	1bc	Agent	*************
    2012-06-19	14:29:16:703	 996	1bc	Agent	WARNING: WU client failed Searching for update with error 0x800b0001
    2012-06-19	14:29:16:704	 996	187c	AU	>>##  RESUMED  ## AU: Search for updates [CallId = {C4D10BE3-B7EE-47F1-84B5-8CF6A5131D4D}]
    2012-06-19	14:29:16:704	 996	187c	AU	  # WARNING: Search callback failed, result = 0x800B0001
    2012-06-19	14:29:16:704	 996	187c	AU	  # WARNING: Failed to find updates with error code 800B0001
    2012-06-19	14:29:16:704	 996	187c	AU	#########
    2012-06-19	14:29:16:704	 996	187c	AU	##  END  ##  AU: Search for updates [CallId = {C4D10BE3-B7EE-47F1-84B5-8CF6A5131D4D}]
    2012-06-19	14:29:16:704	 996	187c	AU	#############
    2012-06-19	14:29:16:704	 996	187c	AU	Successfully wrote event for AU health state:0
    2012-06-19	14:29:16:705	 996	187c	AU	AU setting next detection timeout to 2012-06-19 17:29:16
    2012-06-19	14:29:16:705	 996	187c	AU	Setting AU scheduled install time to 2012-06-23 14:00:00
    2012-06-19	14:29:16:705	 996	187c	AU	Successfully wrote event for AU health state:0
    2012-06-19	14:29:16:705	 996	187c	AU	Successfully wrote event for AU health state:0
    2012-06-19	14:29:21:703	 996	1bc	Report	REPORT EVENT: {050A72E6-A8FB-4557-ADEE-693955062D87}	2012-06-19 14:29:16:703+0200	1	148	101	{D67661EB-2423-451D-BF5D-13199E37DF28}	1	800b0001	SelfUpdate	Failure	Software Synchronization	Windows Update Client failed to detect with error 0x800b0001.
    2012-06-19	14:29:21:711	 996	1bc	Report	CWERReporter::HandleEvents - WER report upload completed with status 0x8
    2012-06-19	14:29:21:711	 996	1bc	Report	WER Report sent: 7.6.7600.256 0x800b0001 D67661EB-2423-451D-BF5D-13199E37DF28 Scan 101 Managed
    2012-06-19	14:29:21:712	 996	1bc	Report	CWERReporter finishing event handling. (00000000)
    2012-06-19	14:39:32:974	 996	1bc	PT	WARNING: Cached cookie has expired or new PID is available
    2012-06-19	14:39:32:974	 996	1bc	PT	Initializing simple targeting cookie, clientId = 79bed6d6-f0af-4338-96a2-d69caa0d9295, target group = , DNS name = client01.test.local
    2012-06-19	14:39:32:974	 996	1bc	PT	  Server URL = http://wsusserver.test.local/SimpleAuthWebService/SimpleAuth.asmx
    2012-06-19	14:39:33:004	 996	1bc	Report	Uploading 1 events using cached cookie, reporting URL = http://wsusserver.test.local/ReportingWebService/ReportingWebService.asmx
    2012-06-19	14:39:33:021	 996	1bc	Report	Reporter successfully uploaded 1 events.

    Tuesday, June 19, 2012 5:15 PM
  • Edin, same problem as mine.  I've opened a support case.  I'll keep everyone posted as to what they say.  Update 2718704 has already been deployed in my organization.  I don't know if removing it will solve the problem.  I'll wait until MS responds.
    Tuesday, June 19, 2012 5:19 PM
  • FYI: Uninstalling 2718704 on my Windows 2008 R2 server did not fix this problem.
    Wednesday, June 20, 2012 9:10 AM
  • I have just built a new Exchange 2010 server and this problem is occuring for me. WSUS updates fail, updates from the internet work fine. I have not yet patched the server so I can only assume that this is not being caused by a specific windows update, but by the way the latest Windows Update app itself is interfacing with WSUS itself.

    This is my WindowsUpdate.log entry:

    2012-06-20	12:06:49:779	 864	268	AU	#############
    2012-06-20	12:06:49:779	 864	268	AU	## START ##  AU: Search for updates
    2012-06-20	12:06:49:779	 864	268	AU	#########
    2012-06-20	12:06:49:779	 864	268	AU	<<## SUBMITTED ## AU: Search for updates [CallId = {481B93AA-619E-4291-816B-E515E61B7709}]
    2012-06-20	12:06:49:779	 864	160c	Agent	*************
    2012-06-20	12:06:49:779	 864	160c	Agent	** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2012-06-20	12:06:49:779	 864	160c	Agent	*********
    2012-06-20	12:06:49:779	 864	160c	Agent	  * Online = Yes; Ignore download priority = No
    2012-06-20	12:06:49:779	 864	160c	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-20	12:06:49:779	 864	160c	Agent	  * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2012-06-20	12:06:49:779	 864	160c	Agent	  * Search Scope = {Machine}
    2012-06-20	12:06:49:779	 864	160c	Setup	Checking for agent SelfUpdate
    2012-06-20	12:06:49:779	 864	160c	Setup	Client version: Core: 7.6.7600.256  Aux: 7.6.7600.256
    2012-06-20	12:06:52:088	 864	160c	Misc	Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
    2012-06-20	12:06:52:088	 864	160c	Misc	 Microsoft signed: Yes
    2012-06-20	12:06:52:088	 864	160c	Misc	WARNING: Digital Signatures on file C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab are not trusted: Error 0x800b0001
    2012-06-20	12:06:52:088	 864	160c	Setup	WARNING: SelfUpdate check failed to download package information, error = 0x800B0001
    2012-06-20	12:06:52:088	 864	160c	Setup	FATAL: SelfUpdate check failed, err = 0x800B0001
    2012-06-20	12:06:52:088	 864	160c	Agent	  * WARNING: Skipping scan, self-update check returned 0x800B0001
    2012-06-20	12:06:52:088	 864	160c	Agent	  * WARNING: Exit code = 0x800B0001
    2012-06-20	12:06:52:088	 864	160c	Agent	*********
    2012-06-20	12:06:52:088	 864	160c	Agent	**  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2012-06-20	12:06:52:088	 864	160c	Agent	*************
    2012-06-20	12:06:52:088	 864	160c	Agent	WARNING: WU client failed Searching for update with error 0x800b0001
    2012-06-20	12:06:52:088	 864	14e8	AU	>>##  RESUMED  ## AU: Search for updates [CallId = {481B93AA-619E-4291-816B-E515E61B7709}]
    2012-06-20	12:06:52:088	 864	14e8	AU	  # WARNING: Search callback failed, result = 0x800B0001
    2012-06-20	12:06:52:088	 864	14e8	AU	  # WARNING: Failed to find updates with error code 800B0001
    2012-06-20	12:06:52:088	 864	14e8	AU	#########
    2012-06-20	12:06:52:088	 864	14e8	AU	##  END  ##  AU: Search for updates [CallId = {481B93AA-619E-4291-816B-E515E61B7709}]
    2012-06-20	12:06:52:088	 864	14e8	AU	#############
    2012-06-20	12:06:52:088	 864	14e8	AU	Successfully wrote event for AU health state:0
    2012-06-20	12:06:52:088	 864	14e8	AU	AU setting next detection timeout to 2012-06-20 16:06:52
    2012-06-20	12:06:52:088	 864	14e8	AU	Successfully wrote event for AU health state:0
    2012-06-20	12:06:52:088	 864	14e8	AU	Successfully wrote event for AU health state:0
    2012-06-20	12:06:54:693	 864	160c	Report	REPORT EVENT: {10930AB2-C267-4C7C-B396-5BF3AD562E82}	2012-06-20 12:06:52:088+0100	1	148	101	{D67661EB-2423-451D-BF5D-13199E37DF28}	1	800b0001	SelfUpdate	Failure	Software Synchronization	Windows Update Client failed to detect with error 0x800b0001.
    2012-06-20	12:06:54:709	 864	160c	Report	CWERReporter::HandleEvents - WER report upload completed with status 0x8
    2012-06-20	12:06:54:709	 864	160c	Report	WER Report sent: 7.6.7600.256 0x800b0001 D67661EB-2423-451D-BF5D-13199E37DF28 Scan 101 Managed
    2012-06-20	12:06:54:709	 864	160c	Report	CWERReporter finishing event handling. (00000000)

    Right now there is not much more I can do with this. The file it's complaining about does not exist on my server "C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab". I copied one in from one of the servers that works and it still did not complete.

    I have tried stopping the Windows Update service and removing the SoftwareUpdate folder, starting again, but the same error occurs both in the app and the WindowsUpdate log file.

    Running Windows Server 2008 R2 by the way, Windows is activated successfully.

    Wednesday, June 20, 2012 11:17 AM
  • Hi folks,

                    Like most of you, I began getting this error recently when trying to install Forefront on client machines. I ran the System Update Readiness Tool, but it found no errors. In the end I followed the link mentioned here: http://blogs.technet.com/b/wsus/archive/2012/06/08/further-hardening-of-wsus-now-available.aspx 

    In step two I applied the KB 2720211 on the WSUS server; listed here:

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

     After restarting the Server, my clients could download their updates again without error. Hope it helps some folks.


    Sys Admin, Rob M

    • Proposed as answer by Edin Smlatic Saturday, June 23, 2012 6:04 PM
    • Marked as answer by Chocolate Eater Saturday, June 23, 2012 7:54 PM
    Wednesday, June 20, 2012 7:53 PM
  • Wednesday, June 20, 2012 9:15 PM
  • Hi Rob,

    Update KB 2720211  also worked fine for me. Thanks for the info.

    Friday, June 22, 2012 9:03 AM
  • I've just installed the update recommended by you and it worked like a charm. The client which has denied updating with 0x800B0001, started to report to the WSUS server fine.

    http://support.microsoft.com/kb/2720211 worked fine on  Win2k8 SP2 machine (built-in WSUS version was used, which is WSUS 3.0 SP2)


    Friday, June 22, 2012 12:44 PM
  • Same here (KB 2720211) and it's working correctly.
    Friday, June 22, 2012 1:00 PM
  • I was having the same exact issue.  Installed KB2720211 only and my clients are now checking in.  Win2k8R2 WSUS version 3.2.7600.226.

    Thanks!

    • Proposed as answer by Ali Akbari Wednesday, June 26, 2013 1:28 AM
    Friday, June 22, 2012 2:50 PM
  • I first made snapshot and backup of sql database, then stopped IIS and WSUS service and after that applied KB2720211.

    Clients are reporting now

    Thanks everyone

    • Proposed as answer by dgf667 Monday, August 06, 2012 8:55 PM
    Saturday, June 23, 2012 6:03 PM
  • Same here. I've just installed a Server 2008 R2 Standard into the environment and applied all updates directly from MS because my WSUS was busy. I tried to check for updates from WSUS afterwards and I got the same error.

    Installing the mentioned KB2720211 on the WSUS (SBS2K11) solved the issue.

    Monday, June 25, 2012 4:00 PM
  • I have this same issue, except when i try to run update KB2720211 it fails saying "A program run as part of the setup did not finish as expected". we're running WSUS 3.0 SP2 on WS2K8R2 SP1, and i've tried stopping the IIS and WSUS services before installing
    Wednesday, June 27, 2012 3:05 AM
  • I believe that I may have been a political target of the Flame virus. I realize that Flame is a weapon of war designed by Western and Israeli intelligence to be used against the Islamic Republic of Iran and other enemies of the Rothschild banking empire. Yesterday morning I rebooted my Windows 7 PC to find a suspicious windows update being installed during the boot sequence despite the fact I disabled automatic updates. I immediately checked the WindowsUpdate.log to see what was installed, and I came across several suspicious warnings and errors that suggest I may have been infected by a variant of Flame or similar malware that spoofs the windows update feature. Others have been reporting similar problems in the last 2-3 weeks.  This was found in my WindowsUpdate.log:

    2012-06-25 21:04:29:829 812 510 Setup Determining whether a new setup handler needs to be downloaded
    2012-06-25 21:04:29:836 812 510 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\Handler\WuSetupV.exe:
    2012-06-25 21:04:29:842 812 510 Misc Microsoft signed: Yes
    2012-06-25 21:04:29:842 812 510 Misc WARNING: Digital Signatures on file C:\Windows\SoftwareDistribution\SelfUpdate\Handler\WuSetupV.exe are not trusted: Error 0x800b0001
    2012-06-25 21:04:29:842 812 510 Setup WARNING: Trust verification failed for WuSetupV.exe. It will be deleted and downloaded, error = 0x800B0001
    2012-06-25 21:04:29:842 812 510 Setup SelfUpdate handler update required: Current version: 7.6.7600.256, required version: 7.6.7600.256
    2012-06-25 21:04:30:741 812 510 Setup SelfUpdate check completed. SelfUpdate is required.
    2012-06-25 21:04:30:741 812 510 Setup Downloading binaries required for SelfUpdate
    2012-06-25 21:04:30:741 812 510 Setup Downloading SelfUpdate handler WuSetupHandler.cab from http://download.windowsupdate.com/v9/1/windowsupdate/b/selfupdate/WSUS3/x64/Vista
    2012-06-25 21:04:30:752 812 510 Misc Validating signature for :\Windows\SoftwareDistribution\SelfUpdate\Handler\WuSetupHandler.cab:
    2012-06-25 21:04:30:765 812 510 Misc Microsoft signed: Yes
    2012-06-25 21:04:31:084 812 510 Setup Successfully downloaded SelfUpdate handler
    2012-06-25 21:04:31:084 812 510 Setup Download of SelfUpdate binaries succeeded
    2012-06-25 21:04:31:084 812 510 Setup Starting agent SelfUpdate
    2012-06-25 21:04:31:084 812 510 Setup Skipping installation because no critical packages are ready to install.

    On reboot Windows 7 installed the so called 'update.'

    Here is my entire WindowsUpdate.log http://www.filedropper.com/windowsupdatelogtar

    "The full mechanism isn't yet completely analyzed, but Flame has a module which appears to attempt to do a man-in-the-middle attack on the Microsoft Update or Windows Server Update Services (WSUS) system. If successful, the attack drops a file called WUSETUPV.EXE to the target computer. This file is signed by Microsoft with a certificate that is chained up to Microsoft root. Except it isn't signed really by Microsoft."

    Source: http://www.f-secure.com/weblog/archives/00002377.html

    "We have confirmed that Flame uses a yet unknown MD5 chosen-prefix collision attack," Marc Stevens and B.M.M. de Weger wrote in an e-mail posted to a cryptography discussion group earlier this week. "The collision attack itself is very interesting from a scientific viewpoint, and there are already some practical implications." 

    Source: http://arstechnica.com/security/2012/06/flame-crypto-breakthrough/

    "New research has shown that it can be run at a rate close to 1 million checks per second on COTS GPU hardware, which means that it is as prone to brute-force attacks as the DES based UNIX crypt was back in 1995: Any 8 character password can be found in a couple of days." 

    Source: http://phk.freebsd.dk/sagas/md5crypt_eol.html

    While my computer was exhibiting symptoms of the Flame variant, my Gigabyte GV-R485-512H-B, ATI 4850 video card P/N: 113-B5012-105 (Bios Revision 011.004.000.000.029193) was overheating (flaming hot if you prefer) and the fan was out of control,  speeding up and down... my computer crashed half a dozen times. I had to flash the bios to fix the problem.   Can variants of Flame use the GPU of infected machines to crack encryption?


    Thursday, June 28, 2012 1:57 AM
  • Hi All

    I am also encountering similar kinds of problem.
    When my clients mainly (Windows 2008 R2) are updated directly from internet they are getting the WUA client version 7.6.7600.256. But when I point to my current WSUS SErver 3.0 SP1(Version: 3.1.6001.65) these client are not reporting any status. They  get the following error message in WindowsUpdate log file:

    2012-06-29 07:10:49:175  860 2180 Setup Checking for agent SelfUpdate
    2012-06-29 07:10:49:188  860 2180 Setup Client version: Core: 7.6.7600.256  Aux: 7.6.7600.256
    2012-06-29 07:10:49:297  860 2180 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
    2012-06-29 07:10:49:301  860 2180 Misc  Microsoft signed: Yes
    2012-06-29 07:10:49:301  860 2180 Misc WARNING: Digital Signatures on file C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab are not trusted: Error 0x800b0001
    2012-06-29 07:10:49:301  860 2180 Setup WARNING: SelfUpdate check failed to download package information, error = 0x800B0001
    2012-06-29 07:10:49:301  860 2180 Setup FATAL: SelfUpdate check failed, err = 0x800B0001
    2012-06-29 07:10:49:302  860 2180 Agent   * WARNING: Skipping scan, self-update check returned 0x800B0001
    2012-06-29 07:10:49:302  860 2180 Agent   * WARNING: Exit code = 0x800B0001


    Kindly suggest what should be my next couse of action..
    Shall I upgrade my WSUS Server from 3.0 Sp1 to 3.0 Sp2 and then apply the KB2720211.
    But I am really apprehensive of the issues encountered with KB2720211.

    Any suggestion would be much appreciated...

    Friday, June 29, 2012 2:12 AM
  • I WSUS 3.0 SP2 (Version: 3.2.7600.226)

    Two clients, Windows XP SP3 and Windows Server 2008 R2 SP1 x64, are reporting Windows Update Client failed to detect with error 0x800b0001 when contacting to WSUS server.

    If I try to connect to Microsoft Update on the Internet, everything works perfectly.

    I didn't install http://support.microsoft.com/kb/2720211 on my WSUS

    Any idea what can I do next?

    Install KB2720122 on the WSUS server.

    Almost certainly your two clients were sent to WU/MU and got the new WUAgent as a result. The new WUAgent CANNOT communicate with the OLD WSUS server.

    -or- (and most certainly NOT recommended) -- you can downgrade those two systems to the v7.4 WUAgent by running the v7.4 installer with the /wuforce flag.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Product Manager, SolarWinds
    Microsoft MVP - Software Distribution (2005-2012)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin

    Sunday, July 01, 2012 10:34 PM
    Moderator
  • I WSUS 3.0 SP2 (Version: 3.2.7600.226)

    Two clients, Windows XP SP3 and Windows Server 2008 R2 SP1 x64, are reporting Windows Update Client failed to detect with error 0x800b0001 when contacting to WSUS server.

    If I try to connect to Microsoft Update on the Internet, everything works perfectly.

    I didn't install http://support.microsoft.com/kb/2720211 on my WSUS

    Any idea what can I do next?

    Install KB2720122 on the WSUS server.

    Almost certainly your two clients were sent to WU/MU and got the new WUAgent as a result. The new WUAgent CANNOT communicate with the OLD WSUS server.

    -or- (and most certainly NOT recommended) -- you can downgrade those two systems to the v7.4 WUAgent by running the v7.4 installer with the /wuforce flag.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Product Manager, SolarWinds
    Microsoft MVP - Software Distribution (2005-2012)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin

    hi

    Our wsus server is  3.2.7600.226 version

    Recently i discovered that computers who Join to wsus server are not repporting with note "the computer has not reported status yet"

    all other server getting update and all fine

    the log from one of the problematics server:


      840 c74 Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
     840 c74 Agent *********
      840 c74 Agent   * Online = Yes; Ignore download priority = No
      840 c74 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"
     840 c74 Agent   * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
      840 c74 Agent   * Search Scope = {Machine}
      840 c74 Setup Checking for agent SelfUpdate
      840 c74 Setup Client version: Core: 7.6.7600.256  Aux: 7.6.7600.256
     840 c74 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
      840 c74 Misc  Microsoft signed: Yes
      840 c74 Misc WARNING: Digital Signatures on file C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab are not trusted: Error 0x800b0001
      840 c74 Setup WARNING: SelfUpdate check failed to download package information, error = 0x800B0001
      840 c74 Setup FATAL: SelfUpdate check failed, err = 0x800B0001
      840 c74 Agent   * WARNING: Skipping scan, self-update check returned 0x800B0001
      840 c74 Agent   * WARNING: Exit code = 0x800B0001
      840 c74 Agent *********
      840 c74 Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
      840 c74 Agent 





    • Edited by Noah Afgin Monday, August 06, 2012 11:11 AM
    • Proposed as answer by Noah Afgin Monday, August 06, 2012 1:49 PM
    • Unproposed as answer by Noah Afgin Monday, August 06, 2012 1:49 PM
    Monday, August 06, 2012 11:03 AM
  • Thank you for this. After spending most of a day trying various different approaches, it was this simple answer that helped me. Seems not stopping IIS and WSUSService leaves files 'locked' and unable to be updated and WSUS is unable to sync with Windows Update on the Internet. Stopping these services and installing the hotfix worked a treat and WSUS can now sync with Windows Update.
    • Edited by dgf667 Monday, August 06, 2012 8:54 PM
    Monday, August 06, 2012 8:54 PM
  • Thanks alot for all

    Wsus is now Ok after installing the update kb2720211 .

    and all servers that did not show status report are now reporting

    Noah Afgin System administrator

    • Proposed as answer by Danilo Beserra Thursday, September 27, 2012 4:34 PM
    Tuesday, August 07, 2012 9:31 AM
  • Gentlemen

    I performed the installation of KB2720211, customers returned the machines to report the server

    Windows 2008 R2, WSUS SP2.

    Thursday, September 27, 2012 4:41 PM
  • This link worked for me !!!! 

    That worked really fantastic !!

    Follow it "As- Is"

    http://social.technet.microsoft.com/Forums/en-US/winserverwsus/thread/a47039d9-4d45-4a61-aa26-6100aeffc1f0

    • Proposed as answer by Chintan Vyas Tuesday, December 11, 2012 7:26 PM
    Monday, December 03, 2012 4:39 PM