none
FIX: Domain Windows 10 WSUS Upgrade Issues File Not Found

    General discussion

  • Hi,

    (posted this in the consumer section and got pointed in this direction)

    We were having an issue with the Windows 10 upgrade MS recently released to WSUS server on our domain. To put a long story short the issue is in IIS and NOT WSUS per say. After some testing it turns out IIS was not serving the .esd file (this is the main update file) due to the mime type not being set. To rectify the issue:

    under IIS Admin->WSUS Administration->Content-> Click on "Mime Types"-> Add

    File Mame Extention:  = .esd

    MIME type:     application/vnd.ms-cab-compressed

    If you have already tried to pull the W10 update you may need to clear your SoftwareDistribution Download Cache under the Windows Dir and clear out the hidden $WINDOWS.~BT

    EDIT:

    The actual mime type for esd, accordion to http://www.filesuffix.com/en/extension/esd, is "application/octet-stream".

    The following is just to help people find this post:

    {5E024B59-62F0-4BA2-A5C0-234D4DCBA9AE}    2015-12-09 09:06:41:558-0000    1    147 [AGENT_DETECTION_FINISHED]    101    {00000000-0000-0000-0000-000000000000}    0    0    UpdateOrchestrator    Success    Software Synchronization    Windows Update Client successfully detected 1 updates.
    {35D02FEB-18F0-4392-ADD2-FBCD30EBD7F7}    2015-12-09 09:06:41:558-0000    1    156 [AGENT_STATUS_30]    101    {00000000-0000-0000-0000-000000000000}    0    0    UpdateOrchestrator    Success    Pre-Deployment Check    Reporting client status.
    {71A6337E-6A4F-45E2-8AA7-89A47DB17077}    2015-12-09 09:06:41:777-0000    1    167 [AGENT_DOWNLOAD_STARTED]    101    {451DFCEE-1974-4A96-8D41-E1BFB766402E}    201    0    UpdateOrchestrator    Success    Content Download    Download started.
    {E84D391E-4AF2-4846-910A-2F6692FAA4CA}    2015-12-09 09:06:44:071-0000    1    162 [AGENT_DOWNLOAD_SUCCEEDED]    101    {451DFCEE-1974-4A96-8D41-E1BFB766402E}    201    0    UpdateOrchestrator    Success    Content Download    Download succeeded.
    {32E1A8AD-6AE7-47FC-B350-3FED71B5B469}    2015-12-09 09:06:44:118-0000    1    181 [AGENT_INSTALLING_STARTED]    101    {451DFCEE-1974-4A96-8D41-E1BFB766402E}    201    0    UpdateOrchestrator    Success    Content Install    Installation Started: Windows has started installing the following update: Upgrade to Windows 10 Pro, version 1511, 10586
    {2164101C-1E96-4F90-8358-AB69D4C9CFBF}    2015-12-09 09:06:51:220-0000    1    147 [AGENT_DETECTION_FINISHED]    101    {00000000-0000-0000-0000-000000000000}    0    0    Dynamic Update    Success    Software Synchronization    Windows Update Client successfully detected 0 updates.
    {AEF7A6D5-E637-4D7F-9F87-09E5A972D202}    2015-12-09 09:09:09:514-0000    1    182 [AGENT_INSTALLING_FAILED]    101    {451DFCEE-1974-4A96-8D41-E1BFB766402E}    201    8024200d    UpdateOrchestrator    Failure    Content Install    Installation Failure: Windows failed to install the following update with error 0x8024200d: Upgrade to Windows 10 Pro, version 1511, 10586.
    {E0043FE0-C513-4857-86C5-584E2A66BA1C}    2015-12-09 09:09:09:951-0000    1    167 [AGENT_DOWNLOAD_STARTED]    101    {451DFCEE-1974-4A96-8D41-E1BFB766402E}    201    0    UpdateOrchestrator    Success    Content Download    Download started.
    {267B22CB-5F44-4CD3-A7E3-D73B5E4869C8}    2015-12-09 09:09:10:154-0000    1    161 [AGENT_DOWNLOAD_FAILED]    101    {451DFCEE-1974-4A96-8D41-E1BFB766402E}    201    80244019    UpdateOrchestrator    Failure    Content Download    Error: Download failed.
    {7649D8C6-37CE-4F12-96DA-9976640E71DF}    2015-12-09 09:09:30:835-0000    1    147 [AGENT_DETECTION_FINISHED]    101    {00000000-0000-0000-0000-000000000000}    0    0    UpdateOrchestrator    Success    Software Synchronization    Windows Update Client successfully detected 1 updates.
    {2855AA41-E40B-40CF-80B7-978574BA4771}    2015-12-09 09:09:30:835-0000    1    156 [AGENT_STATUS_30]    101    {00000000-0000-0000-0000-000000000000}    0    0    UpdateOrchestrator    Success    Pre-Deployment Check    Reporting client status.
    {6A9643F1-1AAE-4421-90B3-FFE018CC7721}    2015-12-09 09:09:31:225-0000    1    161 [AGENT_DOWNLOAD_FAILED]    101    {451DFCEE-1974-4A96-8D41-E1BFB766402E}    201    80244019    UpdateOrchestrator    Failure    Content Download    Error: Download failed.
    Friday, December 18, 2015 9:58 AM

All replies

  • Hi,

    Thanks for the sharing!

    Your time and efforts are highly appreciated!

    Best Regards,


    Steven Lee Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Tuesday, January 12, 2016 8:51 AM
    Moderator
  • Thank you for sharing this solution!

    I lost a lot of time performing troubleshooting on client computers and a lot of research on the Internet to find it. Something that should be transparent to users of the WSUS service. I believe that Microsoft should improve this and perform this required configuration of IIS via Windows Update or at least share it officially.


    Alex Felipe Hilleshain MCP, MCDST, MCITP Windows 7

    Friday, July 1, 2016 4:11 PM
  • https://support.microsoft.com/en-us/kb/3159706
    Update enables ESD decryption provision in WSUS in Windows Server 2012 and Windows Server 2012 R2

    Don [doesn't work for MSFT, and they're probably glad about that ;]

    Saturday, July 2, 2016 10:15 AM