locked
Windows Clients don't update after re-install of WSUS RRS feed

  • Question

  • Hi,

    I had to reinstall WSUS SP2 on my SBS 2001 server. All seems well the WSUS downloads updates, I've approve all to be installed, and WSUS reports which Clints have not installed updates.

    However the client themselves think they are up to date and hence won't donnload any updates from WSUS.

    Any ideas about whats going on?

    Sunday, July 1, 2012 9:54 AM

Answers

  • Run the following lines on a client computer from an administrative command prompt
    net stop wuauserv
    REG DELETE "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v AccountDomainSid /f
    REG DELETE "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v PingID /f
    REG DELETE "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v SusClientId /f
    net start wuauserv
    wuauclt /resetauthorization /detectnow
    


    Jeremy

    • Marked as answer by Sean Zhu - Monday, July 9, 2012 6:40 AM
    Tuesday, July 3, 2012 5:18 AM
  • and something I've found I had to do several times just recently is go into %windir%\SoftwareDistribution\Download and delete everything, but NOT the folder itself.

    Theory suggests you should 1st stop 'update services' but I haven't needed to.

    The other thing is the recent update to WSUS itself. Is the WSUS patched to this recent release? If WSUS is not patched you can get a conflict in the update client version.

    _some_ have had issues allowing the update to WSUS from WSUS itself. I believe thecurrent suggestion is to download http://support.microsoft.com/kb/2720211 as a 'standalone' and apply it manually.

    • Marked as answer by Sean Zhu - Monday, July 9, 2012 6:40 AM
    Tuesday, July 3, 2012 5:58 AM
  • You can also check the following thread on the same error message:

    0x8024400E error with WSUS SP2

    http://social.technet.microsoft.com/Forums/en-US/winserverwsus/thread/8c023438-5b65-42b6-b276-071fc5f16ecf/

    If the issue still cannot be resolved, you can post to WSUS forum:

    http://social.technet.microsoft.com/Forums/en-US/winserverwsus/threads

    Thanks.


    Sean Zhu

    TechNet Community Support

    • Marked as answer by Sean Zhu - Monday, July 9, 2012 6:41 AM
    Thursday, July 5, 2012 8:10 AM

All replies

  • Would SBS2001 be SBS2003, SBS2008 or SBS2011?

    Can you post the last hundred or so lines from C:\Windows\WindowsUpdate.log on one of the failing client machines?

    Jim

    Sunday, July 1, 2012 10:56 AM
  • The Server is SBS 2011. Here is the log entries;

    2012-06-25 09:05:11:023  380 4890 Misc  Microsoft signed: Yes
    2012-06-25 09:05:11:039  380 4890 Setup Determining whether a new setup handler needs to be downloaded
    2012-06-25 09:05:11:039  380 4890 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\Handler\WuSetupV.exe:
    2012-06-25 09:05:11:039  380 4890 Misc  Microsoft signed: Yes
    2012-06-25 09:05:11:039  380 4890 Setup SelfUpdate handler update NOT required: Current version: 7.4.7600.226, required version: 7.4.7600.226
    2012-06-25 09:05:11:039  380 4890 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.4.7600.226"
    2012-06-25 09:05:11:491  380 4890 Setup Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.4.7600.226" is already installed.
    2012-06-25 09:05:11:491  380 4890 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.4.7600.226"
    2012-06-25 09:05:11:523  380 4890 Setup Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.4.7600.226" is already installed.
    2012-06-25 09:05:11:523  380 4890 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.4.7600.226"
    2012-06-25 09:05:11:569  380 4890 Setup Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.4.7600.226" is already installed.
    2012-06-25 09:05:11:569  380 4890 Setup SelfUpdate check completed.  SelfUpdate is NOT required.
    2012-06-25 09:05:12:568  380 4890 PT +++++++++++  PT: Synchronizing server updates  +++++++++++
    2012-06-25 09:05:12:568  380 4890 PT   + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://MEEKSSVER:8530/ClientWebService/client.asmx
    2012-06-25 09:05:12:599  380 4890 PT WARNING: Cached cookie has expired or new PID is available
    2012-06-25 09:05:12:599  380 4890 PT Initializing simple targeting cookie, clientId = 2eadea24-c6cd-4fae-8719-7403bf7ea2a5, target group = , DNS name = meekssver.markco.local
    2012-06-25 09:05:12:599  380 4890 PT   Server URL = http://MEEKSSVER:8530/SimpleAuthWebService/SimpleAuth.asmx
    2012-06-25 09:05:12:615  380 4890 PT WARNING: GetAuthorizationCookie failure, error = 0x8024400E, soap client error = 7, soap error code = 400, HTTP status code = 200
    2012-06-25 09:05:12:615  380 4890 PT WARNING: SOAP Fault: 0x000190
    2012-06-25 09:05:12:615  380 4890 PT WARNING:     faultstring:System.Web.Services.Protocols.SoapException: Fault occurred
       at Microsoft.UpdateServices.Internal.SimpleAuth..ctor()
    2012-06-25 09:05:12:615  380 4890 PT WARNING:     ErrorCode:InternalServerError(5)
    2012-06-25 09:05:12:615  380 4890 PT WARNING:     Message:(null)
    2012-06-25 09:05:12:615  380 4890 PT WARNING:     Method:"http://www.microsoft.com/SoftwareDistribution/Server/SimpleAuthWebService/GetAuthorizationCookie"
    2012-06-25 09:05:12:615  380 4890 PT WARNING:     ID:ab9d7acb-c501-4a03-90b6-9538d2a182be
    2012-06-25 09:05:12:615  380 4890 PT WARNING: Failed to initialize Simple Targeting Cookie: 0x8024400e
    2012-06-25 09:05:12:615  380 4890 PT WARNING: PopulateAuthCookies failed: 0x8024400e
    2012-06-25 09:05:12:615  380 4890 PT WARNING: RefreshCookie failed: 0x8024400e
    2012-06-25 09:05:12:615  380 4890 PT WARNING: RefreshPTState failed: 0x8024400e
    2012-06-25 09:05:12:615  380 4890 PT WARNING: Sync of Updates: 0x8024400e
    2012-06-25 09:05:12:615  380 4890 PT WARNING: SyncServerUpdatesInternal failed: 0x8024400e
    2012-06-25 09:05:12:615  380 4890 Agent   * WARNING: Failed to synchronize, error = 0x8024400E
    2012-06-25 09:05:12:615  380 4890 Agent   * WARNING: Exit code = 0x8024400E
    2012-06-25 09:05:12:615  380 4890 Agent *********
    2012-06-25 09:05:12:615  380 4890 Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2012-06-25 09:05:12:615  380 4890 Agent *************
    2012-06-25 09:05:12:615  380 4890 Agent WARNING: WU client failed Searching for update with error 0x8024400e
    2012-06-25 09:05:12:630  380 4b7c AU >>##  RESUMED  ## AU: Search for updates [CallId = {EC1F9F9C-C5EC-4E85-83FC-55130D85EC30}]
    2012-06-25 09:05:12:630  380 4b7c AU   # WARNING: Search callback failed, result = 0x8024400E
    2012-06-25 09:05:12:630  380 4b7c AU   # WARNING: Failed to find updates with error code 8024400E
    2012-06-25 09:05:12:630  380 4b7c AU #########
    2012-06-25 09:05:12:630  380 4b7c AU ##  END  ##  AU: Search for updates [CallId = {EC1F9F9C-C5EC-4E85-83FC-55130D85EC30}]
    2012-06-25 09:05:12:630  380 4b7c AU #############
    2012-06-25 09:05:12:630  380 4b7c AU Successfully wrote event for AU health state:0
    2012-06-25 09:05:12:630  380 4b7c AU AU setting next detection timeout to 2012-06-25 08:58:27
    2012-06-25 09:05:12:630  380 4b7c AU Successfully wrote event for AU health state:0
    2012-06-25 09:05:12:630  380 4b7c AU Successfully wrote event for AU health state:0
    2012-06-25 09:05:17:622  380 4890 Report REPORT EVENT: {9FB1B713-7B67-4EE7-ADA6-11A3D3F91495} 2012-06-25 09:05:12:615+0100 1 148 101 {00000000-0000-0000-0000-000000000000} 0 8024400e AutomaticUpdates Failure Software Synchronization Windows Update Client failed to detect with error 0x8024400e.
    2012-06-25 09:05:17:622  380 4890 Report CWERReporter::HandleEvents - WER report upload completed with status 0x8
    2012-06-25 09:05:17:622  380 4890 Report WER Report sent: 7.5.7601.17514 0x8024400e 00000000-0000-0000-0000-000000000000 Scan 101 Managed
    2012-06-25 09:05:17:622  380 4890 Report CWERReporter finishing event handling. (00000000)
    2012-06-25 09:07:38:293  380 4890 PT WARNING: Cached cookie has expired or new PID is available
    2012-06-25 09:07:38:293  380 4890 PT Initializing simple targeting cookie, clientId = 2eadea24-c6cd-4fae-8719-7403bf7ea2a5, target group = , DNS name = meekssver.markco.local
    2012-06-25 09:07:38:293  380 4890 PT   Server URL = http://MEEKSSVER:8530/SimpleAuthWebService/SimpleAuth.asmx
    2012-06-25 09:07:38:309  380 4890 PT WARNING: GetAuthorizationCookie failure, error = 0x8024400E, soap client error = 7, soap error code = 400, HTTP status code = 200
    2012-06-25 09:07:38:309  380 4890 PT WARNING: SOAP Fault: 0x000190
    2012-06-25 09:07:38:309  380 4890 PT WARNING:     faultstring:System.Web.Services.Protocols.SoapException: Fault occurred
       at Microsoft.UpdateServices.Internal.SimpleAuth..ctor()
    2012-06-25 09:07:38:309  380 4890 PT WARNING:     ErrorCode:InternalServerError(5)
    2012-06-25 09:07:38:309  380 4890 PT WARNING:     Message:(null)
    2012-06-25 09:07:38:309  380 4890 PT WARNING:     Method:"http://www.microsoft.com/SoftwareDistribution/Server/SimpleAuthWebService/GetAuthorizationCookie"
    2012-06-25 09:07:38:309  380 4890 PT WARNING:     ID:b0c868f2-f5ae-436f-a72d-b75322ef2658
    2012-06-25 09:07:38:309  380 4890 PT WARNING: Failed to initialize Simple Targeting Cookie: 0x8024400e
    2012-06-25 09:07:38:309  380 4890 PT WARNING: PopulateAuthCookies failed: 0x8024400e
    2012-06-25 09:07:38:309  380 4890 PT WARNING: RefreshCookie failed: 0x8024400e
    2012-06-25 09:07:38:309  380 4890 PT WARNING: RefreshPTState failed: 0x8024400e
    2012-06-25 09:07:38:309  380 4890 PT WARNING: PTError: 0x8024400e
    2012-06-25 09:07:38:309  380 4890 Report WARNING: Reporter failed to upload events with hr = 8024400e.
    2012-06-25 09:26:28:398  380 3b4 PT WARNING: Cached cookie has expired or new PID is available
    2012-06-25 09:26:28:398  380 3b4 PT Initializing simple targeting cookie, clientId = 2eadea24-c6cd-4fae-8719-7403bf7ea2a5, target group = , DNS name = meekssver.markco.local
    2012-06-25 09:26:28:398  380 3b4 PT   Server URL = http://MEEKSSVER:8530/SimpleAuthWebService/SimpleAuth.asmx
    2012-06-25 09:26:28:414  380 3b4 PT WARNING: GetAuthorizationCookie failure, error = 0x8024400E, soap client error = 7, soap error code = 400, HTTP status code = 200
    2012-06-25 09:26:28:414  380 3b4 PT WARNING: SOAP Fault: 0x000190
    2012-06-25 09:26:28:414  380 3b4 PT WARNING:     faultstring:System.Web.Services.Protocols.SoapException: Fault occurred
       at Microsoft.UpdateServices.Internal.SimpleAuth..ctor()
    2012-06-25 09:26:28:414  380 3b4 PT WARNING:     ErrorCode:InternalServerError(5)
    2012-06-25 09:26:28:414  380 3b4 PT WARNING:     Message:(null)
    2012-06-25 09:26:28:414  380 3b4 PT WARNING:     Method:"http://www.microsoft.com/SoftwareDistribution/Server/SimpleAuthWebService/GetAuthorizationCookie"
    2012-06-25 09:26:28:414  380 3b4 PT WARNING:     ID:c45df2b9-7c23-48cf-945a-5a2e46df3008
    2012-06-25 09:26:28:414  380 3b4 PT WARNING: Failed to initialize Simple Targeting Cookie: 0x8024400e
    2012-06-25 09:26:28:414  380 3b4 PT WARNING: PopulateAuthCookies failed: 0x8024400e
    2012-06-25 09:26:28:414  380 3b4 PT WARNING: RefreshCookie failed: 0x8024400e
    2012-06-25 09:26:28:414  380 3b4 PT WARNING: RefreshPTState failed: 0x8024400e
    2012-06-25 09:26:28:414  380 3b4 PT WARNING: PTError: 0x8024400e
    2012-06-25 09:26:28:414  380 3b4 Report WARNING: Reporter failed to upload events with hr = 8024400e.
    2012-06-25 09:47:40:483  380 4164 PT WARNING: Cached cookie has expired or new PID is available
    2012-06-25 09:47:40:483  380 4164 PT Initializing simple targeting cookie, clientId = 2eadea24-c6cd-4fae-8719-7403bf7ea2a5, target group = , DNS name = meekssver.markco.local
    2012-06-25 09:47:40:483  380 4164 PT   Server URL = http://MEEKSSVER:8530/SimpleAuthWebService/SimpleAuth.asmx
    2012-06-25 09:47:40:498  380 4164 PT WARNING: GetAuthorizationCookie failure, error = 0x8024400E, soap client error = 7, soap error code = 400, HTTP status code = 200
    2012-06-25 09:47:40:498  380 4164 PT WARNING: SOAP Fault: 0x000190
    2012-06-25 09:47:40:498  380 4164 PT WARNING:     faultstring:System.Web.Services.Protocols.SoapException: Fault occurred
       at Microsoft.UpdateServices.Internal.SimpleAuth..ctor()
    2012-06-25 09:47:40:498  380 4164 PT WARNING:     ErrorCode:InternalServerError(5)
    2012-06-25 09:47:40:498  380 4164 PT WARNING:     Message:(null)
    2012-06-25 09:47:40:498  380 4164 PT WARNING:     Method:"http://www.microsoft.com/SoftwareDistribution/Server/SimpleAuthWebService/GetAuthorizationCookie"
    2012-06-25 09:47:40:498  380 4164 PT WARNING:     ID:6e5ab68e-305c-443e-b218-86b8392f0a8f
    2012-06-25 09:47:40:498  380 4164 PT WARNING: Failed to initialize Simple Targeting Cookie: 0x8024400e
    2012-06-25 09:47:40:498  380 4164 PT WARNING: PopulateAuthCookies failed: 0x8024400e
    2012-06-25 09:47:40:498  380 4164 PT WARNING: RefreshCookie failed: 0x8024400e
    2012-06-25 09:47:40:498  380 4164 PT WARNING: RefreshPTState failed: 0x8024400e
    2012-06-25 09:47:40:498  380 4164 PT WARNING: PTError: 0x8024400e
    2012-06-25 09:47:40:498  380 4164 Report WARNING: Reporter failed to upload events with hr = 8024400e.
    2012-06-25 09:58:27:658  380 3010 AU #############
    2012-06-25 09:58:27:658  380 3010 AU ## START ##  AU: Search for updates
    2012-06-25 09:58:27:658  380 3010 AU #########

    Sunday, July 1, 2012 11:02 AM
  • WARNING: GetAuthorizationCookie failure, error = 0x8024400E, soap client error = 7, soap error code = 400, HTTP status code = 200

    Doesn't look good. Try running the appropriate BPA, and also compare the IIS settings for the WSuS branches with another SBS2011 box, as the error appears to lie in IIS.

    Jim

    EDIT: PS: what symptoms triggered you to uninstall it?
    Sunday, July 1, 2012 11:06 AM
  • Anything of use here?

    Jim

    Sunday, July 1, 2012 12:13 PM
  • Hi,

    The WSUS BPA just says WSUS should not be installed on a Domain Controller. As this as a single Server SBS2011 install that not very helpful.

    The original problem arose when I had a power failure that some for some reason was not caught properly by the UPS. The original issue was with MS Exchange, it stop accepting incoming emails and I had to delete its database queues. It did not notice the issue with the WSUS installation until a week or so later when I was advised to try a reinstall which required some manual cleaning of registry keys to be successful.

    BPA for IIS reports no relevant issues.

    Sunday, July 1, 2012 2:15 PM
  • Tried that.

    Does not seem to have made any difference

    Sunday, July 1, 2012 2:36 PM
  • For iis settings you can refer http://blogs.technet.com/b/sus/archive/2009/02/19/troubleshooting-guide-for-issues-where-wsus-clients-are-not-reporting-in.aspx
    Sunday, July 1, 2012 6:03 PM
  • Have you got WSUS showing up in the SBS Console and can you chage the settings  from there?

    If you can, ensure the computers are added to the WSUS groups. (Client or Server) if these do not exist, WSUS will not work correctly with the console and you will need to add them in manually.

    I had to do this on SBS 2008 and I needed to add the groups manually, these are:

    Update Services Client Computers

    Update Services Server Computers

    Update Services Excluded Computers

    Not sure if these are the same in SBS 2011.

    Monday, July 2, 2012 9:25 AM
  • Run the following lines on a client computer from an administrative command prompt
    net stop wuauserv
    REG DELETE "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v AccountDomainSid /f
    REG DELETE "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v PingID /f
    REG DELETE "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v SusClientId /f
    net start wuauserv
    wuauclt /resetauthorization /detectnow
    


    Jeremy

    • Marked as answer by Sean Zhu - Monday, July 9, 2012 6:40 AM
    Tuesday, July 3, 2012 5:18 AM
  • and something I've found I had to do several times just recently is go into %windir%\SoftwareDistribution\Download and delete everything, but NOT the folder itself.

    Theory suggests you should 1st stop 'update services' but I haven't needed to.

    The other thing is the recent update to WSUS itself. Is the WSUS patched to this recent release? If WSUS is not patched you can get a conflict in the update client version.

    _some_ have had issues allowing the update to WSUS from WSUS itself. I believe thecurrent suggestion is to download http://support.microsoft.com/kb/2720211 as a 'standalone' and apply it manually.

    • Marked as answer by Sean Zhu - Monday, July 9, 2012 6:40 AM
    Tuesday, July 3, 2012 5:58 AM
  • You can also check the following thread on the same error message:

    0x8024400E error with WSUS SP2

    http://social.technet.microsoft.com/Forums/en-US/winserverwsus/thread/8c023438-5b65-42b6-b276-071fc5f16ecf/

    If the issue still cannot be resolved, you can post to WSUS forum:

    http://social.technet.microsoft.com/Forums/en-US/winserverwsus/threads

    Thanks.


    Sean Zhu

    TechNet Community Support

    • Marked as answer by Sean Zhu - Monday, July 9, 2012 6:41 AM
    Thursday, July 5, 2012 8:10 AM