If Windows fails to update and then won’t boot, the update process likely corrupted critical system files or the boot configuration. This guide explains how to repair the boot process using built-in Windows recovery tools, restore your system to a working state, and prevent the problem from recurring.
Why Windows Updates Can Break Booting
Windows updates modify core system files, drivers, and the boot configuration data (BCD). When an update is interrupted—by a power loss, forced shutdown, or disk error—the system may be left with incomplete or mismatched files. The boot loader then cannot find or load Windows correctly, resulting in errors like “Your PC needs to be repaired” or a black screen with a blinking cursor.
Another common cause is insufficient disk space. Updates need room to download, extract, and install. If the drive fills up mid-installation, the process can fail and leave the system unbootable. Antivirus software can also interfere, mistakenly quarantining update components.
First Steps: Accessing Windows Recovery Environment
Before attempting any repair, you need to get into the Windows Recovery Environment (WinRE). This is a separate environment that can fix startup problems. Here’s how to access it:
- Turn on your PC. When Windows fails to boot, it will usually automatically enter WinRE after a few attempts.
- If it doesn’t, force a shutdown by holding the power button until the PC turns off. Turn it on again, and repeat this three times. On the third restart, Windows should display the recovery screen.
- On the recovery screen, select Troubleshoot > Advanced options.
If you have a Windows installation USB drive, you can boot from it and select “Repair your computer” on the first screen to reach the same options.
Using Startup Repair
Startup Repair is the first tool to try because it automates many common fixes. It scans for problems like missing boot files or corrupted registry entries and attempts to repair them.
- In the Advanced options menu, select Startup Repair.
- Choose your operating system (usually Windows 10 or 11) and wait for the process to complete.
- If it finds issues, it will attempt to fix them and restart your PC.
If Startup Repair says it couldn’t repair your PC, don’t panic. It doesn’t cover every scenario. Move on to the command-line methods below.
Repairing Boot Files with Bootrec and BCDEdit
When Startup Repair fails, the boot configuration data (BCD) or the Master Boot Record (MBR) may be corrupted. You can rebuild these using the Command Prompt from WinRE.
- In Advanced options, select Command Prompt.
- Type the following commands one by one, pressing Enter after each:
bootrec /fixmbr bootrec /fixboot bootrec /scanos bootrec /rebuildbcd
If you get an “Access is denied” error when running bootrec /fixboot, your system uses UEFI with a GPT disk. In that case, you need to rebuild the BCD manually:
- At the command prompt, type
diskpartand press Enter. - Type
list volumeto see your partitions. Note the drive letter of the EFI partition (usually labeled “System” and formatted as FAT32). - Type
exitto leave DiskPart. - Now type the following, replacing
C:with the actual drive letter of your EFI partition:
bcdedit /export C:\BCD_Backup ren C:\BCD BCD.old bootrec /rebuildbcd
When prompted, type Y to add the Windows installation to the boot list. This should recreate the BCD store.
Using System Restore and DISM
If the boot files are fine but Windows still won’t start, the update may have corrupted system files. Two tools can help:
System Restore rolls your system files and settings back to a point before the failed update. To use it:
- In Advanced options, select System Restore.
- Choose a restore point that predates the update (if one exists).
- Follow the prompts and wait for the restoration to complete.
DISM (Deployment Image Servicing and Management) repairs the Windows image itself. It’s more thorough than System Restore. From the Command Prompt, run:
dism /Online /Cleanup-Image /RestoreHealth
This scans for corruption and fixes it using Windows Update or a local source. If you have a Windows installation USB, you can use it as a source:
dism /Online /Cleanup-Image /RestoreHealth /Source:D:\sources\install.wim
Replace D: with the drive letter of your USB drive. After DISM completes, run sfc /scannow to verify system file integrity.
What to Do If Nothing Works
If all repair attempts fail, you have two remaining options:
- Reset This PC (from WinRE) reinstalls Windows while keeping your personal files. Choose Troubleshoot > Reset this PC > Keep my files. This will remove installed apps but preserve your documents and photos.
- Clean install from a USB drive. This erases everything and gives you a fresh system. It’s the most reliable but requires a backup of your data beforehand.
Before resetting or reinstalling, try to back up critical files. You can do this by booting from a Linux live USB and copying files to an external drive, or by using the Command Prompt to copy files to a USB stick.
Preventing Future Boot Failures
To reduce the risk of this happening again:
- Always keep at least 15-20 GB of free space on your system drive.
- Use a UPS (uninterruptible power supply) to prevent power loss during updates.
- Create a restore point manually before installing major updates.
- If an update fails, don’t force shutdown repeatedly. Use the Windows Update troubleshooter or wait for the system to roll back automatically.
- Keep your system drive healthy by running
chkdsk /foccasionally from an elevated command prompt.
Frequently Asked Questions
Can I recover my files if Windows won’t boot?
Yes. You can boot from a Windows installation USB, open Command Prompt, and copy files to an external drive using commands like copy C:\Users\YourName\Documents\* D:\Backup\. Alternatively, use a Linux live USB to access the drive and copy files graphically.
How long does Startup Repair take?
It usually takes 5-15 minutes, but it can take longer if the drive is large or heavily fragmented. If it exceeds 30 minutes, it may be stuck; you can restart the process or try a different repair method.
What does “bootrec /fixboot” do?
It writes a new boot sector to the system partition. This is useful when the boot sector is corrupted, but it won’t fix missing boot files—that’s what bootrec /rebuildbcd is for.
Will System Restore remove my personal files?
No. System Restore only reverts system files, registry settings, and installed programs. Your personal documents, photos, and other user files remain untouched. However, it may uninstall recently installed apps.
Is it safe to use DISM on a live system?
Yes, DISM is a built-in Windows tool designed for this purpose. Running it from the Command Prompt in WinRE is safe, but it requires an internet connection or a local source to download replacement files. It can take 20-30 minutes to complete.
What if I don’t have a restore point?
If System Protection was disabled, you won’t have restore points. In that case, use DISM and SFC to repair system files, or consider a reset. To avoid this in the future, enable System Protection for your system drive.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- Photonic Inference vs GPU Inference: Key Differences16,384.00 µs
- Android Low Storage Survival Tips That Actually Work
- How to Password Protect PDFs on iPhone
- iPhone Force Restart Not Working? Fixes
- Add or Remove Keyboard Layout in Windows 10
- Razer Barracuda V2 Pro Dongle: Store & Find