Error: Unable to find resource while trying to upgrade to Windows 10 1709 Enterprise through WSUS

While upgrading to Windows 10 1709 Enterprise via WSUS your clients may report the following error:

(Unable to find resource):ReportingEvent.Client.167; Parameters: Feature update to Windows 10 (business editions), version 1709, en-us

This may happen to other versions too

In this case your IIS may be missing the “.esd” mime type. If so, add it and check for updates again:

1) Go to your WSUS

2) Open IIS, select server’s name and double click on “Mime Types”

3) Add new mime type:

Filename extension: .esd
Mime type: application/octet-stream

4) Click OK and try to search for updates on your computers

Note that if you have many clients they may flood your network (especially 100MB ones) since the update is 3GB+

The problem should be solved.

In theory KB3095113 should had added this mime type. But if you add WSUS role after KB3095113, your IIS will not have .esd mime type and you should add it manually.

13 thoughts on “Error: Unable to find resource while trying to upgrade to Windows 10 1709 Enterprise through WSUS

  1. Ding ding ding! This did the trick for me. I could not get a feature update for Windows 10 1809 to download (my computer new it needed the update but was stuck at 0% download). Adding this mime type fixed the downloading issue within 3 minutes and I did not have to restart any services on WSUS or the client machine.

    Thank you very much for this tip Petar

  2. Thanks!!!
    I had same issue as Jonathan and now WIndows 10 is updating after adding the MIME type

  3. Thanks, it worked for me. User can download the package.
    Unfortunately he gets other error. (Feature update windows 10(Consumer edittion) v1803, en-us,error 0xc1900131.

  4. I´ll try this solution.
    Since they appear together sometimes, I wonder if this solution also solves the “(Unable to Find Resource:) ReportingEvent.Client.181; Parameters:” issue…
    Does anyone know?

  5. I am getting same error.

    I am running wsus on server 2019

    When I go to add the extension it is already there, but the MIME type is:\

    • I have the same issue


      Any idea about whether to change this ?

  6. Thanks a lot guys,

    after i tried many troubleshoot, at last i found this trick and it works fine.

  7. i have the same issu but the filename .esd alrady exist and i can’t install the update Windows 10

  8. application/ here as well. Do we need to change it to octet-stream?

  9. Sorry application/ is the correct. I just copied from above comment.

Leave a Reply

Your email address will not be published. Required fields are marked *