locked
WSUS not pushing updates, also 2016 servers unable to manually update RRS feed

  • Question

  • So I'm currently trying to get my 2016 WSUS server to update manually, via "Start>Settings>Windows Update" I have gone through a plethora of google searches attempting to figure out why I cannot download updates. Currently the error I'm getting is this:

    "There were problems installing some updates, but we'll try again later. If you keep seeing this and want to search the web or contact support for more information, this may help:"

    Then it gives me two of the updates I'm trying to install (which were approved via WSUS but not installing automatically or manually) and Error 0x80244019.

    On top of that, ALL of my 2016 servers are not pulling updates from WSUS. All approved updates are showing "Install" under status and yet none of them are actually installing. I'm assuming it has something to do with the above. As I've tried manually updating some other test servers and get similar errors, but same end result of no updates.

    Only thing that seemed to work on the test machines was to add the following to the registry:

    HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows Update

    DisableWindowsUpdateAccess

    DoNotConnectToWindowsUpdateInternetLocations

    Both keys set to 0 allowed me to manually download updates.

    Any help would be appreciated and hopefully save my hair from being ripped out further.


    Jeremiah

    Wednesday, January 9, 2019 5:48 PM

All replies

  • Hello,
     
    Are there any error messages in the event viewer of WSUS and IIS? And in the windowsupdate.log on the affected clients?
     
    I assumed that your WSUS server is pointed to itself, so the issue in your WSUS server is same as other 2016 servers. 
     
    0x80244019 means that "the server cannot find the requested URI (Uniform Resource Identifier)". First, we need to check the connectivity between WSUS and Clients. On the affected clients, open a browser and navigate to the following URL.
     
    http://yourwsusserver.domain.local:8530/selfupdate/wuident.cab
     
    If there is not a prompt for file downloading, there must be some issues about the connectivity. Check the firewall, port, etc.
     
    If the connectivity is OK. Check IIS to see if the Wsuspool and the WSUS site are running, if the virtual directories are pointing to the correct physical paths.
     
    If the issue persists, upload any error messages you find in event viewer and log.
     
    Hope my answer could help you and look forward to your feedback.
     
    Best Regards,
    Ray

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

    Thursday, January 10, 2019 7:33 AM
  • Just to be clear, for the url, am I pasting it exactly how you have it or am I using my own WSUS Server and Domain in place of it? What is the local value if anything? Or is it just Local?

    I ask because I tried it as is as well as with my WSUS Server and Domain and neither worked. Both just went straight to an error page: "This page can't be displayed"

    When I check the Event Viewer, there are no WSUS/Windows Update client errors or IIS that I'm finding. In fact, I'm seeing "WSUS is working correctly" in the logs.

    Will send WindowsUpdate.Log snipped shortly.

    Thursday, January 10, 2019 7:38 PM
  • Hello,
     
    Replace it with your WSUS server location you put in the policy.
     

     
    If everything is OK, you would see a prompt like this.
     

     
    If not, there must be something wrong with the connection between the WSUS and the clients. Make sure the WSUS server location is correct, and check the firewall, port as I mentioned above. Can you ping the WSUS server on the clients?
     
    Best Regards,
    Ray

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

    Friday, January 11, 2019 8:28 AM
  • Here is the WindowsUpdate.log after another failed attempt of running updates as described in my OP. Again, this is the logs from my actual WSUS server trying to update.

    2019/01/10 14:33:49.1153308 1200  5316  ComApi          * START *   Init Search ClientId = UpdateOrchestrator
    2019/01/10 14:33:49.1153332 1200  5316  ComApi          * START *   Search ClientId = UpdateOrchestrator
    2019/01/10 14:33:49.1251281 1200  5316  Agent           * START * Queueing Finding updates [CallerId = UpdateOrchestrator  Id = 10]
    2019/01/10 14:33:49.1251312 1200  5316  Agent           Removing service 00000000-0000-0000-0000-000000000000 from sequential scan list
    2019/01/10 14:33:49.1251332 1200  5316  Agent           Added service 00000000-0000-0000-0000-000000000000 to sequential scan list
    2019/01/10 14:33:49.1251596 1200  5316  ComApi          Search ClientId = UpdateOrchestrator
    2019/01/10 14:33:49.1280640 1200  4884  Agent           * END * Queueing Finding updates [CallerId = UpdateOrchestrator  Id = 10]
    2019/01/10 14:33:49.1303305 1200  4884  Agent           * START * Finding updates CallerId = UpdateOrchestrator  Id = 10
    2019/01/10 14:33:49.1303317 1200  4884  Agent           Online = Yes; AllowCachedResults = No; Ignore download priority = No
    2019/01/10 14:33:49.1303325 1200  4884  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""
    2019/01/10 14:33:49.1303348 1200  4884  Agent           ServiceID = {00000000-0000-0000-0000-000000000000} Third party service
    2019/01/10 14:33:49.1303356 1200  4884  Agent           Search Scope = {Machine}
    2019/01/10 14:33:49.1303372 1200  4884  Agent           Caller SID for Applicability: S-1-5-21-609924933-2590847731-1494915315-1691
    2019/01/10 14:33:49.1303380 1200  4884  Agent           ProcessDriverDeferrals is set
    2019/01/10 14:33:49.1303380 1200  4884  Agent           RegisterService is set
    2019/01/10 14:33:49.1336970 1200  4884  Misc            Got WSUS Client/Server URL: http://**removed**:8530/ClientWebService/client.asmx""
    2019/01/10 14:33:49.2704442 1200  4884  ProtocolTalker  ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://*removed*:8530/ClientWebService/client.asmx
    2019/01/10 14:33:49.2705842 1200  4884  ProtocolTalker  OK to reuse existing configuration
    2019/01/10 14:33:49.2705870 1200  4884  ProtocolTalker  Existing cookie is valid, just use it
    2019/01/10 14:33:49.2705878 1200  4884  ProtocolTalker  PTInfo: Server requested registration
    2019/01/10 14:33:49.9087890 1200  4884  WebServices     Auto proxy settings for this web service call.
    2019/01/10 14:33:49.9320272 1200  4884  ProtocolTalker  PTInfo: syncing with server using normal query
    2019/01/10 14:33:49.9369978 1200  4884  ProtocolTalker  SyncUpdates round trips: 2
    2019/01/10 14:33:52.0346349 1200  4884  ProtocolTalker  ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://*removed*:8530/ClientWebService/client.asmx
    2019/01/10 14:33:52.0346377 1200  4884  ProtocolTalker  OK to reuse existing configuration
    2019/01/10 14:33:52.0346412 1200  4884  ProtocolTalker  Existing cookie is valid, just use it
    2019/01/10 14:33:52.0346424 1200  4884  ProtocolTalker  PTInfo: Server requested registration
    2019/01/10 14:33:52.0808282 1200  4884  Agent           Update 39F9CDD1-795C-4D0E-8C0A-73AB3F31746D.200 is pruned out due to potential supersedence
    2019/01/10 14:33:52.0808302 1200  4884  Agent           Update 9BB6C406-1C49-4625-815B-AF11DA0BFADD.200 is pruned out due to potential supersedence
    2019/01/10 14:33:52.0808321 1200  4884  Agent           Update 0F28AFF6-2969-4C8E-BDD4-58016FF4D275.200 is pruned out due to potential supersedence
    2019/01/10 14:33:52.0808341 1200  4884  Agent           Update 05D83D6B-8690-4E3C-979F-E1134AE54AA7.200 is pruned out due to potential supersedence
    2019/01/10 14:33:52.0808357 1200  4884  Agent           Update 64E80467-8751-4C5F-ABEC-B58263201FB2.200 is pruned out due to potential supersedence
    2019/01/10 14:33:52.0808519 1200  4884  Agent           Added update 84D22E36-5AD2-4349-8865-4E1BB5F33240.200 to search result
    2019/01/10 14:33:52.0808542 1200  4884  Agent           Added update B923DAE5-F828-4F7D-8A5D-A9C51D2E957E.201 to search result
    2019/01/10 14:33:52.0808700 1200  4884  Agent           Policy driven service does not support additional filtering on feature updates.
    2019/01/10 14:33:52.0808704 1200  4884  Agent           Found 2 updates and 85 categories in search; evaluated appl. rules of 940 out of 1189 deployed entities
    2019/01/10 14:33:52.0916593 1200  4884  Agent           * END * Finding updates CallerId = UpdateOrchestrator  Id = 10
    2019/01/10 14:33:52.1104013 1200  4648  ComApi          *RESUMED* Search ClientId = UpdateOrchestrator
    2019/01/10 14:33:52.1120629 1200  4648  ComApi          Updates found = 2
    2019/01/10 14:33:52.1120636 1200  4648  ComApi          * END *   Search ClientId = UpdateOrchestrator
    2019/01/10 14:33:52.1183003 1200  5316  ComApi          ISusInternal:: DisconnectCall failed, hr=8024000C
    2019/01/10 14:33:52.3345763 1200  5316  ComApi          * START *   Download ClientId = UpdateOrchestrator
    2019/01/10 14:33:52.3345771 1200  5316  ComApi          Flags: 0X1000C; Download priority: 3; Network Cost Policy: 0
    2019/01/10 14:33:52.3345779 1200  5316  ComApi          Updates in request: 1
    2019/01/10 14:33:52.3345870 1200  5316  ComApi          ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2019/01/10 14:33:52.3361330 1200  5316  ComApi          *QUEUED* Download ClientId = UpdateOrchestrator
    2019/01/10 14:33:52.3361413 1200  4352  Shared          Effective power state: AC
    2019/01/10 14:33:52.3361468 1200  4352  Agent           Obtained a network PDC reference for callID {688C18EE-BB94-4CD4-B6B6-870FE8C17515} with No-Progress-Timeout set to 4294967295; ActivationID: 136.
    2019/01/10 14:33:52.3372493 1200  4352  DownloadManager * START * Begin Downloading Updates [CallerId = UpdateOrchestrator] [Call ID = 688C18EE-BB94-4CD4-B6B6-870FE8C17515]
    2019/01/10 14:33:52.3372517 1200  4352  DownloadManager Priority = 3, NetworkCostPolicy = 0, Interactive = 1, Download on Battery = 1, Bypass Regulation = 1, Owner is system = 1, Proxy session id = 2, ServiceId = 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7
    2019/01/10 14:33:52.3372521 1200  4352  DownloadManager Updates to download = 1
    2019/01/10 14:33:52.3372529 1200  4352  Agent             Title = Definition Update for Windows Defender Antivirus - KB2267602 (Definition 1.281.941.0)
    2019/01/10 14:33:52.3372548 1200  4352  Agent             UpdateId = 84D22E36-5AD2-4349-8865-4E1BB5F33240.200
    2019/01/10 14:33:52.3372552 1200  4352  Agent               Bundles 4 updates:
    2019/01/10 14:33:52.3372572 1200  4352  Agent                 1D3075E1-63F0-4103-BA63-1DCAC0FE104D.200
    2019/01/10 14:33:52.3372588 1200  4352  Agent                 768A0D05-B285-4ACD-AE87-34AD5A7D63A8.200
    2019/01/10 14:33:52.3372604 1200  4352  Agent                 C77D78DC-CC82-4FAE-B090-DB0A518157F7.200
    2019/01/10 14:33:52.3372623 1200  4352  Agent                 8FB117EF-979C-4AAB-A317-F79668C2BF36.200
    2019/01/10 14:33:52.3451468 1200  4352  DownloadManager Failed to connect to the DO service; (hr = 80040154)
    2019/01/10 14:33:52.3451476 1200  4352  DownloadManager GetDOManager() failed, hr=80246008, hrExtended=80040154
    2019/01/10 14:33:52.3451484 1200  4352  DownloadManager Failed creating DO job with hr 80246008
    2019/01/10 14:33:52.3465036 1200  4352  DownloadManager DO download failed with error 80246008[Extended: 80040154], falling back to BITS and retrying with new Download Job.
    2019/01/10 14:33:52.3955690 1200  5316  ComApi          * START *   Download ClientId = UpdateOrchestrator
    2019/01/10 14:33:52.3955698 1200  5316  ComApi          Flags: 0X1000C; Download priority: 3; Network Cost Policy: 0
    2019/01/10 14:33:52.3955706 1200  5316  ComApi          Updates in request: 1
    2019/01/10 14:33:52.3955785 1200  5316  ComApi          ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2019/01/10 14:33:52.5703518 1200  4352  DownloadManager BITS job initialized: JobId = {D1C30D74-506F-416E-84AB-AB793133F091}
    2019/01/10 14:33:52.5800347 1200  4352  DownloadManager Downloading from http://*removed*:8530/c/msdownload/update/software/defu/2018/11/mpsigstub_87d88cc3d7357ccfee82a33ff6152e1a71146044.exe to C:\Windows\SoftwareDistribution\Download\e4fc628daae1b21820ae0a8386a44f6e\87d88cc3d7357ccfee82a33ff6152e1a71146044 (full file)
    2019/01/10 14:33:52.5818571 1200  4352  DownloadManager New download job {D1C30D74-506F-416E-84AB-AB793133F091} for UpdateId 768A0D05-B285-4ACD-AE87-34AD5A7D63A8.200
    2019/01/10 14:33:52.5866428 1200  4352  DownloadManager Download job D1C30D74-506F-416E-84AB-AB793133F091 resumed.
    2019/01/10 14:33:52.5906520 1200  4352  DownloadManager Failed to connect to the DO service; (hr = 80040154)
    2019/01/10 14:33:52.5906528 1200  4352  DownloadManager GetDOManager() failed, hr=80246008, hrExtended=80040154
    2019/01/10 14:33:52.5906536 1200  4352  DownloadManager Failed creating DO job with hr 80246008
    2019/01/10 14:33:52.5919994 1200  4352  DownloadManager DO download failed with error 80246008[Extended: 80040154], falling back to BITS and retrying with new Download Job.
    2019/01/10 14:33:52.6009583 1200  4352  DownloadManager BITS job initialized: JobId = {7F51DDB9-EFFA-410B-B788-2C2D69FAFF86}
    2019/01/10 14:33:52.6090123 1200  4352  DownloadManager Downloading from http://*removed*:8530/c/msdownload/update/software/defu/2018/11/am_base_3b20f6b64fd0793ff22c6b08066248618e82e3b3.exe to C:\Windows\SoftwareDistribution\Download\21a4ac8e83dd049556dd7cb02abacab6\3b20f6b64fd0793ff22c6b08066248618e82e3b3 (full file)
    2019/01/10 14:33:52.6101937 1200  4352  DownloadManager New download job {7F51DDB9-EFFA-410B-B788-2C2D69FAFF86} for UpdateId 8FB117EF-979C-4AAB-A317-F79668C2BF36.200
    2019/01/10 14:33:52.6162955 1200  4352  DownloadManager Download job 7F51DDB9-EFFA-410B-B788-2C2D69FAFF86 resumed.
    2019/01/10 14:33:52.6227522 1200  4352  Shared          Effective power state: AC
    2019/01/10 14:33:52.6227554 1200  4352  Agent           Released network PDC reference for callId {688C18EE-BB94-4CD4-B6B6-870FE8C17515}; ActivationID: 136
    2019/01/10 14:33:52.6227581 1200  4352  Agent           Obtained a network PDC reference for callID {688C18EE-BB94-4CD4-B6B6-870FE8C17515} with No-Progress-Timeout set to 4294967295; ActivationID: 141.
    2019/01/10 14:33:52.6228673 1200  4500  Agent           WU client calls back to download call {688C18EE-BB94-4CD4-B6B6-870FE8C17515} with code Call progress and error 0
    2019/01/10 14:33:52.6252690 1200  5316  ComApi          *QUEUED* Download ClientId = UpdateOrchestrator
    2019/01/10 14:33:52.6385779 1200  3928  Shared          Effective power state: AC
    2019/01/10 14:33:52.6385799 1200  3928  Agent           Released network PDC reference for callId {688C18EE-BB94-4CD4-B6B6-870FE8C17515}; ActivationID: 141
    2019/01/10 14:33:52.6385830 1200  3928  Agent           Obtained a network PDC reference for callID {688C18EE-BB94-4CD4-B6B6-870FE8C17515} with No-Progress-Timeout set to 4294967295; ActivationID: 142.
    2019/01/10 14:33:52.6387617 1200  4500  Agent           WU client calls back to download call {688C18EE-BB94-4CD4-B6B6-870FE8C17515} with code Call progress and error 0
    2019/01/10 14:33:52.6452192 1200  5616  DownloadManager Suspended update 768A0D05-B285-4ACD-AE87-34AD5A7D63A8 for reason 0x40000
    2019/01/10 14:33:52.6452231 1200  5616  DownloadManager Attempted to resume update 768A0D05-B285-4ACD-AE87-34AD5A7D63A8 for reason 0x40000, update is no longer suspended afterward.
    2019/01/10 14:33:52.6452310 1200  5616  DownloadManager BITS job {D1C30D74-506F-416E-84AB-AB793133F091} failed, updateId = 768A0D05-B285-4ACD-AE87-34AD5A7D63A8.200, hr = 0x80190194. File URL = http://*removed*:8530/c/msdownload/update/software/defu/2018/11/mpsigstub_87d88cc3d7357ccfee82a33ff6152e1a71146044.exe, local path = C:\Windows\SoftwareDistribution\Download\e4fc628daae1b21820ae0a8386a44f6e\87d88cc3d7357ccfee82a33ff6152e1a71146044
    2019/01/10 14:33:52.6453280 1200  5616  DownloadManager   Progress failure bytes total = 592416, bytes transferred = 0
    2019/01/10 14:33:52.6456576 1200  5616  DownloadManager UpdateId = {768A0D05-B285-4ACD-AE87-34AD5A7D63A8}.200, Job ID = D1C30D74-506F-416E-84AB-AB793133F091, xszResponseHeaders = HTTP/1.1 404 Not Found  Date: Thu, 10 Jan 2019 19:33:52 GMT  Content-Length: 0  Server: Microsoft-IIS/10.0  X-Powered-By: ASP.NET    .
    2019/01/10 14:33:52.6537187 1200  5616  DownloadManager   Download job completion. Progress for update {768A0D05-B285-4ACD-AE87-34AD5A7D63A8} - total = 592416, transferred = 0 bytes. Transfer time=0, connect time=0 (ms)
    2019/01/10 14:33:52.6548244 1200  5616  DownloadManager Error 0x80244019 occurred while downloading update; notifying dependent calls.
    2019/01/10 14:33:52.6586842 1200  3928  DownloadManager Suspended update 8FB117EF-979C-4AAB-A317-F79668C2BF36 for reason 0x40000
    2019/01/10 14:33:52.6586933 1200  3928  DownloadManager Attempted to resume update 8FB117EF-979C-4AAB-A317-F79668C2BF36 for reason 0x40000, update is no longer suspended afterward.
    2019/01/10 14:33:52.6586976 1200  3928  DownloadManager BITS job {7F51DDB9-EFFA-410B-B788-2C2D69FAFF86} failed, updateId = 8FB117EF-979C-4AAB-A317-F79668C2BF36.200, hr = 0x80190194. File URL = http://*removed*:8530/c/msdownload/update/software/defu/2018/11/am_base_3b20f6b64fd0793ff22c6b08066248618e82e3b3.exe, local path = C:\Windows\SoftwareDistribution\Download\21a4ac8e83dd049556dd7cb02abacab6\3b20f6b64fd0793ff22c6b08066248618e82e3b3
    2019/01/10 14:33:52.6587843 1200  3928  DownloadManager   Progress failure bytes total = 139329200, bytes transferred = 0
    2019/01/10 14:33:52.6590824 1200  3928  DownloadManager UpdateId = {8FB117EF-979C-4AAB-A317-F79668C2BF36}.200, Job ID = 7F51DDB9-EFFA-410B-B788-2C2D69FAFF86, xszResponseHeaders = HTTP/1.1 404 Not Found  Date: Thu, 10 Jan 2019 19:33:52 GMT  Content-Length: 0  Server: Microsoft-IIS/10.0  X-Powered-By: ASP.NET    .
    2019/01/10 14:33:52.6680863 1200  3928  DownloadManager   Download job completion. Progress for update {8FB117EF-979C-4AAB-A317-F79668C2BF36} - total = 139329200, transferred = 0 bytes. Transfer time=0, connect time=0 (ms)
    2019/01/10 14:33:52.6690760 1200  3928  DownloadManager Error 0x80244019 occurred while downloading update; notifying dependent calls.
    2019/01/10 14:33:52.6706769 1200  4352  Shared          Effective power state: AC
    2019/01/10 14:33:52.6706796 1200  4352  Agent           Released network PDC reference for callId {688C18EE-BB94-4CD4-B6B6-870FE8C17515}; ActivationID: 142
    2019/01/10 14:33:52.6706828 1200  4352  Agent           Obtained a network PDC reference for callID {688C18EE-BB94-4CD4-B6B6-870FE8C17515} with No-Progress-Timeout set to 4294967295; ActivationID: 143.
    2019/01/10 14:33:52.6706836 1200  4352  DownloadManager * END * Begin Downloading Updates CallerId = UpdateOrchestrator
    2019/01/10 14:33:52.6706852 1200  4352  Shared          Effective power state: AC
    2019/01/10 14:33:52.6706867 1200  4352  Agent           Obtained a network PDC reference for callID {AB0FFE58-F116-4D46-B91C-11A312828F8D} with No-Progress-Timeout set to 4294967295; ActivationID: 144.
    2019/01/10 14:33:52.6707731 1200  4500  Agent           WU client calls back to download call {688C18EE-BB94-4CD4-B6B6-870FE8C17515} with code Call progress and error 0
    2019/01/10 14:33:52.6719734 1200  4352  DownloadManager * START * Begin Downloading Updates [CallerId = UpdateOrchestrator] [Call ID = AB0FFE58-F116-4D46-B91C-11A312828F8D]
    2019/01/10 14:33:52.6720151 1200  4352  DownloadManager Priority = 3, NetworkCostPolicy = 0, Interactive = 1, Download on Battery = 1, Bypass Regulation = 1, Owner is system = 1, Proxy session id = 2, ServiceId = 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7
    2019/01/10 14:33:52.6720171 1200  4352  DownloadManager Updates to download = 1
    2019/01/10 14:33:52.6720179 1200  4352  Agent             Title = Windows Malicious Software Removal Tool x64 - December 2018 (KB890830)
    2019/01/10 14:33:52.6720207 1200  4352  Agent             UpdateId = B923DAE5-F828-4F7D-8A5D-A9C51D2E957E.201
    2019/01/10 14:33:52.6720211 1200  4352  Agent               Bundles 1 updates:
    2019/01/10 14:33:52.6720230 1200  4352  Agent                 7972D2BA-DD61-4891-823A-0E24B3669AC5.201
    2019/01/10 14:33:52.6787210 1200  4352  DownloadManager * END * Download Call Complete Call 11 for caller UpdateOrchestrator has completed; signaling completion.
    2019/01/10 14:33:52.6898033 1200  4352  Shared          Effective power state: AC
    2019/01/10 14:33:52.6898053 1200  4352  Agent           Released network PDC reference for callId {688C18EE-BB94-4CD4-B6B6-870FE8C17515}; ActivationID: 143
    2019/01/10 14:33:52.6899157 1200  4500  ComApi          *RESUMED* Download ClientId = UpdateOrchestrator
    2019/01/10 14:33:52.6899165 1200  4500  ComApi          Download call complete (succeeded = 0, succeeded with errors = 0, failed = 1, unaccounted = 0)
    2019/01/10 14:33:52.6899181 1200  4500  ComApi          Exit code = 0x00000000; Call error code = 0x80240022
    2019/01/10 14:33:52.6899184 1200  4500  ComApi          * END *   Download ClientId = UpdateOrchestrator
    2019/01/10 14:33:52.6899196 1200  4500  Agent           WU client calls back to download call {688C18EE-BB94-4CD4-B6B6-870FE8C17515} with code Call complete and error 0x80244019
    2019/01/10 14:33:52.6908344 1200  5316  ComApi          ISusInternal:: DisconnectCall failed, hr=8024000C
    2019/01/10 14:33:52.6957947 1200  4352  DownloadManager Failed to connect to the DO service; (hr = 80040154)
    2019/01/10 14:33:52.6957955 1200  4352  DownloadManager GetDOManager() failed, hr=80246008, hrExtended=80040154
    2019/01/10 14:33:52.6957959 1200  4352  DownloadManager Failed creating DO job with hr 80246008
    2019/01/10 14:33:52.6971350 1200  4352  DownloadManager DO download failed with error 80246008[Extended: 80040154], falling back to BITS and retrying with new Download Job.
    2019/01/10 14:33:52.7071692 1200  4352  DownloadManager BITS job initialized: JobId = {1B210937-3514-48F6-837F-24D15009D6E3}
    2019/01/10 14:33:52.7180519 1200  4352  DownloadManager Downloading from http://*removed*:8530/d/msdownload/update/software/uprl/2018/12/windows-kb890830-x64-v5.67_da12229b461546fd0a491ff3013f15e7b2c3e2c0.exe to C:\Windows\SoftwareDistribution\Download\1ea11c7b794fc18954b79c9d2ba107e2\da12229b461546fd0a491ff3013f15e7b2c3e2c0 (full file)
    2019/01/10 14:33:52.7193330 1200  4352  DownloadManager New download job {1B210937-3514-48F6-837F-24D15009D6E3} for UpdateId 7972D2BA-DD61-4891-823A-0E24B3669AC5.201
    2019/01/10 14:33:52.7236542 1200  4352  DownloadManager Download job 1B210937-3514-48F6-837F-24D15009D6E3 resumed.
    2019/01/10 14:33:52.7271299 1200  4352  Shared          Effective power state: AC
    2019/01/10 14:33:52.7271323 1200  4352  Agent           Released network PDC reference for callId {AB0FFE58-F116-4D46-B91C-11A312828F8D}; ActivationID: 144
    2019/01/10 14:33:52.7271359 1200  4352  Agent           Obtained a network PDC reference for callID {AB0FFE58-F116-4D46-B91C-11A312828F8D} with No-Progress-Timeout set to 4294967295; ActivationID: 148.
    2019/01/10 14:33:52.7290108 1200  4500  Agent           WU client calls back to download call {AB0FFE58-F116-4D46-B91C-11A312828F8D} with code Call progress and error 0
    2019/01/10 14:33:52.7333276 1200  4220  DownloadManager Suspended update 7972D2BA-DD61-4891-823A-0E24B3669AC5 for reason 0x40000
    2019/01/10 14:33:52.7333378 1200  4220  DownloadManager Attempted to resume update 7972D2BA-DD61-4891-823A-0E24B3669AC5 for reason 0x40000, update is no longer suspended afterward.

    Friday, January 11, 2019 4:17 PM
  • Hi,

    It looks like an incorrect configuration for the file download:

    2019/01/10 14:33:52.6452310 1200  5616  DownloadManager BITS job {D1C30D74-506F-416E-84AB-AB793133F091} failed, updateId = 768A0D05-B285-4ACD-AE87-34AD5A7D63A8.200, hr = 0x80190194. File URL =http://*removed*:8530/c/msdownload/update/software/defu/2018/11/mpsigstub_87d88cc3d7357ccfee82a33ff6152e1a71146044.exe, l

    0x80190194 means HTTP error 404 file not found, because it looks like the download URL is a combination of your WSUS server & the Microsoft Update URL.

    Do you have WSUS configured for clients to get update files from Microsoft Update or from your WSUS server?

    Best regards,
    Andrei


    We could change the world, if God would give us the source code.

    Sunday, January 13, 2019 8:38 AM
  • The clients pull from Microsoft update currently. This log is from my actual WSUS server.
    Monday, January 14, 2019 2:24 PM
  • Hello,
     
    For now, your WSUS is pointed to itself to get the updates, is it right? And the above log is from this WSUS server, right?
     
    As Andrei said, the link in the log is incorrect, could you check the content location in the IIS setting?
     

     
    Best Regards,
    Ray

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

    Tuesday, January 15, 2019 11:45 AM
  • My other WSUS servers are pointing to themselves as well and seem to be working fine...Here's the advanced settings location you posted. I did the same setup as my previous 3 WSUS servers, the only difference is this new WSUS is 2016 and it can't even manually update itself. I've only been able to use the Microsoft Update Catalog to install updates.


    • Edited by jerm20201 Tuesday, January 15, 2019 2:18 PM
    Tuesday, January 15, 2019 2:17 PM
  • Hello,

    In the GPO linked to your WSUS server, try to set the alternate download server with your WSUS server.
     

     
    Then try to update again and check the result.
      
    And I think we should confirm that the download from the URL "http://yourwsusserver:8530/selfupdate/wuident.cab" is failed, right?
     
    Best Regards,
    Ray


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

    Wednesday, January 16, 2019 10:30 AM
  • Hello,
     
    I noticed that you have not updated for several days. So does your issue solved or is there any update?
     
    Feel free to feedback.
     
    Best Regards,
    Ray

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

    Monday, January 21, 2019 10:54 AM
  • Sorry, yeah, so I've been able to get servers to manually update now. But I'm still unable to approve updates via WSUS(I use solarwinds patch manager).

    What seemed to fix my issues with manually running windows updates were the following:

    Removed the Alternate URL from "UpdateServiceURLAlternate" and changed the WUServer and WUStatusServer from the IP to the server name. IE https://WSUS01:8530

    Added DisableWindowsUpdateAccess set to 0

    Added DoNotConnectToWindowsUpdateInternetLocations set to 0

    Then modified the Host file to have the WSUS IP and server name.

    I'm now trying to figure out if my Registry settings are correct or if I'm missing something?

    Wednesday, January 30, 2019 5:58 PM
  • I saw your post and decided to blog about it. While it doesn't actually explain why your systems are getting those errors, it may enlighten you to the reason why (WUfB policies in a WSUS network). See it here:

    https://www.ajtek.ca/wsus/dual-scan-making-sense-of-why-so-many-have-issues/


    Adam Marshall, MCSE: Security
    https://www.ajtek.ca
    Microsoft MVP - Windows and Devices for IT

    Friday, February 1, 2019 4:06 AM