Oct 182017

Well, it’s October 18th 2017 and the Fall Creators update (Feature update to Windows 10, version 1709) is now available for download. In my particular environment, I use WSUS to deploy and manage updates.

I went ahead earlier today and approved the updates for deployment, however I noticed an issue on multiple Windows 10 machines, where the Windows Update client would get stuck on Downloading updates 0% status.

I checked a bunch of things, but noticed that it simply couldn’t download the updates from my WSUS server. Further investigation found that the feature updates are packaged in .esd files and IIS may not be able to serve these properly without a minor modification. I remember applying this fix in the past, however I’m assuming it was removed by a prior update on my Windows Server 2012 R2 server.

If you are experiencing this issue, here’s the fix:

  1. On your server running WSUS and IIS, open up the IIS manager.
  2. Expand Sites, and select “WSUS Administration”
  3. On the right side, under IIS, select “MIME Types”
  4. Make sure there is not a MIME type for .esd, if there is, you’re having a different issue, if not, continue with the instructions.
  5. Click on “Add” on the right Actions pane.
  6. File name extension will be “.esd” (without quotations), and MIME type will be “application/octet-stream” (without quotations).
  7. Reset IIS or restart WSUS/IIS server

You’ll notice the clients will not update without a problem! Happy Updating!

  27 Responses to “Windows 10 Fall Creators Update stuck on “Downloading Updates” from WSUS”

  1. Saved my day! Thank you! MS still doesn’t have official solution for this. Can’t believe them.

  2. Thank you this is exactly what I needed to resolve the dreaded 0% downloaded for 1709.

  3. Thank you the Download of 1709 runs now.

  4. Thank you – the soltion works well and now my updates are downloaded from the wsus server.

  5. Many thanks for a very simple and efficient solution. Greetings from Poland!

  6. Thank you very much, this solved our problem too.

  7. We had same issue, thanks for the quick fix! Microsoft’s technet was no help. Now all my upgrades are flying out the door. Many thanks!

  8. Thanks so much. Not like there was anything I could find from MS on this. Though AV, appreciate it greatly.

  9. Thank you very much, this solved our problem too.!

  10. Many thanks for that, the problem had been driving me crazy for the last 2 weeks, well, the last week not, I was on leave, but got back this morning to find my test machines still hadn’t been updated.

    Applied the patch and et voilá!

  11. gopher: Worth noting that this is Microsoft’s official solution, albeit their instructions are a bit disorganized and scattered. 2012 R2 pre-dates Windows as a Service, so the ability to service Windows with feature updates via WSUS had to be patched in. (A few KBs through Windows Update, plus this IIS MIME type. And in some cases, a post-install servicing command) Server 2016 and newer natively support .esd decryption/delivery for servicing Windows with feature updates.

  12. many many Thanks!

  13. thank you ! works great! save my day!

  14. Thank you very much.

  15. Great !!!!!
    “Feature Update to Windows 10, Version 1709, en-us” downloading started immediately after above fix !
    A Big Thanks to Stephen !! : )

  16. Super great works like a charm

  17. Thanks!! Works like a charm

  18. Excellent. Thank you!

  19. Perfect! THANK YOU!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

  20. Hi ,
    Your solution worked with me too. The only thing is I dont want to have the 1709 installed on my computers. Any ideas how to control that? The update was never approved on my WSUS server….


  21. Hi Diego,

    The update either needs to be approved for deployment, or the computers have to directly check Microsoft Update for it to be deployed.

    It shouldn’t have deployed by itself.

    In my case, on my workstations, it wouldn’t even show the fall creators update initially on WSUS, so for those machines I had to download from Microsoft Update (Windows Update) directly. Only later on did it show up on WSUS, in which I had to approve it.


  22. Lot of pc blocked waiting for an update that it was impossibile to download from my internal WSUS.
    Applayed your trick and everything restart working as it has to do!
    Really thanks for sharing this solution!

  23. Worked for me as well — just wanted to say thanks!

  24. Thank you! .. That resolved my issue as well. Why can’t MS publish that solution as precisely as you did? and as easy to find?
    Great job!

  25. Please help. I approved “Feature Update to Windows 10, version 1709, en-us” on WSUS but File status is “The update is downloading” for a week. On IIS, .esd is available with MIME type application/vnd.ms-cab-compressed. Should I add new MIME Type “application/octet-stream”?

  26. Hello NJ,

    I can’t really answer your questions as I haven’t tried it your way using “application/vnd.ms-cab-compressed”, however I would recommend changing to “application/octet-stream” as I know this works.

    I would also recommend resetting Windows Update on the hosts that are having issues downloading.

    Also and finally, make sure that you have the appropriate patches installed to enable Windows 10 update support on your WSUS serrver.


  27. Thanks so much for this. Applied the fix and downloads started immediately.

 Leave a Reply

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>