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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2021-06-24T17:54:15+00:00

    For those with AMD builds, it might be worth updating your motherboard BIOS to the latest version.

    I was having this same issue, and none of the fixes in this thread worked... until I updated my BIOS. Afterward, the "Upgrade in Place" procedure outlined here worked like a charm -- and several subsequent Updates installed without an issue using the normal "Install & Reboot" process.

    So, if you're running an AMD with an older BIOS (mine was from 2016; the new version is from 2019), it might be worth a shot.

    Was this answer helpful?

    0 comments
  2. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  3. Anonymous
    2021-06-06T06:15:09+00:00

    I've also been fighting the failed 20H2 update for months. None of the suggestions worked for me. However, I just came across the following new suggestion and it worked:

    Open a command prompt window as Administrator. Type the following command "bcdedit /set {bootmgr} device partition=C:" and hit enter. Restart your computer and re-try the update to 20H2.

    Did not work for me.

    Anybody have another suggestion?

    Was this answer helpful?

    0 comments
  4. Anonymous
    2021-06-05T15:20:13+00:00

    I've also been fighting the failed 20H2 update for months. None of the suggestions worked for me. However, I just came across the following new suggestion and it worked:

    Open a command prompt window as Administrator. Type the following command "bcdedit /set {bootmgr} device partition=C:" and hit enter. Restart your computer and re-try the update to 20H2.

    Was this answer helpful?

    0 comments
  5. Sumit 44,316 Reputation points Volunteer Moderator
    2021-06-03T13:46:11+00:00

    I have given up as well. After trying to get an update to my 1909 version which I have had a few years, I finally watched a Microsoft video that explained these latest Windows updates are rolling out in phases, and if I don't see one in my security & updates area under settings, it is not time for my laptop to get one. I guess they are rolling it out cautiously so I will be more patient and wait. Apparently, there are issues.

    Let us check the Installation log to find why the update failed. Please share the logs as mentioned in this article. You should use a File sharing service like Onedrive or Media Fire to upload files and share the link in the next reply.

    https://answers.microsoft.com/en-us/windows/forum/all/troubleshoot-feature-update-install-failures/eaf4ff24-64d6-4c72-824c-3ba3df716fc3

    The Panther logs. Files named Setupact.log and Setuperr.log from the following path C:$Windows.~BT\Sources\Panther

    The Rollback logs: These usually are created if Windows Update rolls back. Files named Setupact.log and Setuperr.log from the following path C:$Windows.~BT\Sources\Rollback

    [Only if the error code is 0xC1900101-0x30018] The Device Install Log from C:/$Windows.~bt\Sources\Rollback\setupapi\setupapi.dev.log

    As the log size might be large consider zipping before uploading.

    Was this answer helpful?

    0 comments