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

Anonymous

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

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

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.

0 comments

75 additional answers

Anonymous

2021-02-20T15:42:34+00:00

I got the same error, are you able to resolve it ?

<Version>1.6.0.0</Version>

<ProfileName>UserProfileCreationFailureDuringFinalize</ProfileName>

<ProfileGuid>C6677BA6-2E53-4A88-B528-336D15ED1A64</ProfileGuid>

<FailureData>Error: SetupDiag reports user profile creation failure during Finalize.Last Phase: Finalize Last Operation: Gather data, scope: EVERYTHINGError = 1009.</FailureData>

<FailureDetails>err = 1009, LastOperation = Gather data, scope: EVERYTHING, LastPhase = Finalize</FailureDetails>

<Remediation>Recommend you check for unused user profiles and remove any unnecessary profiles found. Reboot and try the update again.</Remediation>
Was this answer helpful?

0 comments No comments
Anonymous

2021-02-14T09:55:27+00:00

After trying all of the steps to several MS Support articles to fix the error code it still hasn’t installed - the articles suggest stopping several services and deleting the update files, it continues to have failed to install 25+ times. Even the OS update in place attempt has not remedied the issue. It tries every couple days...🤷��‍♂️ I’m out of ideas...

I have the same problem! And it has been bothering me for a long time from the version 1900! And the windows10 updates automatically in the background! Sometimes I clicked the restart button by mistake, ****!
Was this answer helpful?

0 comments No comments
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 No comments
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 No comments