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: Newest
Most helpful Newest Oldest
  1. Anonymous
    2021-03-15T18:51:37+00:00

    Thank you Bernard... after wasting a week on several remedies, I highly recommend just going to your "in-place upgrade" recommendation. Windows took care of every problem and made a nice clean-up in the system.

    Regards,

    No Me Lo Plagies

    Was this answer helpful?

    0 comments
  2. Anonymous
    2021-03-08T20:14:50+00:00

    So I've been struggling with problem for a while and much research have resolved it.

    I found this post where the person had noted that they started getting this issue after upgrading their Hard Disk to a SSD, which is exactly what happened to me.

    https://answers.microsoft.com/en-us/windows/forum/windows\_10-update/windows-update-fails-with-0x80004005-error-root/dc3c988e-2756-42f1-86dd-a5ada6fbd6d4

    Hopefully it helps someone!

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2021-03-05T00:48:12+00:00

    Be careful with the step of format, it will delete all the things at the partition!

    I've been battling this for months on an older Dell XPS 14Z that started with W7 then was upgraded to W8 and finally to W10 which update fine until this version. Your method was the next thing I was going to try but I saw an article that said converting the disk to GPT might also fix it. I didn't even realize this older computer was MBR or that it should be converted to GPT. I just completed the GPT conversion today after cloning a backup drive yesterday and after the 2nd attempted update it finally successfully upgraded to 20h. One thing to keep in mind before converting an MBR disk to GPT is that the BIOS must support UEFI. In this case, the BIOS (A06) didn't but I found a mod someone did themselves that did. The option was in the BIOS but it was hidden so it was a matter of enabling all of the optional features.

    What frustrates me about this, and I'm sure many others, is that there appear to be many computers with the same issue. Why does Microsoft have an Update troubleshooter that doesn't correct this specific problem?

    At any rate, here's the article that put me onto the GPT based solution:

    errore 0x80004005 e 0x80242016 alternativamente update da 1903 a 2004 (microsoft.com)

    Good luck people!

    Was this answer helpful?

    0 comments
  4. Anonymous
    2021-03-04T15:05:53+00:00

    Be careful with the step of format, it will delete all the things at the partition!

    Was this answer helpful?

    0 comments
  5. 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?

    1 person found this answer helpful.
    0 comments