locked
Client Error Sequence in 1607 > 1809 Upgrade via WSUS - error 0x8024200d RRS feed

  • Question

  • Hi,

    Basically, I've got so much information and at this point, I don't really know where to start with it. An important thing to note, is that these upgrades of 1607 to 1809 (deployed 17763.107.101029-1455.rs5_release_svc_refresh_CLIENTBUSINESS_VOL_x64FRE_en-us.esd via WSUS) have been successful on ~85% of the ~400 clients targeted. Many of the computers that were seeing the same (or similar) sequence of errors have successfully completed with no intervention. Still, some of them are still looping through these errors and restarting at inopportune times (when the user is logged in, but the machine is locked even though the "No auto-restart with logged on users for scheduled automatic updates installations" GPO is in place)

    Here's what I've done to troubleshoot:

    1. Server 2012 R2, WSUS 6.3.9600.18838. Confirmed that WSUS and the requisite updates for feature upgrades are installed. Well, almost. I have the .esd application/octet-stream mime type enabled, and a superseding update (KB4489881) is installed. So, this supersedes KB3095113, but does it supersede the "hotfix" version of KB3095113? All that said, feature upgrades are syncing and are successfully deploying with just these few exceptions.
    2. Stopped Windows Update service on the client and renamed the SoftwareDistribution folder to .old., restarted WU service.
    3. Disabled all non-microsoft startup services.
    4. Confirmed that the WU registry settings reflect what's in the WSUS GPO.
    5. Confirmed HKEY_USERS\S-1-5-18\Software\Microsoft\Windows\CurrentVersion\WinTrust\Trust Providers\Software Publishing is 0x00023c00
    6. Disabled Symantec Endpoint Protection, tried again
    7. Removed temp files

    I honestly can't remember whether or not I ran the Windows Update Troubleshooter in this particular machine or not. That said, I'd really rather fix it myself so I can maybe solve the cause of problem as well as the problem itself.

    I've been through several different forums where different things are suggested and I often see the "(Unable to Find Resource)" events addressed, but I haven't seen anything in forums (or in the Resolution procedures that directly addresses the errors I'm seeing. Here's an example of the string of errors shown on one machine when running the report in WSUS and clicking the "failed" link:

    [machinename.domain.local]
    Feature update to Windows 10 (business editions), version 1809, en-us x64
    Event reported at 4/8/2019 11:08 PM:
    (Unable to Find Resource:) ReportingEvent.Client.167; Parameters: Feature update to Windows 10 (business editions), version 1809, en-us x64

    [machinename.domain.local]
    Feature update to Windows 10 (business editions), version 1809, en-us x64
    Event reported at 4/9/2019 1:07 AM:
    Installation successful and restart required for the following update:
    Feature update to Windows 10 (business editions), version 1809, en-us x64

    [machinename.domain.local]
    Feature update to Windows 10 (business editions), version 1809, en-us x64
    Event reported at 4/9/2019 7:57 AM:
    (Unable to Find Resource:) ReportingEvent.Client.181; Parameters: Feature update to Windows 10 (business editions), version 1809, en-us x64

    [machinename.domain.local]
    Feature update to Windows 10 (business editions), version 1809, en-us x64
    Event reported at 4/9/2019 8:00 AM:
    Installation Failure: Windows failed to install the following update with
    error 0x8024200d: Feature update to Windows 10 (business editions), version 1809, en-us x64

    [machinename.domain.local]
    Feature update to Windows 10 (business editions), version 1809, en-us x64
    Event reported at 4/9/2019 8:03 AM:
    (Unable to Find Resource:) ReportingEvent.Client.181; Parameters: Feature update to Windows 10 (business editions), version 1809, en-us x64

    [machinename.domain.local]
    Feature update to Windows 10 (business editions), version 1809, en-us x64
    Event reported at 4/9/2019 8:03 AM:
    Download succeeded.

    [machinename.domain.local]
    Feature update to Windows 10 (business editions), version 1809, en-us x64
    Event reported at 4/9/2019 8:03 AM:
    (Unable to Find Resource:) ReportingEvent.Client.167; Parameters: Feature update to Windows 10 (business editions), version 1809, en-us x64

    In WindowsUpdate.log, the most common error I see is

    2019/03/27 13:41:32.5086982 1416  4324  ComApi          ISusInternal:: DisconnectCall failed, hr=8024000C

    So, at this point I'm afraid that this is happening because the "hotfix" version of KB3095113 isn't installed. Or is it? Since I have the most current superseding update of the "Update for Windows Server 2012 R2 (KB3095113) installed? Since the upgrades are successful on the vast majority of machines, I'm second-guessing that and I don't want to have to delete/re-sync all of these updates if that's not the problem. Any help on how to resolve this and/or reconcile the fact that the update is working on the majority of machines in the environment would be greatly appreciated.


    • Edited by Garrett B Tuesday, April 9, 2019 4:36 PM details added to last paragraph
    Tuesday, April 9, 2019 4:25 PM

All replies

  • Hi Garrett,
      

    Thank you for posting here.
    According to my understanding, error 0x8024200 indicates that there is a problem with the download and its file is corrupted or missing. To troubleshoot what you have done, try the following to fix it:
      

    1. In the IIS console, change the MIME type of the '.esd' file to 'application/vnd.ms-cab-compressed'.
    2. Select some Windows 10 clients with abnormalities to test, do the following:
      (1)  Press the start key or start button and immediately type 'cmd'
      (2)  Right click on the cmd application from the search results and select 'Run as administrator'.
      (3)  In the command prompt window, type this line 'C:\WINDOWS\system32>sfc /scannow' and hit Enter. Wait for the scan to complete.
      Windows Resource Protection will find corrupt files and successfully repaired them. You can retry installing your update after this.
        

    Hope the above can help you.
     

    Regards,
    Yic


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, April 10, 2019 5:32 AM
  • Hi thanks for the response. Since the update is working on the vast majority of computers, I'm apprehensive about modifying the MIME type that has been in place during a mostly very successful deployment.
    • Edited by Garrett B Wednesday, April 10, 2019 2:53 PM grammar
    Wednesday, April 10, 2019 2:53 PM
  • Run the client side script here:

    https://www.ajtek.ca/wsus/client-machines-not-reporting-to-wsus-properly/

    Does that fix the problem? I'm in agreement, if the MIME type is set and is working on most systems, the issue is not with the mime type.


    Adam Marshall, MCSE: Security
    https://www.ajtek.ca
    Microsoft MVP - Windows and Devices for IT

    Saturday, April 13, 2019 5:32 AM
  • Hi Garrett,
      

    Are these anti-virus software installed on these problematic clients? Uninstall any anti-virus software except Defender.
      

    And although I'm not sure if this will help you, a clean boot is performed to start Windows using a minimal set of drivers and startup programs:
      

    1. Type msconfig in the searching box and click “System Configuration” from the searching results.
    2. Click Service tab on the System Configuration dialog box.
    3. Select Hide all Microsoft services option on the lower part and click Disable all button.
    4. Click Startup tab and select Open Task Manager link.
    5. Under the Startup tab of Task Manager you can see several items. Select each item and click Disable one by one.
    6. Close Task Manager. Click OK button on System Configuration dialog box. Then Restart computer. 
        

    Complete the above steps, please re-execute the update again.
    Hope the above can help you.
      

    Regards,
    Yic

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, April 19, 2019 6:50 AM
  • Hi,

    I am also having similar issues with upgrading from windows 1909 > 2004. I checked the MIME type and the information is correct already. The error is

    (Unable to Find Resource:) ReportingEvent.Client.181; Parameters: Feature update to Windows 10 (consumer editions), version 2004, en-us x64

    On an individual machine, I went to services.msc > windows installer -> start

    windows modules installer  -> automatic and start

    I was able to install the upgrade successfully. 

    However, i cannot do this for over 200 PC in my domain. Anyone with an idea to fix this?


    • Edited by Engrjainno Wednesday, July 22, 2020 1:37 PM
    Wednesday, July 22, 2020 1:37 PM