SoftwareDistribution folder and reset the Windows Update components via Command Prompt, which forces the system to redownload fresh update files rather than retrying the failed partial install.
Understanding the 73% Stuck Point
The percentage indicator in Windows Update represents the progress of downloading and extracting update packages relative to the total size of the payload. When it freezes at 73%, the system has likely downloaded approximately three-quarters of the required data but fails during the verification or installation phase. This specific hang point often correlates with issues in the BITS (Background Intelligent Transfer Service) queue or corruption within the C:\Windows\SoftwareDistribution directory where temporary update files are stored.
While minor glitches can sometimes resolve themselves after a long wait, persistent hangs require manual intervention. If you have been waiting for several hours, proceeding with troubleshooting steps is necessary to prevent further disk I/O bottlenecks. Note that if your system is experiencing broader instability, such as input delays or freeze-ups, refer to our guide on Solving Temporary Freeze-ups and Input Delays on 64-bit Windows 10 Systems to ensure underlying hardware drivers are not causing the bottleneck.
Step 1: Restart Essential Services
The first line of defense involves stopping the services responsible for handling updates and then restarting them to clear any locked processes. This action releases files that may be held open by a hung process, allowing the update mechanism to proceed cleanly.
- Press Win + R, type
services.msc, and press Enter. - Locate Windows Update in the list, right-click it, and select Stop.
- Similarly, find BITS (Background Intelligent Transfer Service), right-click, and select Stop.
- Wait ten seconds to ensure both services are fully terminated.
- Right-click each service again and select Start to restart them.
After restarting these services, check your Windows Update settings to see if the progress bar moves past the 73% mark. If the issue persists, the problem likely lies deeper within the file cache itself.
Step 2: Clear the SoftwareDistribution Folder
If restarting services does not work, you must manually delete the corrupted temporary files. The SoftwareDistribution folder contains the downloaded update packages; if these files are corrupted or partially written, Windows will repeatedly fail at the same percentage.
Before deleting anything, ensure the Windows Update and BITS services are stopped using the steps above. Then, navigate to C:\Windows\SoftwareDistribution. You should see folders named Download and DataStore. Delete all contents inside the Download folder. Do not delete the Download folder itself, only its contents. Similarly, clear the contents of the DataStore folder if possible, though the Download folder is the primary culprit.
net stop wuauserv
net stop bits
rd /s /q C:\Windows\SoftwareDistribution\Download
net start wuauserv
net start bitsRunning these commands via an Administrator Command Prompt is faster and ensures no files are in use. Once cleared, return to Settings > Update & Security > Windows Update and click Check for Updates. The system will now redownload the necessary files from scratch.
Step 3: Run System File Checker and DISM
Corruption in core Windows system files can also cause update failures. The Deployment Image Servicing and Management (DISM) tool and the System File Checker (SFC) can repair these foundational components.
Open Command Prompt as Administrator and run the following command to repair the component store:
DISM /Online /Cleanup-Image /RestoreHealthThis process may take some time depending on your internet speed and disk performance. Once completed, run the SFC scan:
sfc /scannowIf these tools report that they fixed corrupt files, restart your computer and attempt the update again. This step addresses deeper OS-level inconsistencies that simple cache clearing cannot fix.
Step 4: Reset Windows Update Components
If the previous steps fail, a full reset of the update infrastructure is required. This involves renaming specific folders and resetting registry keys related to update configuration.
Create a batch file with the following commands and run it as Administrator:
net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old
net start wuauserv
net start cryptSvc
net start bits
net start msiserverThis sequence stops critical services, renames the problematic folders to force Windows to recreate them with default settings, and then restarts the services. This is a comprehensive solution for stubborn update hangs.
Preventive Measures and Related Issues
To avoid future occurrences, ensure that your third-party antivirus software is not blocking Windows Update processes. Some security suites incorrectly flag update downloads as threats. Additionally, keep your storage drives defragmented (if HDD) and free up sufficient space, as low disk space can interrupt the extraction phase of updates.
If you encounter network-related errors during the update process, such as connectivity timeouts, it might be unrelated to the update engine itself. For instance, if your VPN connections won't work on Windows 10 while trying to update, this could indicate a broader network stack issue. Refer to our article on Troubleshooting VPN Connections Stopped Working on Windows 10 Pro to diagnose potential network adapter conflicts.
Frequently Asked Questions
Why does Windows Update get stuck at exactly 73%?
This specific percentage often corresponds to the completion of downloading large cumulative update packages followed by a failure in the verification stage. It indicates that the download was successful, but the subsequent installation or integrity check encountered corrupted data or a service conflict.
Is it safe to delete the SoftwareDistribution folder?
Yes, it is completely safe to delete the contents of the SoftwareDistribution folder. These files are temporary caches used for downloading updates. Deleting them forces Windows to re-download fresh copies, which resolves issues caused by partial or corrupted downloads.
What if the update fails after clearing the cache?
If clearing the cache does not work, the issue may lie with corrupted system files or driver conflicts. Running the DISM and SFC scans is the next logical step to repair underlying OS components that support the update installation process.
Can third-party antivirus software cause this issue?
Absolutely. Some antivirus programs monitor file changes aggressively and may lock files needed by Windows Update, causing the process to hang. Temporarily disabling real-time protection or adding an exclusion for the SoftwareDistribution folder can help identify if this is the cause.
How long should I wait before troubleshooting?
Windows Update can legitimately take a long time, especially on older hardware or slow connections. However, if the percentage has not changed for more than two to three hours, it is highly likely stuck due to an error. Waiting longer than this rarely resolves the issue and may lead to further system instability.