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
Answer recommended by moderator
Anonymous
2021-03-04T15:01:25+00:00

I have the same problem induced by transfering the windows10 from HDD to SDD disk, during the transfer the WinRE partition was lost!

To repair Bootloader, you should prepare a Windows 10 installation disc.

Step 1. Boot from Windows 10 installation disc and press any key to continue.

Step 2. Then navigate to Repair your computer->Troubleshoot->Advanced options->Command Prompt.

Step 3. Type diskpart in the command prompt.

Step 4. Type the following command and press Enter after each command.

List disk
Sel disk 0 (where 0 stands for the boot drive)
List vol (note which volume is the EFI partition, mine is 4)
Sel vol 4
assign letter=N:
Exit
Step 5. Type N: (the drive letter you just assigned and hit Enter.)

Step 6. After you have assigned a drive letter Using Diskpart, you can format the EFI partition using the following command.

format N: /FS:FAT32(type the label of the volume, my is SYSTEM)

Step 7. Now, type bcdboot C:\windows /s N: /f UEFI and hit Enter. This command will repair your Bootloader.(My windows are located in D:\windows)

Then try the bootrec /fixboot command again, fixboot access denied in Windows 10 could be solved.

Was this answer helpful?

2 people found this answer helpful.
0 comments

75 additional answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2021-01-21T01:09:07+00:00

    The suggestion did not resolve the issue.    Below is the updated setupdiagresults.xml file.   I read an article (somewhere) that this error log describes the root cause of the error  contributing to the 0x80242016 feature update install error.

    <?xml version="1.0" encoding="utf-16"?>

    <SetupDiag xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="https://docs.microsoft.com/en-us/windows/deployment/upgrade/setupdiag">

    <Version>1.6.0.0</Version>

    <ProfileName>FindAbruptDownlevelFailure</ProfileName>

    <ProfileGuid>55882B1A-DA3E-408A-9076-23B22A0472BD</ProfileGuid>

    <LogErrorLine>2021-01-20 18:50:39, Error                 SP     Operation failed: Update Boot Code. Error: 0x80004005[gle=0x000000b7]</LogErrorLine>

    <FailureData>Error: SetupDiag reports abrupt down-level failure.Last Operation: FinalizeError:0x80004005 - 0x60016</FailureData>

    <FailureData>LogEntry: 2021-01-20 18:50:39, Error                 SP     Operation failed: Update Boot Code. Error: 0x80004005[gle=0x000000b7]</FailureData>

    <FailureData>Refer to "https://docs.microsoft.com/en-us/windows/desktop/Debug/system-error-codes" for error information.</FailureData>

    <FailureDetails>ErrorCode = 0x80004005, ExCode = 0x60016, Oper = Finalize</FailureDetails>

    <SetupPhaseInfo>

    <PhaseName>Finalize</PhaseName>

    <PhaseStartTime>1/20/2021 6:50:22 PM</PhaseStartTime>

    <PhaseEndTime>1/1/0001 12:00:00 AM</PhaseEndTime>

    <PhaseTimeDelta>0:00:00:00.0000000</PhaseTimeDelta>

    <CompletedSuccessfully>false</CompletedSuccessfully>

    </SetupPhaseInfo>

    <SetupOperationInfo>

    <OperationName>Update Boot Code</OperationName>

    <OperationStartTime>1/20/2021 6:50:36 PM</OperationStartTime>

    <OperationEndTime>1/1/0001 12:00:00 AM</OperationEndTime>

    <OperationTimeDelta>0:00:00:00.0000000</OperationTimeDelta>

    <CompletedSuccessfully>false</CompletedSuccessfully>

    </SetupOperationInfo>

    </SetupDiag>

    Was this answer helpful?

    0 comments
  2. Anonymous
    2021-01-26T08:40:00+00:00

    I have the very same problem.

    System: 64 bit Dell XPS 15 9550 (Swedish language setup/OS)

    OS: Windows 10 Pro Build 1909

    Install date 2019-06-10

    OS version 18363.1198

    I too have tried shutting down services, deleting and downloading updates, update from ISO, and whatnot. No success as of yet.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2021-01-26T15:14:34+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.

    Was this answer helpful?

    0 comments
  4. 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