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: Newest
Most helpful Newest Oldest
  1. Anonymous
    2021-05-13T02:53:38+00:00

    I feel the same way. I do not want a complicated method to resolve this continual failure to update to version 20H2. I am also not willing to uninstall various programs, etc. in order to have this Windows version. I will just keep the previous one. But I do dislike being reminded often that I am not up to date when I have tried so many times.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2021-05-06T07:46:08+00:00

    Dear PepsiCherry6940,

    thank you for sharing your experience with this update. Unfortunately so far I have found no other solution than suspending updates on my computer. I wish good luck to you for getting a better way.

    Georg

    Was this answer helpful?

    0 comments
  3. Anonymous
    2021-05-05T23:45:25+00:00

    I'm also having this problem to this day, probably failed over 30 times, tried media creation tool, and the other one which i forgot the name of, nothing works, 1909 is busted.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2021-04-20T12:18:27+00:00

    it clearly seems that you had a different problem compared to us ,otherwise it wouldnt have been fixed that easily ,glad it worked out eitherway

    Was this answer helpful?

    0 comments