Hi Seth,
We recommend that you reset Windows Update components on Windows 10 manually using command prompt. Here are the steps:
- Use the Windows key + X to open the Power User menu and select
Command Prompt (Admin).
- Stop the BITS (Background Intelligent Transfer Service), Windows Update service, and Cryptographic service. Type the following commands and make sure to press
Enter on each line:
net stop bits
net stop wuauserv
net stop appidsvc
net stop cryptsvc
- Delete all the qmgr*.dat files created by BITS from your PC. Type the following command and press
Enter:
Del "%ALLUSERSPROFILE%\Application Data\Microsoft\Network\Downloader\qmgr*.dat"
- Clear the Windows Update cache to allow Windows 10 re-download the updates, instead of using the files already downloaded on your system that might be damaged. Type the following commands and make sure to press
Enter on each line:
rmdir %systemroot%\SoftwareDistribution /S /Q
rmdir %systemroot%\system32\catroot2 /S /Q
Quick Tip:****We’re using the remove directory rmdir command with the /S switch to delete the specified directory and all subdirectories within the main folder, and the /Q switch is used to delete directories quietly without confirmation. If you get the message “The process cannot access the file because it is being used by another process.”, then repeatstep 1* and try again, as one of the services might have restarted unexpectedly.*
- Reset the network configurations that might be part of the problem (but do not restart your computer just yet). Type the following commands and make sure to press
Enter on each line:
netsh winsock reset
netsh winsock reset proxy
- Restart the BITS, Windows Update, and Cryptographic services using the following commands and make sure to press
Enter on each line:
net start bits
net start wuauserv
net start appidsvc
net start cryptsvc
Restart your Windows 10 PC.
You can also check Fix Windows Update issues for a guided walk through on how to troubleshoot Windows Update concerns.
For further assistance, feel free to post back on our Microsoft Community.