Windows 10 Feature Update 20H2 consistently fails with 0x80242016 error

Anonymous
2020-12-17T20:42:31+00:00

Feature Update to Windows 10, version 20H2 has failed to installed 43 times.   The message in the "View Update History" indicates "Last failed install attempted on MM/DD/YYY - 0x80242016".

I've tried numerous posted articles to correct the 0x80242016 error to no avail.    Will I've tried various suggestions to delete the the update and download it, windows update trouble shooter, or stopping/starting various services before attempting to reinstall the update.  I have not be able to use the DISM command, with the local source files because I cannot locate the Windows source files on my PC.  Open to ideas and suggestions.

  • What risk to my machine would there be to perform a Windows 10 Update In Place from 1909 to 20H2 (assuming I can download an install the most current version/build)?
  • Would the update in place reuse my current license/activation.
  • Windows10 Update in place KB Article

Windows Specification:

Windows 10 Pro 1909 OS Build 18363.1256 Installed 4/22/2020

Desktop Machine:

Dell T3610, Xeon CPU E5-1620 0 @ 3.60GHz, 32 GB RAM

1.09 TB free on a 2TB Drive

Thank you - Community

Windows for home | Windows 10 | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

76 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2021-01-31T11:32:04+00:00

    Yo!

    Same problem here, i have tried several methods with the same result, Error 0x80242016 when updating.

    /Janne

    Was this answer helpful?

    0 comments
  2. Anonymous
    2021-02-01T18:31:38+00:00

    I've got the same problem aswell.

    Dell OPTIFLEX 990

    OS version 1909 (build 18363.1139)

    Was this answer helpful?

    0 comments
  3. Anonymous
    2021-02-01T23:49:22+00:00

    A member of the community, Saltgrass, helped me troubleshoot my issue.  I was able to update to 20H2 successfully through his/her suggestions.

    My Boot Data Store was really messed up and pointed to a bogus Windows Recovery Environment (WinRE.WIM).  I needed to get my Windows Recovery Environment working.    I followed the suggested commands to re-configure my Boot Data Store.   In my case the feature updated needed some of the utilities/tools in this special environment to complete the update.

    The lesson for me was that the errors indicated by the update failure or in the update history were not really highlighting the underlying issue on my PC.  Inside the Setupdiaresults.xml file pointed to the root cause of my problem a broken recovery environment that couldn't Update my Boot Code (0x80004005).  The setuperr and setupact log files also help identify the root cause.  After resolving this issue the update took for me.

    This articlemay be helpful.   I was totally over my head, but the right information to the right community member can get you going.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2021-02-02T10:43:37+00:00

    I have a couple posts out there and the suggestion I'm pursuing is an underlying issue I have with the Windows Recovery Environment (WinRE), which is broken.  The update seems to fail because it cannot update the BCD Directory. 

    In the c:\Windows\Logs\SetupDiag folder you will find "setupdiagresults".    I believe this XML file documents the root cause of the update failure for me.   I'm following the suggestion of a community member to fix my Windows Recovery Environment which contains utilities Windows needs to update the system and in my case the Boot Code.

    Additional logs are found in the $WINDOWS.~BT\Sources\Panther folder  specifically the "setupact" and "setuperr" logs.   I still haven't resolved my issue but this is the path I'm following to take corrective action.  Yours may be different.   

    I'm obviously no expert....just a struggling user looking for a working feature update.   

    Good luck and if you resolve let me know.

    Interesting, I did find this string in the XML-file: "Error: SetupDiag reports user profile creation failure during Finalize.Last Phase: Finalize Last Operation: Gather data, scope: EVERYTHINGError = 1009"

    Now I just need to figure out how to resolve THAT error.

    Many thanks though!

    Was this answer helpful?

    0 comments
  5. Anonymous
    2021-02-02T20:06:43+00:00

    I finally resolved my Windows Recovery Environment (WinRE.WIM) Issue.   My Boot Data Store was misconfigured so after a few more suggestions to fix my boot data, I was able to get the recovery environment tools working....the 20H2 update was successful.   

    Yeah - almost - the 20H2 Update broke the driver for my High Definition Audio, so I have limited sound.    Now I get to find a driver and learn how to fix this issue.   OMG - it never ends with the modern tech.   

    The error you found is likely the underlying issue is probably the starting place for resolve your feature update problem.   May the force be with you - or at least have better luck that I.

    Was this answer helpful?

    0 comments