locked
Windows 10 client cannot update from WSUS RRS feed

  • Question

  • Hi,

    I have a problem updating my windows 10 clients from my wsus.

    My W10 clients cannot download updates from my wsus server, it got stuck at 0,97,99 %
    My wsus server's url is : https://server:8531
    The name is fictionnal, i changed it

    When i check the windowsupdate.log from my W10 client, i see that it chooses from the good wsus server :
    Here are 2 lines from the windowsupdate.log :

    2017/04/05 10:50:04.1946870 1032  2324  Misc            Got WSUS SecuredClient/Server URL: https://server:8531/ClientWebService/client.asmx/secured""
    2017/04/05 10:50:04.1947931 1032  2324  WebServices     Auto proxy settings for this web service call.

    But then, i don't know why, it seems that it downloads the .cab files from the good server but from http, i got this in the log file :

    2017/04/05 10:50:04.8745578 1032  2324  DownloadManager New download job UpdateId = {0765F079-FB25-495E-BC5E-F4A53CD58864}.101
    2017/04/05 10:50:04.8764668 1032  2324  DownloadManager BITS job initialized, JobId = {80E3CE8B-077A-48EE-8E16-D98351F706ED}
    2017/04/05 10:50:04.9655120 1032  2324  DownloadManager Downloading from http://servername:8530/Content/CC/EFEAF7EC1E61F7306B175A11BF61F419E50A74CC.cab to C:\windows\SoftwareDistribution\Download\5adf1c8a3286eafbab8cbd7c8e6e15a4\outlook-x-none.cab (full file).
    2017/04/05 10:50:04.9664532 1032  2324  DownloadManager Found proxy myproxyserver:8080 for BITS job 80E3CE8B-077A-48EE-8E16-D98351F706ED. Bypass-list: NULL
    2017/04/05 10:50:04.9680410 1032  2324  DownloadManager CUpdateDownloadJob::GetNetworkCostSwitch() Neither unrestricted or restricted network cost used, so using current cost
    2017/04/05 10:50:04.9682308 1032  2324  DownloadManager P2P download failed, falling back on BITS and retrying with new Download Job.
    2017/04/05 10:50:04.9684086 1032  2324  DownloadManager CUpdateDownloadJob::GetNetworkCostSwitch() Neither unrestricted or restricted network cost used, so using current cost
    2017/04/05 10:50:04.9717732 1032  2324  DownloadManager New download job UpdateId = {BE861CC2-5ADB-4431-866A-95D399AA0B5C}.101

    I checked the registry and i see the good url with https.
    The Windows 10 client reports well in the wsus console.
    The GPO is good, at least it works well with my windows 7 clients.

    I also deleted the C:\softwaredistribution and redownload updates 2 times, it didn't fix anything, the same problem appears.

    I also tried several times to restart windowsupdate service, wuauclt /detectnow etc... reboot computer i still got this problem.

    Can anyone help me please ?

    Sorry english is not my mother tongue.

    Thanks

    Benjamin.

    Wednesday, April 5, 2017 9:15 AM

Answers

  • Anne thanks

    I found the problem by myself :

    And you are right, the problem seems to come from the proxy:

    I had to delete the following registry key :

     HKLM\SOFTWARE\Microsoft\WIndows\Currentversion\Internet Settings\Connection\WinHttpSettings

    And reboot windows update.

    Now it works fine

    Thanks !!

    • Marked as answer by BenjaminFili Thursday, April 6, 2017 12:19 PM
    Thursday, April 6, 2017 12:18 PM

All replies

  • Hi BenjaminFili,

    >2017/04/05 10:50:04.9664532 1032  2324  DownloadManager Found proxy myproxyserver:8080 for BITS job 80E3CE8B-077A-48EE-8E16-D98351F706ED. Bypass-list: NULL

    1. Do you set a proxy between the WSUS server and WSUS clients when downloading updates, if yes, please check the proxy settings, enable it forward the packets correctly;

    >But then, i don't know why, it seems that it downloads the .cab files from the good server but from http, i got this in the log file :

    After configuring SSL for WSUS server, it only secure the metadata of the update, when downloading the update binary files, it still use http. SSL is used to verify if the WSUS server is the trusted and secure WSUS server.

    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.

    Thursday, April 6, 2017 9:01 AM
  • Anne thanks

    I found the problem by myself :

    And you are right, the problem seems to come from the proxy:

    I had to delete the following registry key :

     HKLM\SOFTWARE\Microsoft\WIndows\Currentversion\Internet Settings\Connection\WinHttpSettings

    And reboot windows update.

    Now it works fine

    Thanks !!

    • Marked as answer by BenjaminFili Thursday, April 6, 2017 12:19 PM
    Thursday, April 6, 2017 12:18 PM
  • Delete from Server or Client(using windows 10?
    Thursday, February 1, 2018 4:57 AM
  • delete from the client
    Tuesday, April 3, 2018 5:27 PM