none
Windows 10 1703 Ent x64 WSUS issue

    Question

  • Hi All,

    After testing multiple senario's i think WSUS client is broken on a W10Enterprise 1703  when connecting to our Wsus server *(W2016 fully patched server) the w10E1703 client keeps saying "Downloading Updates 0%"

    are there more people who can confirm they have the same issue (and so it's a bug)

     

    Tuesday, April 11, 2017 7:17 AM

All replies

  •  

    Hi Matthew Koeman (NL),

    Did the issue occur with other system versions such as windows 10 1607 or windows 8.1?

    The similar issue occurred with previous Windows 10 1607 version and it was fixed by a later update. We could try to install the kb4016251 manually for Windows 1703 then check the symptom again. If it is possible, please update from windows update directly.

    If the issue persists, check the Windowsupdate.log for more information to troubleshoot the issue. 

    Best regard


    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 12, 2017 6:14 AM
    Moderator
  • Hi,

    The wsus works just fine for W10E 1607 and other 2016 servers ....
    we only see the issue on a new 1703 rollout, as well as from the MDT process as from a manualy installed W10 1703 x64 with only the gpo for wsus applied.

    i already applied kb4016251 and kb4015583 manualy, that doesnt fix the issue.

    some snippets from my logs , any idee ?

    2017-04-12 09:51:13.2247871 4260  4436  DownloadManager [0]10A4.1154::04/12/2017-09:51:13.224 [agent]Dynamic download data fetcher for ServiceId 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 does not exist.
    2017-04-12 09:51:13.2252131 4260  4320  DownloadManager [0]10A4.10E0::04/12/2017-09:51:13.225 [agent]DO job {F996B9EA-D85E-4BD7-8AB4-53400C56E327} hit a transient error, updateId = C77DC62F-6DAA-46C8-B644-5743F1395F16.201 <NULL>, error = 0x80D0000A
    2017-04-12 09:51:13.2258747 4260  4320  DownloadManager [0]10A4.10E0::04/12/2017-09:51:13.225 [agent]Error 0x80d0000a occurred while downloading update C77DC62F-6DAA-46C8-B644-5743F1395F16.201; notifying dependent calls.
    
    
    2017-04-12 09:55:21.2039159 4260  4320  IdleTimer       [0]10A4.10E0::04/12/2017-09:55:21.203 [agent]WU operation (DL.UpdateOrchestrator) started; operation # 94; does<NULL> use network; is<NULL> at background priority<NULL>
    2017-04-12 09:55:21.2039234 4260  4320  Agent           [0]10A4.10E0::04/12/2017-09:55:21.203 [agent]Obtained a network PDC reference for callID {242031C5-4C8B-4671-9D82-9BB9D3EB82FE} with No-Progress-Timeout set to 4294967295; ActivationID: 94.
    2017-04-12 09:55:21.2040505 4260  3992  Agent           [0]10A4.0F98::04/12/2017-09:55:21.204 [agent]WU client calls back to download call {242031C5-4C8B-4671-9D82-9BB9D3EB82FE} with code Call progress and error 0
    
    
    2017-04-12 09:55:21.2035768 4260  4320  Agent           [0]10A4.10E0::04/12/2017-09:55:21.203 [agent]Effective power state: AC; IsOnAC: Yes.
    2017-04-12 09:55:21.2035788 4260  4320  IdleTimer       [0]10A4.10E0::04/12/2017-09:55:21.203 [agent]WU operation (DL.UpdateOrchestrator, operation # 20) stopped; does<NULL> use network; is not at background priority<NULL>
    2017-04-12 09:55:21.2035811 4260  4320  Agent           [0]10A4.10E0::04/12/2017-09:55:21.203 [agent]Released network PDC reference for callId {59733973-B6F1-4C4E-B0CC-F5437D52A7A5}; ActivationID: 20
    2017-04-12 09:55:21.2035906 4260  4320  IdleTimer       [0]10A4.10E0::04/12/2017-09:55:21.203 [agent]WU operation (DL.UpdateOrchestrator) started; operation # 93; does<NULL> use network; is not at background priority<NULL>
    2017-04-12 09:55:21.2035918 4260  4320  Agent           [0]10A4.10E0::04/12/2017-09:55:21.203 [agent]Obtained a network PDC reference for callID {59733973-B6F1-4C4E-B0CC-F5437D52A7A5} with No-Progress-Timeout set to 4294967295; ActivationID: 93.
    2017-04-12 09:55:21.2035930 4260  3992  Agent           [0]10A4.0F98::04/12/2017-09:55:21.203 [agent]download call is NOT finished
    2017-04-12 09:55:21.2036790 4260  4320  DownloadManager [0]10A4.10E0::04/12/2017-09:55:21.203 [agent]Dynamic download data fetcher for ServiceId 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 does not exist.
    2017-04-12 09:55:21.2039076 4260  4320  Agent           [0]10A4.10E0::04/12/2017-09:55:21.203 [agent]Effective power state: AC; IsOnAC: Yes.
    2017-04-12 09:55:21.2039092 4260  4320  IdleTimer       [0]10A4.10E0::04/12/2017-09:55:21.203 [agent]WU operation (DL.UpdateOrchestrator, operation # 84) stopped; does<NULL> use network; is<NULL> at background priority<NULL>
    2017-04-12 09:55:21.2039111 4260  4320  Agent           [0]10A4.10E0::04/12/2017-09:55:21.203 [agent]Released network PDC reference for callId {242031C5-4C8B-4671-9D82-9BB9D3EB82FE}; ActivationID: 84
    2017-04-12 09:55:21.2039159 4260  4320  IdleTimer       [0]10A4.10E0::04/12/2017-09:55:21.203 [agent]WU operation (DL.UpdateOrchestrator) started; operation # 94; does<NULL> use network; is<NULL> at background priority<NULL>
    2017-04-12 09:55:21.2039234 4260  4320  Agent           [0]10A4.10E0::04/12/2017-09:55:21.203 [agent]Obtained a network PDC reference for callID {242031C5-4C8B-4671-9D82-9BB9D3EB82FE} with No-Progress-Timeout set to 4294967295; ActivationID: 94.
    2017-04-12 09:55:21.2040505 4260  3992  Agent           [0]10A4.0F98::04/12/2017-09:55:21.204 [agent]WU client calls back to download call {242031C5-4C8B-4671-9D82-9BB9D3EB82FE} with code Call progress and error 0
    2017-04-12 09:55:21.2055040 4260  1832  DownloadManager [0]10A4.0728::04/12/2017-09:55:21.205 [agent]Dynamic download data fetcher for ServiceId 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 does not exist.
    2017-04-12 09:55:21.2057499 4260  1832  DownloadManager [0]10A4.0728::04/12/2017-09:55:21.205 [agent]Dynamic download data fetcher for ServiceId 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 does not exist.
    
    2017-04-12 09:55:40.4165121 4260  3472  DownloadManager [0]10A4.0D90::04/12/2017-09:55:40.416 [agent]Avoiding download as update is already marked complete.
    2017-04-12 09:55:40.4210388 4260  3472  DownloadManager [0]10A4.0D90::04/12/2017-09:55:40.421 [agent]All files for update 67FB57D6-A766-4EB3-9C94-E52E30754DB6.201 were already downloaded and are valid.
    2017-04-12 09:55:40.4224584 4260  3472  DownloadManager [0]10A4.0D90::04/12/2017-09:55:40.422 [agent]* END * Download Call Complete Call 3 for caller UpdateOrchestrator has completed; signaling completion.
    2017-04-12 09:55:40.4286458 4260  3472  DownloadManager [0]10A4.0D90::04/12/2017-09:55:40.428 [agent]Dynamic download data fetcher for ServiceId 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 does not exist.
    2017-04-12 09:55:40.4286494 4260  3472  Agent           [0]10A4.0D90::04/12/2017-09:55:40.428 [agent]DownloadHeartbeat - Download complete failed with hr=80240007
    2017-04-12 09:55:40.4293311 4260  3472  Agent           [0]10A4.0D90::04/12/2017-09:55:40.429 [agent]Effective power state: AC; IsOnAC: Yes.
    2017-04-12 09:55:40.4293327 4260  3472  IdleTimer       [0]10A4.0D90::04/12/2017-09:55:40.429 [agent]WU operation (DL.UpdateOrchestrator, operation # 90) stopped; does<NULL> use network; is<NULL> at background priority<NULL>
    2017-04-12 09:55:40.4293339 4260  3472  Agent           [0]10A4.0D90::04/12/2017-09:55:40.429 [agent]Released network PDC reference for callId {1C6E21BC-E2F1-421B-9955-25B0D54FD8C9}; ActivationID: 90
    2017-04-12 09:55:40.4293505 4260  3992  Agent           [0]10A4.0F98::04/12/2017-09:55:40.429 [agent]download call is <NULL> finished
    2017-04-12 09:55:40.4347338 4260  3472  DownloadManager [0]10A4.0D90::04/12/2017-09:55:40.434 [agent]Avoiding download as update is already marked complete.

     

    Wednesday, April 12, 2017 8:13 AM
  • after giving the machine internet right the process continues.

    without internet acces for teh machine (normal in our mdt process street) it's NOt working

    Wednesday, April 12, 2017 8:31 AM
  • Hi Matthew Koeman (NL),

    I have checked the symptom on my WSUS environment(server 2012 R2). The Windows 10 1703 could update from WSUS well.

    Please upload the full windowsupdate log to OneDrive and paste the link here.

    Best regards


    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 14, 2017 6:45 AM
    Moderator
  • my WU logs  from a fresh mdt rollout 
    https://1drv.ms/u/s!AjYOdnayF8npgfYod10vIxRhFG8Dsg

    more issues like this are appearing :

    https://social.technet.microsoft.com/Forums/en-US/73d6ac20-cbf5-4e0e-8bd2-53b987df7814/windows-10-1703-enterprise-download-stuck-at-0-from-wsus?forum=win10itprogeneral

     

    Saturday, April 15, 2017 8:21 PM
  • Hi Matthew Koeman (NL,

    There is one key point I want to confirm. Do you mean the update package or upgrade package?

    If you mean the upgrade pacakge, please try to add the MIMI type with .esd.

    For the Windowsupdate.log, please open a powershell command line and run "get-windowsupdatelog" then upload the log here.

    Best regards

    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 19, 2017 8:08 AM
    Moderator
  • Hi, I mean the update ......

    We rollout W10 1703, during rollout, clients cannot dowload UPDATES from the W2016 wsus server.
    it stays @ downloading 0% (and 10 mdt try's)

    also installing manualy w10 1703 Ent. doesnt allow us downloading updates from the wsus server.

    if i pick a task with W10Ent. 1607  all works perfect. here are the created logs : https://1drv.ms/u/s!AjYOdnayF8npgfZOs-h_YOQ_grkvmw

    also on W2016 Wsus server the .esd is already registerd as MIME type by default as application/vnd.ms-cab-compressed  ( checked again....)



    Wednesday, April 19, 2017 8:34 PM
  • Hi,

    I have this problem, too.

    The upgrade to 1703 is ok, but after this the Client stocks at 0% in my test-lab, where is no internet connection. When this client becomes internet access, the download begins (then the updates are downloaded from the wsus-server).

    I've tested with an upgrade to 1703 via WSUS, upgrade via ISO, new install of 1703, the problem is the same.

    best regards

    Friday, April 21, 2017 8:45 AM
  • Hi SStehl,

    "but after this the Client stocks at 0% in my test-lab, where is no internet connection. When this client becomes internet access, the download begins (then the updates are downloaded from the wsus-server)."
    Do you mean the issue will be resovled after we updating from Windows Update directly?

    Best regards

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

    Monday, April 24, 2017 9:56 AM
    Moderator
  • Hi Matthew Koeman (NL),

    How about the issue, is there anything to update? Have you tried to update from Windows Update then update from WSUS?

    According to the windowsupdate.log, there are many errors "Failed to retrieve SLS response data for service 117cab2d-82b1-4b5a-a08c-4d62dbee7782, error = 0x80040154".
    Try to clear the Windows Update cache then check the symptom again.
    Clear the windows update cache.
    net stop wuauserv
    cd %systemroot%\SoftwareDistribution
    ren Download Download.old
    net start wuauserv
    Restart the machine and manually check for updates again

    Best regards

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

    Monday, April 24, 2017 10:07 AM
    Moderator
  • Same issue here... Did you find the solution?
    Monday, April 24, 2017 10:32 AM
  • Hi meipoXU,

    This is a new MDT Rollout, cq a brand new machine .
    during the MDT rollout it trys 10times to cal WSUS dor updates.

    every new W1703 rollout has the same problem
    Even i think it can't be it, i did clean the cache and tried again.
    No FIX

    when we gave the machine internet access, i see about 1mb data traffic in the firewall to/from the pc
    and after that the updates are downloaded from wsus.
     

    Monday, April 24, 2017 1:19 PM
  • no solution yet....:s
     ... in the meanwhile i just created a ticked with MS (117042415641571) to address this problem 
    Monday, April 24, 2017 1:21 PM
  • Just curious, are you using any updates from SCUP?  I had this issue in my SCCM environment,  after carefully pruning the Dell catalog to the updates I needed (and removing metadata-only updates),  my scans succeeded...

    • Proposed as answer by pcsnm505 Thursday, May 11, 2017 9:20 PM
    Monday, May 01, 2017 9:23 PM
  • Hi,

    I have this problem, too.

    The upgrade to 1703 is ok, but after this the Client stocks at 0% in my test-lab, where is no internet connection. When this client becomes internet access, the download begins (then the updates are downloaded from the wsus-server).

    I've tested with an upgrade to 1703 via WSUS, upgrade via ISO, new install of 1703, the problem is the same.

    best regards

    I can confirm this. We have exactly the same problem!

    Wednesday, May 03, 2017 7:33 AM
  • Hi MeipoXu,

    when the Client has no internet connection (private switch in Hyper-V), it show's short the updates, that he want's to download. After this the updatestatus shows that updates are downloading. But nothing downloads and the percentage stays at 0%

    When I change the client network to public and after an ipconfig renew, the clients starts download and install the updates.

    In the state without internet connection, the client doesn't call his status at the WSUS-Server. With internet connection, also the status at the WSUS-Server is updated.

    Best regards

    Thursday, May 04, 2017 9:07 AM
  • Hi Matthew,

    Have you heard anything from MS yet?

    All of our 1703 clients also get this error in Wuahandler.log 
    "OnSearchComplete - Failed to end search job. Error = 0x8024000d"

    Thursday, May 04, 2017 11:50 AM
  • Any update to this by now?
    Monday, May 08, 2017 12:23 PM
  • I too am having this issue.

    Does anyone have any updates?

    Many thanks,

    Lee

    Tuesday, May 09, 2017 2:53 PM
  • No fix with recently released KB4016871
    Wednesday, May 10, 2017 7:21 AM
  • I am also experiencing this with all 1703 workstations.
    Wednesday, May 10, 2017 9:56 PM
  • I have been trying to diagnose this problem and am just sharing some observations.
    We use a python script tool to automate the download of update patches and install them.
    What I have noticed from my use of this tool is that it "thinks" it is able to download the files, but never REALLY attempts to download them. I have run Fiddler to capture the traffic and seen that I get all of the sequence fromthe WSUS<->Client (basically steps 1-7 from the following https://msdn.microsoft.com/en-us/library/gg258073.aspx) but the updates themselves NEVER download, as is mirrored by the GUI. But I have noticed that wermgr.exe is kicking in at the point that the downloads should be starting. So it seems that the Windows Update client is crashing on getting the information required to evaluate from WSUS. Not having much luck capturing the dump files that should be generated, but still trying.

    David J. This posting is provided "AS IS" with no warranties, and confers no rights. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Wednesday, May 10, 2017 11:44 PM
  • Just curious, are you using any updates from SCUP?  I had this issue in my SCCM environment,  after carefully pruning the Dell catalog to the updates I needed (and removing metadata-only updates),  my scans succeeded...

    For those of you that are still experiencing this issue, I seriously suggest you take a good look at Julian's post here. It resolved our issue here in our environment.  

    More specifically...0x8024000d

    Thursday, May 11, 2017 9:22 PM
  • The problem with removing metadata-only updates is they're in there so we can work out what full updates we need to publish!
    Friday, May 12, 2017 9:19 AM
  • Not using SCCM and no updates imported to WSUS.
    Therefore, this does not solve my problem - unfortunately.
    Friday, May 12, 2017 9:32 AM
  • I too am not using SCCM...so, problem still remains!
    Friday, May 12, 2017 11:12 AM
  • BTW, I think I have found the answer to this issue in another forum post:
    https://social.technet.microsoft.com/Forums/en-US/bbfa477f-0290-4f71-bd9b-da03174f510d/windows-10-1703-build-15063-updates-are-available-from-wsus-stuck-at-downloading-updates-0?forum=winserverwsus

    GPEdit-> Computer Configurations>Administrative Templates>Windows Components>Delivery Optimization>Download Mode>Bypass
    Reboot and updates are able to download and install properly

    David J. This posting is provided "AS IS" with no warranties, and confers no rights. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Friday, May 12, 2017 12:32 PM
  • Already tried this ... to no avail.
    Friday, May 12, 2017 12:41 PM
  • This solved it for us!

    First set all "published metadata only" to expire in SCUP then follow this guide https://patchmypc.net/scupcatalog/documentation/CleaningUpExpiredUpdates.pdf



    • Edited by GleSax Wednesday, May 17, 2017 12:18 PM
    Wednesday, May 17, 2017 11:56 AM
  • We use WSUS only - so this does not solve it for me.
    Wednesday, May 17, 2017 12:23 PM
  • If you trying to solve this issue, you may have some kind of WSUS cleanup in place.
    And if this is your first 1703 installation, the updates could have been cleaned because there are no computers needing this updates.
    If you then search for them it could take a long time for the WSUS to download the updates and deliver then to the client.
    I thought, that i had no luck with setting the "Download Mode" to "Bypass", but that solved the issue for me.
    I used the following command with a reboot after in our MDT. After that my client was able to download updates from our WSUS.

    reg.exe add "HKLM\SOFTWARE\Policies\Microsoft\Windows\DeliveryOptimization /f /v DODownloadMode /t REG_DWORD /d 100"

    At about the same time i was experimenting with the 1703 build, i noticed that our WSUS application pool in IIS was a bit more memory hungry that usual. I could not get updates on some (not even 1703) machines. After i raised the memory limit a bit, it worked again. So that is something to keep an eye on.

    I'm sure you did, but make sure, that you have prepared your WSUS and IIS for ESD Updates:
    https://blogs.technet.microsoft.com/wsus/2016/09/21/resolving-error-0xc1800118/

    Edit: wsusutil.exe reset could help, too if the cause are corrupt updates.

    If you don't use the integrated database, check your "Remote query timeout" in the SQL Server Management Studio under Server Properties.


    Tuesday, May 23, 2017 5:17 PM
  • Read my last post here to see the solution for my issue.
    Thursday, May 25, 2017 12:24 PM
  • I must revoke my answer. I still have problems with 1703 images getting updates. I don't know why it worked one time.

    I think i have to go the same route as McLion. I will  I let you know if this solved my issue.

    Thursday, May 25, 2017 2:06 PM
  • Removing old SCUP categories and metadata fixed it for me as Julian mentioned previously.

    https://scif.codeplex.com/wikipage?title=%20Deleting%20WSUS%20Updates&ProjectName=scif

    https://www.reddit.com/r/SCCM/comments/6ae3zl/sccm_1702_windows_10_1703_machines_not_receiving/


    Friday, May 26, 2017 4:45 PM
  • Any Update? Tried everything!

    -Made a brand new WSUS with Server 2016

    -use of newest PolicyDefinitions

    -WSUS with SSL

    -tried downloadmode bypass

    Every client with no internet access is still stuck at 0% downloading updates :(

    Wednesday, June 21, 2017 8:13 AM
  • Try installing the new Commutative Update: http://www.catalog.update.microsoft.com/Search.aspx?q=KB4022716

    And this:

    [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate]

    "DoNotConnectToWindowsUpdateInternetLocations"=dword:00000001

    [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DeliveryOptimization]

    "DODownloadMode"=dword:00000100

    For me it finally worked. Microsoft fixed something in the Update Agent.
    My 1703er Version found updates after about 20 Seconds.

    See: https://social.technet.microsoft.com/Forums/en-US/55a42d60-1432-4ab3-8804-1efede6788af/windows-10-1703-and-wsus?forum=win10itprogeneral

    Tuesday, July 04, 2017 3:46 PM
  • I can confirm this. The KB4022716 fixed the issue in our environment as well.
    Nothing else has been changed on the client.
    Wednesday, July 05, 2017 6:21 AM
  • I can confirm this. The KB4022716 fixed the issue in our environment as well.
    Nothing else has been changed on the client.

    Still doesn't work for us. We didn't have the 0x8024000d error. The update agent just hangs at 0% when the client has no internet connection. We never get any error code. Seems the fix is not for this error :(

    Wednesday, July 05, 2017 12:09 PM
  • I am getting this same problem and I am getting a long log file.
    Tuesday, July 11, 2017 5:31 PM
  • Finally i was able to find the reason why this is happening!

    You should not configure any defer or pause policys for feature or quality updates since they are only for standalone devices and windows update for business and not for managed clients with wsus. 

    More information about this:
    https://blogs.technet.microsoft.com/windowsserver/2017/01/09/why-wsus-and-sccm-managed-clients-are-reaching-out-to-microsoft-online/

    • Proposed as answer by RZ-BV Friday, July 14, 2017 7:30 AM
    Friday, July 14, 2017 7:30 AM