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: Most helpful
  1. 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
  2. Anonymous
    2021-01-19T19:19:13+00:00

    Open Powershell with Admin or CMD with Admin (Press Windows key + X then click Windows Powershell(Admin))

    Copy each line of command to Powershell then press enter (one line at a time)

    net stop bits

    net stop wuauserv

    net stop appidsvc

    net stop cryptsvc

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

    rmdir %systemroot%\SoftwareDistribution /S /Q

    rmdir %systemroot%\system32\catroot2 /S /Q

    regsvr32.exe /s atl.dll

    regsvr32.exe /s urlmon.dll

    regsvr32.exe /s mshtml.dll

    netsh winsock reset

    netsh winsock reset proxy

    net start bits

    net start wuauserv

    net start appidsvc

    net start cryptsvc

    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...

    Regarding the instructions above: If you are running PowerShell (which can be detected by the PS letters at the beginning of the command line) the %...% syntax will not work. The easiest way around is to start cmd in that console window by typing cmd[Enter]. Only then you'll be able to run the commands above. There are equivalents for PS, but I don't know them from the top of my head. The same goes for rmdir which is not the same rmdir as in PowerShell, so the /S /Q flags will also work only in cmd. The MS person should've noted that. I hope it helps!

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2021-01-16T17:58:40+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...

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2021-01-16T16:57:04+00:00

    I've just been hit by the same problem. It's not the first time that this has happened with Windows updates, although the first time with Windows 10.

    I think I'll wait till the next update and hope that it's fixed.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2021-01-06T03:15:57+00:00

    I am having the same problem.  Seems systemic.  What are the options of waiting for a new update/fix from MS.  Seems like they have a bad update and they should fix it before all the customers either trash their computers or spend all their time Restoring their computers.....

    Was this answer helpful?

    0 comments No comments