A blue screen during a Windows 10 update is usually caused by corrupted system files, conflicting third-party drivers, or insufficient disk space. To fix this, you must boot into Safe Mode to prevent the crash loop, then use built-in repair tools like DISM and SFC to restore integrity before retrying the installation. This approach addresses the root causes of file corruption without requiring complex registry edits.
Booting into Safe Mode
When an update fails with a critical error, Windows often enters a restart loop. You need to interrupt this cycle to access advanced recovery options. If your computer cannot reach the login screen, force it off by holding the power button for ten seconds when the Windows logo appears. Repeat this three times until the system displays
Automatic Repair. From there, navigate to
Advanced Options, select
Troubleshoot, then
Advanced Options, and choose
Startup Settings. Click
Restart and press
4 or
F4 to enter Safe Mode. This loads Windows with minimal drivers, allowing you to run diagnostics without triggering the crash.
Running System File Checker
Corrupted system files are a primary cause of update failures. The System File Checker (SFC) tool scans protected Windows files and replaces incorrect versions with correct Microsoft ones. Open the Start menu, type
cmd, right-click
Command Prompt, and select
Run as administrator. In the elevated window, type the following command and press Enter:
sfc /scannow
Wait for the process to complete. It may take up to fifteen minutes. If the tool reports that it found corrupt files and successfully repaired them, restart your computer normally and attempt the update again. If SFC finds errors it cannot fix, proceed to the next step. Note that while some guides suggest checking specific cache paths, the modern Windows architecture relies on the WinSxS store for component storage, so standard SFC commands are sufficient for most repairs.
Using DISM to Restore Health
The Deployment Image Servicing and Management (DISM) tool fixes the Windows image that SFC uses. If the source image is corrupted, SFC will fail even if individual files are intact. Still in the elevated Command Prompt, run these commands one by one, pressing Enter after each:
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
The
/RestoreHealth command connects to Windows Update servers to download fresh copies of damaged components. This step requires an active internet connection. Once completed, restart your PC. This method resolves deeper image issues that simple file checks miss. For users experiencing persistent update stalls, forcing a restart via the settings menu can sometimes clear stuck processes, as detailed in our guide on
Forcing Windows Update in Windows 10.
Checking Disk Space and Drivers
Insufficient free space is a common but overlooked reason for update failures. Windows 10 typically requires at least 16 GB of free space for major feature updates. Right-click the
Start button, select
System, and check the
Storage section. If space is low, delete temporary files using
Settings >
System >
Storage >
Temporary files. Additionally, outdated or incompatible drivers can cause blue screens during the installation phase. Third-party antivirus software or peripheral drivers often conflict with system changes. Uninstall recent driver updates from
Device Manager and roll back to previous versions if possible. This reduces the risk of conflicts during the write phase of the update.
Resetting Windows Update Components
If the above steps fail, the Windows Update service itself may be corrupted. Resetting the update components clears cached data and resets service states. Stop the Windows Update service by running
net stop wuauserv in Command Prompt. Navigate to
C:\Windows\SoftwareDistribution and delete all contents of this folder. Restart the service with
net start wuauserv. This forces Windows to re-download update metadata. While trace logs can help diagnose issues, they are not always necessary for basic resets. Disabling unnecessary logging can also prevent clutter, as explained in our article on
How to Disable Windows Update Trace Logs in Temp Folder.
Performing an In-Place Upgrade
As a final solution, perform an in-place upgrade using the Media Creation Tool. Download the tool from Microsoft’s official website and run it. Select
Upgrade this PC now. This method reinstalls Windows while keeping your files, apps, and settings intact. It replaces all system files with fresh copies, effectively bypassing any remaining corruption. Ensure you have backed up important data before proceeding. This technique is highly effective for resolving persistent update loops that resist standard troubleshooting.
Frequently Asked Questions
What does Error Code 0x80070005 mean?
This code indicates an access denied error, often caused by permission issues or antivirus interference. Disable third-party security software temporarily and try the update again. Ensure your user account has administrative privileges.
Can I skip the problematic update?
Yes, you can hide specific updates through
Settings >
Update & Security >
View update history. However, skipping critical security patches leaves your system vulnerable. Only hide updates if you plan to troubleshoot the issue further.
Why does my PC restart repeatedly during updates?
Repeated restarts usually indicate a failure in the deployment package or a driver conflict. Booting into Safe Mode allows you to uninstall recent drivers or run repair tools without triggering the loop. Check Event Viewer logs for specific error details.
Is it safe to delete the SoftwareDistribution folder?
Yes, deleting the contents of
C:\Windows\SoftwareDistribution is safe and recommended for resetting updates. Windows will recreate the folder automatically. This action clears corrupted download caches that block new installations.
How do I know if my hard drive is failing?
Use the
chkdsk C: /f command in Command Prompt to check for disk errors. If you hear clicking sounds or see frequent file corruption, your drive may be physically failing. Back up your data immediately if you suspect hardware issues.