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
    2020-12-19T15:24:46+00:00

    Hello and thank you.

    Could you share any good diagnostic tool or troubleshooting guides to correct the underlying issues represented by the error codes?  Reinstalling many years worth of applications is not something I look forward to if it is not ultimately the final last resort.    Now after upwards of 45 attempts to update to 20H2, throwing the whole machine in the dumpster could feel liberating.   It's been exhausting.

    I will spend the weekend thinking about the custom install and searching for an alternative.

    Best regards,

    Was this answer helpful?

    0 comments
  2. Lester Bernard Reyes 84,985 Reputation points Independent Advisor
    2020-12-19T11:33:25+00:00

    Thanks for replying, seems that the last option is a custom installation however this process will delete all apps but retain all files, if you are okay with this, kindly check the steps here:

    https://answers.microsoft.com/en-us/windows/for...

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-12-18T23:20:55+00:00

    Hello,

    I couldn't get the Window Update for 20H2 to install, so I went the Windows 10 update in place suggestion.   It also failed.  Here's the setupdiaresults.xml file below.  Seems to be related to the boot/reboot process.....

    <?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>2020-12-18 16:49:28, Error                 SP     Operation failed: Update Boot Code. Error: 0x80004005[gle=0x000000b7]</LogErrorLine>

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

      <FailureData>LogEntry: 2020-12-18 16:49:28, 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 = 0x50016, Oper = Finalize</FailureDetails>

      <SetupPhaseInfo>

        <PhaseName>Finalize</PhaseName>

        <PhaseStartTime>12/18/2020 4:49:15 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>12/18/2020 4:49:24 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
  4. Lester Bernard Reyes 84,985 Reputation points Independent Advisor
    2020-12-18T09:06:40+00:00

    Hi thanks for replying, It's okay just ignore if you have error and proceed to next command or method.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-12-17T22:41:17+00:00

    Hello Bernard,   thank you for  the suggestion - I'm having trouble with the "Del"  statement syntax.  

    The results within the Powershell....the first with quotes as in your response, the second without.

    PS C:\WINDOWS\system32> Del "%ALLUSERSPROFILE%\Application Data\Microsoft\Network\Downloader\*.*"

    Del : Cannot find path 'C:\WINDOWS\system32%ALLUSERSPROFILE%\Application Data\Microsoft\Network\Downloader' because

    it does not exist.

    At line:1 char:1

    • Del "%ALLUSERSPROFILE%\Application Data\Microsoft\Network\Downloader\ ...
    •

        + CategoryInfo          : ObjectNotFound: (C:\WINDOWS\syst...work\Downloader:String) [Remove-Item], ItemNotFoundEx

       ception

        + FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.RemoveItemCommand

    PS C:\WINDOWS\system32> del %ALLUSERSPROFILE%\Application Data\Microsoft\Network\Downloader\*.*

    Remove-Item : A positional parameter cannot be found that accepts argument 'Data\Microsoft\Network\Downloader\*.*'.

    At line:1 char:1

    • del %ALLUSERSPROFILE%\Application Data\Microsoft\Network\Downloader\* ...
    •

        + CategoryInfo          : InvalidArgument: (:) [Remove-Item], ParameterBindingException

        + FullyQualifiedErrorId : PositionalParameterNotFound,Microsoft.PowerShell.Commands.RemoveItemCommand

    PS C:\WINDOWS\system32>

    Was this answer helpful?

    0 comments