locked
0x8024500c Error on W10 1607 clients with WSUS RRS feed

  • Question

  • Dear,

    Our environment: WSUS Server 2012R2 and W10 1607.

    Situation:

    What happend was following: On Tuesday last week I synced our main WSUS which downloads from Internet, some updates came in (creators update, some cumulative updates, silverlight, flash etc) I approved the updates (except the creators one) for our "test update computers". Then a lot of clients started to downloading this updates from the internet instead of the WSUS server. It was so heavy that we needed to block it on our proxy servers.

    After this I also set the GPO that they are not allowed to connect to internet ressources. And now they do not update anymore at all. They check for round about 30 seconds and then they stop with the error 0x8024500c

    Here is the LOG from one of the clients:

    2017.04.19 11:56:37.3200266 744   13504 Misc            Got WSUS Client/Server URL: http://vre12026:8530/ClientWebService/client.asmx"";
    2017.04.19 11:56:37.3200730 744   13504 ProtocolTalker  OK to reuse existing configuration
    2017.04.19 11:56:37.3200779 744   13504 ProtocolTalker  Existing cookie is valid, just use it
    2017.04.19 11:56:37.3200791 744   13504 ProtocolTalker  PTInfo: Server requested registration
    2017.04.19 11:56:37.3523803 744   13504 Misc            Got WSUS Reporting URL: http://vre12026:8530/ReportingWebService/ReportingWebService.asmx"";
    2017.04.19 11:56:37.3525743 744   13504 WebServices     Auto proxy settings for this web service call.
    2017.04.19 11:57:39.7121371 744   13504 Shared          Effective power state: AC
    2017.04.19 11:57:40.7270245 744   13504 Shared          Effective power state: AC
    2017.04.19 11:57:41.7744600 744   13504 Shared          Effective power state: AC
    2017.04.19 11:57:42.8102861 744   13504 Shared          Effective power state: AC
    2017.04.19 11:57:59.6265982 744   7660  ComApi          * START *   Init Search ClientId = UpdateOrchestrator
    2017.04.19 11:57:59.6266052 744   7660  ComApi          * START *   Search ClientId = UpdateOrchestrator
    2017.04.19 11:57:59.6602577 744   7660  Agent           * START * Queueing Finding updates [CallerId = UpdateOrchestrator  Id = 8]
    2017.04.19 11:57:59.6602663 744   7660  Agent           Removing service 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 from sequential scan list
    2017.04.19 11:57:59.6602708 744   7660  Agent           Service 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 is not in sequential scan list
    2017.04.19 11:57:59.6602758 744   7660  Agent           Added service 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 to sequential scan list
    2017.04.19 11:57:59.6603197 744   7660  ComApi          Search ClientId = UpdateOrchestrator
    2017.04.19 11:57:59.6604009 744   12952 Agent           Service 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 is in sequential scan list
    2017.04.19 11:57:59.6763012 744   9040  Agent           * END * Queueing Finding updates [CallerId = UpdateOrchestrator  Id = 8]
    2017.04.19 11:57:59.6900214 744   9040  Agent           * START * Finding updates CallerId = UpdateOrchestrator  Id = 8
    2017.04.19 11:57:59.6900226 744   9040  Agent           Online = Yes; AllowCachedResults = No; Ignore download priority = No
    2017.04.19 11:57:59.6900235 744   9040  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""
    2017.04.19 11:57:59.6900284 744   9040  Agent           ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2017.04.19 11:57:59.6900288 744   9040  Agent           Search Scope = {Machine}
    2017.04.19 11:57:59.6900337 744   9040  Agent           Caller SID for Applicability: S-1-5-21-119551109-2424701800-2670629823-6720
    2017.04.19 11:57:59.6900345 744   9040  Agent           ProcessDriverDeferrals is set
    2017.04.19 11:57:59.6900345 744   9040  Agent           RegisterService is set
    2017.04.19 11:57:59.6955513 744   9040  Agent           Blocking Windows content for WUfB
    2017.04.19 11:57:59.6967550 744   9040  Misc            Got WSUS Client/Server URL: http://vre12026:8530/ClientWebService/client.asmx"";
    2017.04.19 11:58:00.4654502 744   9040  ProtocolTalker  ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://vre12026:8530/ClientWebService/client.asmx
    2017.04.19 11:58:00.4656845 744   9040  ProtocolTalker  OK to reuse existing configuration
    2017.04.19 11:58:00.4656886 744   9040  ProtocolTalker  Existing cookie is valid, just use it
    2017.04.19 11:58:00.4656894 744   9040  ProtocolTalker  PTInfo: Server requested registration
    2017.04.19 11:58:00.4978137 744   9040  Agent           Update filtered by policy: 6964AAB4-C5B5-43BD-A17D-FFB4346A8E1D.100
    2017.04.19 11:58:01.6469408 744   9040  WebServices     Auto proxy settings for this web service call.
    2017.04.19 11:58:01.7266028 744   9040  Agent           Update filtered by policy: 6964AAB4-C5B5-43BD-A17D-FFB4346A8E1D.100
    2017.04.19 11:58:01.7562438 744   9040  ProtocolTalker  PTInfo: syncing with server using normal query
    2017.04.19 11:58:01.7916953 744   9040  ProtocolTalker  SyncUpdates round trips: 2
    2017.04.19 11:58:01.8461409 744   9040  Agent           Update filtered by policy: 6964AAB4-C5B5-43BD-A17D-FFB4346A8E1D.100
    2017.04.19 11:58:01.8720633 744   9040  Agent           Update filtered by policy: 6964AAB4-C5B5-43BD-A17D-FFB4346A8E1D.100
    2017.04.19 11:58:03.0516958 744   9040  EEHandler       DeterminePatchSequence succeeded but status indicated an error 0x00000000
    2017.04.19 11:58:04.0074094 744   9040  EEHandler       DeterminePatchSequence succeeded but status indicated an error 0x00000000
    2017.04.19 11:58:13.2376052 744   9040  EEHandler       DeterminePatchSequence succeeded but status indicated an error 0x00000000
    2017.04.19 11:58:13.9754349 744   9040  EEHandler       DeterminePatchSequence succeeded but status indicated an error 0x00000000
    2017.04.19 11:58:30.0208056 744   9040  EEHandler       DeterminePatchSequence succeeded but status indicated an error 0x00000000
    2017.04.19 11:58:31.6758068 744   9040  EEHandler       DeterminePatchSequence succeeded but status indicated an error 0x00000000
    2017.04.19 11:58:32.2028787 744   9040  EEHandler       DeterminePatchSequence succeeded but status indicated an error 0x00000000
    2017.04.19 11:58:32.7272588 744   9040  Agent           Found 0 updates and 87 categories in search; evaluated appl. rules of 2212 out of 2895 deployed entities
    2017.04.19 11:58:32.7778713 744   9040  Agent           * END * Finding updates CallerId = UpdateOrchestrator  Id = 8
    2017.04.19 11:58:32.7830647 744   2704  ComApi          *RESUMED* Search ClientId = UpdateOrchestrator
    2017.04.19 11:58:32.7837207 744   2704  ComApi          Updates found = 0
    2017.04.19 11:58:32.7837216 744   2704  ComApi          * END *   Search ClientId = UpdateOrchestrator
    2017.04.19 11:58:32.7842053 744   7660  ComApi          ISusInternal:: DisconnectCall failed, hr=8024000C
    2017.04.19 11:58:32.8447681 744   7660  ComApi          * START *   Init Search ClientId = UpdateOrchestrator
    2017.04.19 11:58:32.8447718 744   7660  ComApi          * START *   Search ClientId = UpdateOrchestrator
    2017.04.19 11:58:32.8683513 744   7660  Agent           * START * Queueing Finding updates [CallerId = UpdateOrchestrator  Id = 9]
    2017.04.19 11:58:32.8683575 744   7660  Agent           Removing service 9482F4B4-E343-43B6-B170-9A65BC822C77 from sequential scan list
    2017.04.19 11:58:32.8683616 744   7660  Agent           Service 9482F4B4-E343-43B6-B170-9A65BC822C77 is not in sequential scan list
    2017.04.19 11:58:32.8683690 744   7660  Agent           Added service 9482F4B4-E343-43B6-B170-9A65BC822C77 to sequential scan list
    2017.04.19 11:58:32.8684112 744   7660  ComApi          Search ClientId = UpdateOrchestrator
    2017.04.19 11:58:32.8685844 744   12952 Agent           Service 9482F4B4-E343-43B6-B170-9A65BC822C77 is in sequential scan list
    2017.04.19 11:58:32.8799296 744   12768 Agent           * END * Queueing Finding updates [CallerId = UpdateOrchestrator  Id = 9]
    2017.04.19 11:58:32.8906307 744   12768 Agent           * START * Finding updates CallerId = UpdateOrchestrator  Id = 9
    2017.04.19 11:58:32.8906324 744   12768 Agent           Online = Yes; AllowCachedResults = No; Ignore download priority = No
    2017.04.19 11:58:32.8906332 744   12768 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""
    2017.04.19 11:58:32.8906402 744   12768 Agent           ServiceID = {9482F4B4-E343-43B6-B170-9A65BC822C77} Windows Update
    2017.04.19 11:58:32.8906410 744   12768 Agent           Search Scope = {Machine}
    2017.04.19 11:58:32.8906455 744   12768 Agent           Caller SID for Applicability: S-1-5-21-119551109-2424701800-2670629823-6720
    2017.04.19 11:58:32.8906463 744   12768 Agent           ProcessDriverDeferrals is set
    2017.04.19 11:58:32.8906467 744   12768 Agent           RegisterService is set
    2017.04.19 11:58:32.8987809 744   12768 Misc            EP: error: 0x8024500C : - failed to get SLS data
    2017.04.19 11:58:32.8987883 744   12768 Misc            Failed to obtain 9482F4B4-E343-43B6-B170-9A65BC822C77 redir SecondaryServiceAuth URL, error = 0x8024500C
    2017.04.19 11:58:32.8987924 744   12768 Agent           Failed to obtain the authorization cab URL for service 7971f918-a847-4430-9279-4a52d1efe18d, hr=0
    2017.04.19 11:58:32.8987932 744   12768 Agent           Caller My App failed to opt in to service 7971f918-a847-4430-9279-4a52d1efe18d, hr=0X8024500C
    2017.04.19 11:58:32.8996814 744   12768 Misc            EP: error: 0x8024500C : - failed to get SLS data
    2017.04.19 11:58:32.8996867 744   12768 Misc            Failed to obtain 9482F4B4-E343-43B6-B170-9A65BC822C77 redir Client/Server URL, error = 0x8024500C
    2017.04.19 11:58:32.8996888 744   12768 ProtocolTalker  PTError: 0x8024500c
    2017.04.19 11:58:32.8996933 744   12768 ProtocolTalker  Initialization failed for Protocol Talker Context 0x8024500c
    2017.04.19 11:58:32.9445302 744   12768 Agent           Exit code = 0x8024500C
    2017.04.19 11:58:32.9445319 744   12768 Agent           * END * Finding updates CallerId = UpdateOrchestrator  Id = 9
    2017.04.19 11:58:32.9518874 744   2704  ComApi          *RESUMED* Search ClientId = UpdateOrchestrator
    2017.04.19 11:58:32.9524416 744   2704  ComApi          Updates found = 0
    2017.04.19 11:58:32.9524420 744   2704  ComApi          Exit code = 0x00000000, Result code = 0x8024500C
    2017.04.19 11:58:32.9524429 744   2704  ComApi          * END *   Search ClientId = UpdateOrchestrator
    2017.04.19 11:58:32.9528786 744   7660  ComApi          ISusInternal:: DisconnectCall failed, hr=8024000C

    Thursday, April 20, 2017 8:06 AM

All replies

  • Hi nevskenamoht,

    1. Is the WSUS server installed KB3095113 and KB3159706(with manual steps), if not, please install them on the WSUS server, and the upgrade files need to be downloaded after installing the KBs;

    2. Do all WSUS clients show up and report to the WSUS server?

    3. Please check if the WSUS server configured with "Do not store update files locally", if yes, then clients will turn to Microsoft Update to download the update files;

    4. Also check if there are any errors in WSUS event log in Event Viewer.

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, April 21, 2017 8:22 AM
  • Hi,

    Just to check if the above reply could be of help? If yes, you may mark useful reply as answer, if not, welcome to feedback.

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, April 26, 2017 8:12 AM
  • I'm getting the same error code, but with the Windows Activation troubleshooter.

    I'm using WSUS on Server 2012 R2, all clients including this windows 10 PC are updating successfully, but this PC won't activate, giving that error code!

    Have MS not patched their servers perhaps?


    Thursday, April 27, 2017 7:01 AM
  • My problem turned out to be a networking related problem for activation. Removing the machine from the domain allowed it to activate. Not sure why as all DNS was the same, but I had configured group policy not to allow machines to go out to the internet for windows updates - which could have affected activation.

    The other thing I did in group policy was to ensure that the "Alternate" server for intranet updates was set - in my case the same settings as the main intranet source.

    Friday, April 28, 2017 7:26 AM