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.
Update: It’s now May 2018, and this article also applies to Windows 10 April 2018 update version 1803 as well!
Update: It’s now October 2018, and this article also applies to Windows 10 October 2018 update version 1809 as well!
Update: It’s now May 2019, and this article also applies to Windows 10 May 2019 update version 1903 as well!
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:
- On your server running WSUS and IIS, open up the IIS manager.
- Expand Sites, and select “WSUS Administration”
- On the right side, under IIS, select “MIME Types”
- 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.
- Click on “Add” on the right Actions pane.
- File name extension will be “.esd” (without quotations), and MIME type will be “application/octet-stream” (without quotations).
- Reset IIS or restart WSUS/IIS server
You’ll notice the clients will now update without a problem! Happy Updating!