none
Windows 10 1607 Anniversary Update Fails via WSUS 0x80244019

    Question

  • Hi All,

    The Windows 10 Anniversary Update has been approved for install on our Windows 2012 WSUS Server. Each Windows client currently runs 1511 with all updates installed and when trying to install 1607 errors with 0x80244019

    The feature update version is Windows 10 Pro, Version 1607, en-gb, Retail

    WSUS is patched with KB3159706 as discussed so I cannot see any issues there.

    A little stuck at this time so any thoughts or suggestions appreciated as this affects all clients on the network.

    Thanks

    Craig

    Thursday, August 18, 2016 1:11 PM

Answers

  • Try adding the mime type below in IIS on the WSUS server. That resolved it for me.

    .esd - application/octet-stream

    • Marked as answer by TowelsRus Friday, August 19, 2016 8:06 AM
    Thursday, August 18, 2016 4:28 PM

All replies

  • Try adding the mime type below in IIS on the WSUS server. That resolved it for me.

    .esd - application/octet-stream

    • Marked as answer by TowelsRus Friday, August 19, 2016 8:06 AM
    Thursday, August 18, 2016 4:28 PM
  • Craig,

    Try reading through this if you haven't already. There are some manual post installation tasks you need to complete after installing KB3159706 to get this working.

    https://blogs.technet.microsoft.com/wsus/2016/05/05/the-long-term-fix-for-kb3148812-issues/

    Adrian


    Thursday, August 18, 2016 5:20 PM
  • Hi,

    Thanks for this. I found a article late yesterday regarding this so it is now functioning and rolled out to to all clients

    Thanks for the help.

    Craig

    Friday, August 19, 2016 8:07 AM
  • "Try adding the mime type below in IIS on the WSUS server. That resolved it for me.

    .esd - application/octet-stream"

    Yes -- this worked for us as well. This was causing the installation of the 1607 (Anniversary Edition) upgrade to fail on all our Windows 10 Pro boxes, even though we had built a new 2012 R2 Server and enabled the WSUS role (and thus were running WSUS 6.3) specifically to avoid issues with WSUS 3.2 and the new "Upgrade" class of update.

    Notes:

    • I restarted IIS and then clicked Try Again on the client, it then worked immediately.
    • I added it to Mime types on the IIS server node, not the WSUS Admin node -- it probably works both ways.
    • Also, we were getting error 10032 ("The server is failing to download some updates") in the Application Event Log on the box running the WSUS server. It hasn't been fixed for long enough here to be sure that issue is also resolved.


    • Edited by Alatar Sunday, August 21, 2016 7:43 PM Add quote of original solution
    • Proposed as answer by pcarlosu Tuesday, October 18, 2016 3:29 PM
    Sunday, August 21, 2016 7:42 PM
  • Brilliant ;)

    Made my day. Tks.

    Thursday, August 25, 2016 2:40 PM
  • "Try adding the mime type below in IIS on the WSUS server. That resolved it for me.

    .esd - application/octet-stream"

    ----------------------------------------------------------------------------------------------

    Yes!  This worked for me also.  Thank you for posting! :)

    • Edited by Evin.Kaless Friday, August 26, 2016 4:24 PM
    Friday, August 26, 2016 4:21 PM
  • hit it perfectly!! thanks
    Tuesday, August 30, 2016 1:33 PM
  • Try adding the mime type below in IIS on the WSUS server. That resolved it for me.

    .esd - application/octet-stream


    Good!!
    Wednesday, September 7, 2016 7:20 AM
  • I'm in the same boat.  No users can install 1607 updates from our WSUS server  Does anyone have a suggestion for fixing this?  So far I've:

    1)  Set .esd - application/octet-stream in IIS
    2)  Checked and 8812 is not installed
    3)  KB3159706 has been installed since 5/18 (date it's listed as installed in Control Panel, Installed Updates)

    4) Server cleanup wizard has been run and completes.  I also have Adamj's script running and it cleaned up all our WSUS server.

    What am I missing?  I don't see where to "uninstall test package" as in step 1.  
    Any help would be greatly appreciated!  Thanks


    • Edited by JonGlenn1 Thursday, September 29, 2016 12:08 PM
    Thursday, September 29, 2016 12:06 PM
  • I've been racking my brains all morning and found your post! Worked for me too. Thanks!
    Tuesday, October 11, 2016 12:36 PM
  • Try adding the mime type below in IIS on the WSUS server. That resolved it for me.

    .esd - application/octet-stream

    Top Answer, now it works as expected. Thanks!

    Wednesday, October 12, 2016 10:08 AM
  • Fixed our problem.  Thank you!
    Saturday, October 15, 2016 5:50 PM
  • This fixed it for me. Only a few words come to my mind at this point. Like 'fuck microsoft', or 'fuck windows'. I don't know. Maybe it's just me.
    Saturday, October 15, 2016 11:51 PM
  • there is an .esd mime type already, do you edit it to match, or create a new one?
    Friday, December 9, 2016 8:58 PM
  • You beautiful person, I've just had this (we've been sat on 1511 for a while as only hand a handful of Win 10 devices)

    May I ask, how, HOW, did you know to do that?

    Thursday, December 29, 2016 5:17 PM
  • Helped for me after doing manual post installation tasks after installing KB3159706 and adding .esd mime type to the IIS server node.

    Thank You!


    Tuesday, January 17, 2017 7:42 AM
  • Hello All,


    The fix forme on the generation of the Windows Update Error, 0x80244019 on Windows 10 Enterprise; was ensuring the GPO (at the minimum) for WSUS had the "Specify intranet Microsoft Update service location" and "Configure Automatic Updates" defined.

    These are virtual intances on VMWare 6.0/vSphere Client 11.x and I also unmounted the CD/DVD drives for all of them; not entirely sure this could cause the error to occur, figured I'd include all variables.


    GhostKev

    Monday, January 30, 2017 6:12 PM
  • I proced to Add Mime types on the IIS server node, not the WSUS Admin node.

    The problem was resolve

    Monday, April 24, 2017 3:27 AM
  • in my case, creating the esd mime type worked perfectly

    but the issuee remains:

    how it happens? why a old product, well-tested, widely used have this kind of problem and there is no KB talking about? why to find the solution on "non-official" channels, like foruns, blogs, etc?

    IN my case:

    DownloadManager Update E4BBFE72-DDD9-4E59-A45E-7E94923B80BD.200 is missing decryption information
    Handler         Windows Setup handler requesting file '14393.0.161119-1705.rs1_refresh_CLIENTENTERPRISE_VOL_x64fre_en-us.esd'

    some lines, maybe related:

    DownloadManager Update E4BBFE72-DDD9-4E59-A45E-7E94923B80BD.200 is missing decryption information
    DownloadManager P2P Download job 98A71076-8DEA-409F-A6B0-4347E641AD59 failed to resume, queueing redownload.
    DownloadManager Update E4BBFE72-DDD9-4E59-A45E-7E94923B80BD.200 is missing decryption information
    DownloadManager All files for update {E4BBFE72-DDD9-4E59-A45E-7E94923B80BD}.200 were already downloaded and are valid.
    Agent             Title = Feature update to Windows 10 Enterprise, version 1607, en-us
    Handler         Updates to install = 1
    Handler         Registering WinSetup COM server as CLSID {1704E45D-E692-44BE-908C-A628CF294E13} and APPID {8F41F478-8266-47B2-B503-D8300FC50DCF}
    Handler         Successfully registered WinSetup COM server as CLSID {1704E45D-E692-44BE-908C-A628CF294E13}
    Handler         Installer completed. Process return code = 0x00000000, result = 0x00000000, callback pending = True
    Handler         State changed. was: Setup360_CompatToolPhase1(5), now: Setup360_Phase2DownloadRequest(7)
    Handler         Exit code = 0x8024200D
    DownloadManager Install failed because the update {E4BBFE72-DDD9-4E59-A45E-7E94923B80BD} was not complete; mark update as not downloaded.
    ComApi          Exit code = 0x00000000; Call error code = 0x80240022
    DownloadManager Updates to download = 1
    Agent             Title = Feature update to Windows 10 Enterprise, version 1607, en-us
    DownloadManager Update E4BBFE72-DDD9-4E59-A45E-7E94923B80BD.200 is missing decryption information
    Handler         Windows Setup handler requesting file '14393.0.161119-1705.rs1_refresh_CLIENTENTERPRISE_VOL_x64fre_en-us.esd'
    Handler         Loaded state. m_dwState now: Setup360_Phase2DownloadRequest(7)
    DownloadManager Suspended update E4BBFE72-DDD9-4E59-A45E-7E94923B80BD for reason 0x40000
    DownloadManager Attempted to resume update E4BBFE72-DDD9-4E59-A45E-7E94923B80BD for reason 0x40000, update is no longer suspended afterward.
    ComApi          ISusInternal:: DisconnectCall failed, hr=8024000C
    DownloadManager DynamicDownloadDataFetcher Refresh complete. 0x8024000c

    Thursday, May 18, 2017 6:12 PM
  • I have been fighting 1709 for two weeks............ Adding this mime type did the trick big time. I wish i could have found this one sooner. Thank you very much for your post. it helped dramatically. I can move on now. :)
    Friday, November 24, 2017 3:57 PM
  • Try adding the mime type below in IIS on the WSUS server. That resolved it for me.

    .esd - application/octet-stream

    This is what I needed to get these working on WSUS 4
    Wednesday, May 2, 2018 2:51 AM