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

76 answers

Sort by: Newest
  1. 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 No comments
  2. 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 No comments
  3. 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 No comments
  4. 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 No comments
  5. Anonymous
    2021-01-20T22:57:41+00:00

    @rgzz

    Thank you for your reply.  I attempted to execute the suggested steps.   Several files within the software distribution folder were in use and didn't delete.  The "log" from the CMD commands is below....    I rebooted and I'm running the Windows Update Troubleshooting "wizard".

    Microsoft Windows [Version 10.0.18363.1256]

    (c) 2019 Microsoft Corporation. All rights reserved.

    C:\WINDOWS\system32>net stop bits

    The Background Intelligent Transfer Service service is stopping..

    The Background Intelligent Transfer Service service was stopped successfully.

    C:\WINDOWS\system32>net stop wuauserv

    The Windows Update service is stopping.

    The Windows Update service was stopped successfully.

    C:\WINDOWS\system32>net stop appidsvc

    The Application Identity service is not started.

    More help is available by typing NET HELPMSG 3521.

    C:\WINDOWS\system32>net stop cryptsvc

    The Cryptographic Services service is stopping..

    The Cryptographic Services service was stopped successfully.

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

    C:\ProgramData\Application Data\Microsoft\Network\Downloader\.*, Are you sure (Y/N)? y*

    C:\WINDOWS\system32>rmdir %systemroot%\SoftwareDistribution /S /Q

    C:\WINDOWS\SoftwareDistribution\Download - The directory is not empty.

    C:\WINDOWS\SoftwareDistribution\EVENTC~1.V2{CF09071D-2995-4D6A-8569-338B2F3791F0}.bin - The process cannot access the file because it is being used by another process.

    C:\WINDOWS\SoftwareDistribution\ReportingEvents.log - The process cannot access the file because it is being used by another process.

    C:\WINDOWS\system32>rmdir %systemroot%\SoftwareDistribution /S /Q

    C:\WINDOWS\SoftwareDistribution\DATAST~1\DataStore.edb - The process cannot access the file because it is being used by another process.

    C:\WINDOWS\SoftwareDistribution\DATAST~1\DataStore.jfm - The process cannot access the file because it is being used by another process.

    C:\WINDOWS\SoftwareDistribution\DATAST~1\Logs\edb.log - The process cannot access the file because it is being used by another process.

    C:\WINDOWS\SoftwareDistribution\DATAST~1\Logs\edbtmp.log - The process cannot access the file because it is being used by another process.

    C:\WINDOWS\SoftwareDistribution\DATAST~1\Logs\tmp.edb - The process cannot access the file because it is being used by another process.

    C:\WINDOWS\SoftwareDistribution\EVENTC~1.V2{CF09071D-2995-4D6A-8569-338B2F3791F0}.bin - The process cannot access the file because it is being used by another process.

    C:\WINDOWS\SoftwareDistribution\ReportingEvents.log - The process cannot access the file because it is being used by another process.

    C:\WINDOWS\system32>rmdir %systemroot%\system32\catroot2 /S /Q

    C:\WINDOWS\system32\catroot2{127D0~1\catdb - The process cannot access the file because it is being used by another process.

    C:\WINDOWS\system32\catroot2{127D0~1\catdb.jfm - The process cannot access the file because it is being used by another process.

    C:\WINDOWS\system32\catroot2{F750E~1\catdb - The process cannot access the file because it is being used by another process.

    C:\WINDOWS\system32\catroot2{F750E~1\catdb.jfm - The process cannot access the file because it is being used by another process.

    C:\WINDOWS\system32>regsvr32.exe /s atl.dll

    C:\WINDOWS\system32>regsvr32.exe /s urlmon.dll

    C:\WINDOWS\system32>regsvr32.exe /s mshtml.dll

    C:\WINDOWS\system32>netsh winsock reset

    Sucessfully reset the Winsock Catalog.

    You must restart the computer in order to complete the reset.

    C:\WINDOWS\system32>netsh winsock reset proxy

    Sucessfully reset the Winsock Catalog.

    You must restart the computer in order to complete the reset.

    C:\WINDOWS\system32>net start bits

    The Background Intelligent Transfer Service service is starting.

    The Background Intelligent Transfer Service service was started successfully.

    C:\WINDOWS\system32>net start wuauserv

    The requested service has already been started.

    More help is available by typing NET HELPMSG 2182.

    C:\WINDOWS\system32>net start appidsvc

    The Application Identity service is starting.

    The Application Identity service was started successfully.

    C:\WINDOWS\system32>net start cryptsvc

    The requested service has already been started.

    More help is available by typing NET HELPMSG 2182.

    C:\WINDOWS\system32>

    Was this answer helpful?

    0 comments No comments