locked
Error 0x80d05001 with Server 2016 - Windows 10 Clients RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    This is on a new install. All Windows Updates were performed on the server.

    Windows 7 machines are updating like normal, but Windows 10 machines are throwing 0x80D05001 during the downloading step.

    IIS on the WSUS server is showing no errors, requests are always responded to with 200 OK.

    Log on the Windows 10 machine shows the following:

    2018/07/16 11:29:31.2041384 3784  4692  DownloadManager Dynamic download data fetcher for ServiceId 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 does not exist.
    2018/07/16 11:29:31.2056279 3784  4692  DownloadManager Update the URLs for DO Job 86BB1BCA-679E-43D0-885D-8E7DA791D985 - Update 7E1C8B32-BCEF-45A9-A324-67E26609A809.200
    2018/07/16 11:29:31.2061021 3784  4692  DownloadManager Download job 86BB1BCA-679E-43D0-885D-8E7DA791D985 resumed.
    2018/07/16 11:29:31.2063063 3784  4692  DownloadManager Dynamic download data fetcher for ServiceId 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 does not exist.
    2018/07/16 11:29:31.5609160 3784  8832  DownloadManager Suspended update 7E0B1F76-AEC3-4146-AE28-3B25E2A97A24 for reason 0x40000 (DynamicUrl)
    2018/07/16 11:29:31.5609210 3784  8832  DownloadManager Attempted to resume update 7E0B1F76-AEC3-4146-AE28-3B25E2A97A24 for reason 0x40000 (DynamicUrl), update is no longer suspended afterward.
    2018/07/16 11:29:31.5609359 3784  8832  DownloadManager DO job {9B2794CE-4FE0-4D1D-A67B-4EC8399042E7} failed, updateId = 7E0B1F76-AEC3-4146-AE28-3B25E2A97A24.200, hr = 0x80D05001. File URL = http://SERVER:8530/, local path = C:\WINDOWS\SoftwareDistribution\Download\6b8c686eddd1df25bc825c072d95a89e\Windows10.0-KB4338832-X64.cab, The response headers = HTTP/1.1 200 OK  Date: Mon, 16 Jul 2018 15:29:32 GMT  Content-Length: 299  Content-Type: text/html; charset=UTF-8  Server: Microsoft-IIS/10.0  X-Powered-By: ASP.NET    
    2018/07/16 11:29:31.5610491 3784  8832  DownloadManager   Progress failure bytes total = 21692015, bytes transferred = 0
    2018/07/16 11:29:31.5642302 3784  8832  DownloadManager *FAILED* [80D05001] Error occurred while downloading update 7E0B1F76-AEC3-4146-AE28-3B25E2A97A24.200; notifying dependent calls.

    Monday, July 16, 2018 4:15 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello John Kidd Jr,

        

    Glad to help.

     

    At first, it would be very helpful if you could provide some details about WSUS version, KB number and so on.

     

    And you could try following method to resolve this issue.

     

    1. On the client side, try to open this website to check the connectivity:

    http://WSUSserver:8530/ClientWebService/client.asmx (Please change wsusserver name )

     

    1. Try following script:

     

    net stop bits
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
reg delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v SusClientIDValidation /f
rd /s /q "C:\WINDOWS\SoftwareDistribution"
net start bits
net start wuauserv
wuauclt /resetauthorization /detectnow
PowerShell.exe (New-Object -ComObject Microsoft.Update.AutoUpdate).DetectNow()

     

    1. Refer to this official website:

    https://support.microsoft.com/en-gb/help/10164/fix-windows-update-errors

     

     

    Hope above methods could help you and look forward to your feedback.

     

    Best Regards,

    Ray Jia

    Please remember to mark the replies as answers if they help.

    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, July 17, 2018 2:41 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    what's more, you could try to download this update from catalog.update.microsoft.com and install it manually.

    Look forward to your feedback.

    Best Regards,

    Ray Jia

    Please remember to mark the replies as answers if they help.

    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, July 17, 2018 2:49 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello John Kidd Jr,

        

    Glad to help.

     

    At first, it would be very helpful if you could provide some details about WSUS version, KB number and so on.

     

    And you could try following method to resolve this issue.

     

    1. On the client side, try to open this website to check the connectivity:

    http://WSUSserver:8530/ClientWebService/client.asmx (Please change wsusserver name )

     

    1. Try following script:

     

    net stop bits
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
reg delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v SusClientIDValidation /f
rd /s /q "C:\WINDOWS\SoftwareDistribution"
net start bits
net start wuauserv
wuauclt /resetauthorization /detectnow
PowerShell.exe (New-Object -ComObject Microsoft.Update.AutoUpdate).DetectNow()

     

    1. Refer to this official website:

    https://support.microsoft.com/en-gb/help/10164/fix-windows-update-errors

     

     

    Hope above methods could help you and look forward to your feedback.

     

    Best Regards,

    Ray Jia

    Please remember to mark the replies as answers if they help.

    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tried the above solutions. No change.

    1. Client Service page appeared when using Edge. Client.asmx downloaded when using Chrome.

    2. Script deleted the download cache and forced a recheck against the server... but no change

    3. Didn't help.

    WSUS version is 5.0, running on Windows Server 2016 (10.0.14393.2007).

    KB's failing to install are: 4338819, 4338832, 4343669, 2267602. All fail with error 0x80D05001. Client OS is Windows 10, version 10.0.17134.112.

    Tuesday, July 17, 2018 1:15 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    what's more, you could try to download this update from catalog.update.microsoft.com and install it manually.

    Look forward to your feedback.

    Best Regards,

    Ray Jia

    Please remember to mark the replies as answers if they help.

    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Manually installing an update on hundreds of computers is not a practical solution.
    Tuesday, July 17, 2018 1:16 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello John Kidd Jr,

      

    At first, let us confirm that all of your windows 10 clients meet this issue and these clients work fine with other updates.

      

    However, this error indicate that your client can not get the updates from wsus. And according to your test, there is no problem with the connectivity between the client and wsus. Then we could consider re-download these updates by following method

    1. Decline these updates
    2. remove them via WSUS Cleanup wizard
    3. import them from catalog.update.microsoft.com manually.

      

    Check if it work.

      

     Look forward to your feedback.

    Best Regards,

    Ray Jia

    Please remember to mark the replies as answers if they help.

    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, July 18, 2018 2:55 AM