A Windows Update normally installs automatically and requires only one or more restarts. However, occasionally a computer may fail to complete the update and enter a boot loop.

Typical symptoms include:

• PC repeatedly restarting after Windows Update
• Windows logo appears and the computer restarts
• "Working on updates" appears repeatedly
• "Updates are underway" never completes
• "We couldn't complete the updates. Undoing changes" repeats
• "Preparing Automatic Repair" appears every time
• "Diagnosing your PC" keeps returning
• Blue Screen of Death (BSOD) followed by an automatic restart
• Black screen after installing an update
• Windows reaches the sign-in screen and immediately crashes
• Windows starts only in Safe Mode
• A cumulative or feature update installs and Windows stops booting

A boot loop does not automatically mean Windows must be formatted. Windows includes several recovery mechanisms specifically intended for startup failures, including Startup Repair, Safe Mode, System Restore, update removal, and Windows Recovery Environment (WinRE). Microsoft recommends Startup Repair when Windows doesn't start or keeps loading, and uninstalling an update when a recently installed update caused the problem.

This guide explains the recovery process from the safest methods through advanced repair procedures.

1. What Is a Windows Update Boot Loop?

A boot loop occurs when Windows starts the boot process but cannot successfully reach a stable desktop.

The sequence may look like:

Power On → Windows Logo → Loading → Error → Restart → Windows Logo → Error → Restart

After an update, this can happen because Windows has installed or scheduled changes that cannot be completed successfully during startup.

The failure can involve:

• Windows system files
• device drivers
• boot configuration
• servicing operations
• registry changes
• update packages
• incompatible software
• disk errors
• damaged Windows component store files

The critical first step is determining whether the problem started immediately after Windows Update. If it did, removing or reverting the recent update is usually preferable to immediately resetting or reinstalling Windows.

2. Do Not Immediately Format the Computer

If Windows stops booting after an update, avoid immediately performing a clean installation.

Try recovery methods approximately in this order:

1. Allow the update sufficient time to finish
2. Disconnect unnecessary external devices
3. Enter Windows Recovery Environment
4. Run Startup Repair
5. Uninstall the latest update
6. Try Safe Mode
7. Use System Restore
8. Revert pending update operations
9. Check the Windows disk and system files
10. Repair Windows
11. Reset or reinstall Windows only when necessary

Before destructive recovery procedures, protect important data whenever possible. Microsoft also recommends backing up important files before recovery operations because some recovery choices can result in data loss.

3. First Determine Whether Windows Is Actually Stuck

Updates can sometimes take considerable time, particularly on:

• older computers
• systems using HDDs instead of SSDs
• computers with limited RAM
• large cumulative updates
• major Windows upgrades
• systems with very little free disk space

If the screen shows an update percentage and disk activity continues, avoid repeatedly switching off the computer.

However, if the computer has restarted repeatedly or remains on exactly the same screen for an unusually long period with no progress, recovery may be required.

4. Disconnect Unnecessary External Hardware

Before performing advanced troubleshooting, shut down the computer and disconnect nonessential devices.

Examples include:

• USB flash drives
• external hard disks
• USB printers
• scanners
• webcams
• card readers
• docking stations
• unnecessary USB adapters

Keep only essential devices such as:

• keyboard
• mouse
• monitor
• power connection

Restart the PC.

An incompatible device or driver can sometimes interfere with startup after Windows updates.

5. Enter Windows Recovery Environment (WinRE)

Most boot-loop recovery procedures are performed through the Windows Recovery Environment, commonly called WinRE.

Microsoft states that Windows may automatically enter WinRE after repeated startup failures. It can also be forced into Automatic Repair by interrupting startup twice; Windows should enter recovery on the third startup.

A common procedure is:

1. Turn on the computer.
2. Wait until the Windows or manufacturer logo appears.
3. Hold the power button until the computer switches off.
4. Turn it on again.
5. Interrupt startup again.
6. Turn the computer on a third time.
7. Windows should display Automatic Repair.
8. Select Advanced options.

You should eventually reach:

Choose an option → Troubleshoot → Advanced options

WinRE provides tools including Startup Repair, Startup Settings, Command Prompt, Uninstall Updates, System Restore, System Image Recovery and UEFI Firmware Settings.

Important BitLocker Warning

If BitLocker or Device Encryption is enabled, Windows recovery tools may request the BitLocker Recovery Key. Microsoft specifically notes that certain WinRE procedures require this key.

Do not format an encrypted drive simply because it appears inaccessible from recovery mode.

6. Solution 1: Run Startup Repair

This is one of the safest first recovery attempts.

Go to:

Troubleshoot → Advanced options → Startup Repair

Select the Windows installation if requested.

Allow Windows to diagnose the system.

Microsoft describes Startup Repair as a recovery tool designed to diagnose and repair common problems that prevent Windows from starting, including damaged system files and boot configuration problems.

If Windows starts successfully afterward, allow the system to settle before attempting further updates.

If Startup Repair reports that it couldn't repair the PC, continue with the next solution.

7. Solution 2: Uninstall the Latest Windows Quality Update

If the boot loop began immediately after Windows Update, this should be one of the primary recovery methods.

From WinRE:

Troubleshoot → Advanced options → Uninstall Updates

You may see options relating to the latest quality or feature update depending on the Windows version and recovery environment.

Start by removing the latest quality update when the problem followed a normal cumulative Windows update.

Microsoft specifically supports uninstalling a recent Windows update through Windows Recovery Environment when Windows itself cannot be accessed.

After uninstalling:

1. Restart the computer.
2. Check whether Windows starts normally.
3. If successful, investigate the failed/problematic update before installing it again.

Important

Removing a security update can temporarily expose vulnerabilities. Treat update removal as a troubleshooting measure rather than a permanent strategy.

8. Solution 3: Try Safe Mode

Safe Mode loads Windows with a limited set of drivers and services.

Navigate to:

Troubleshoot → Advanced options → Startup Settings → Restart

Then select:

Enable Safe Mode

or:

Enable Safe Mode with Networking

Microsoft explains that Safe Mode starts Windows in a limited state using only essential files and drivers. If the problem does not occur there, this can help narrow the problem to something outside the basic Windows startup environment.

If Safe Mode works, investigate:

• recently installed drivers
• display drivers
• antivirus/security software
• third-party system utilities
• recently installed applications
• Windows Update history

9. Disable Automatic Restart to See the Actual Error

A boot loop can hide the real problem because Windows restarts immediately following a system failure.

From:

Troubleshoot → Advanced options → Startup Settings → Restart

select:

Disable automatic restart on system failure

Microsoft specifically describes this option as useful when Windows repeatedly fails, restarts, and fails again.

Instead of immediately rebooting, Windows may now display a blue-screen error and stop code.

Examples could include:

• INACCESSIBLE_BOOT_DEVICE
• CRITICAL_PROCESS_DIED
• SYSTEM_SERVICE_EXCEPTION
• PAGE_FAULT_IN_NONPAGED_AREA

Record the exact stop code because it can significantly narrow the troubleshooting process.

10. Solution 4: Use System Restore

If restore points exist, System Restore can return Windows system configuration to a point before the problematic update or system change.

Open:

Troubleshoot → Advanced options → System Restore

Choose a restore point created before the boot-loop problem began.

System Restore can revert system-level changes without normally affecting personal files. Microsoft lists System Restore as one of the primary recovery options when Windows fails to start and Startup Repair doesn't solve the problem.

Applications, drivers and updates installed after the selected restore point may need to be reinstalled.

11. Solution 5: Revert Pending Windows Update Actions Using DISM

This is an important advanced recovery procedure when Windows Update has scheduled servicing operations that cannot complete.

Enter:

Troubleshoot → Advanced options → Command Prompt

First identify the Windows partition.

In WinRE, Windows is not guaranteed to be C:.

Try:

diskpart
list volume
exit

Then check likely partitions:

dir C:\Windows

or:

dir D:\Windows

Continue until you identify the partition containing the actual Windows directory.

Suppose Windows is on C:.

Run:

dism /Image:C:\ /Cleanup-Image /RevertPendingActions

Then restart the computer.

Microsoft documents /RevertPendingActions specifically for system-recovery scenarios where servicing operations may be responsible for a boot failure. Microsoft also documents using this technique from recovery when Windows Update failures leave pending actions.

Important

Do not blindly assume that Windows is on C: while working in WinRE.

Verify the Windows partition first.

12. Solution 6: Check the Windows Drive for File-System Errors

From WinRE Command Prompt, identify the Windows drive and run:

chkdsk C: /f

If you suspect disk-level problems and understand that a deeper scan can take substantially longer, further disk diagnostics may be appropriate.

A damaged file system can prevent an update from completing successfully or prevent Windows from loading afterward.

If CHKDSK reports significant errors repeatedly, investigate the physical SSD/HDD health rather than assuming Windows Update alone caused the problem.

13. Solution 7: Run Offline System File Checker

When Windows cannot boot normally, System File Checker can be run against the offline installation.

First identify the correct Windows drive.

A typical command is:

sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows

However, the boot and Windows partitions can differ depending on the system configuration.

Therefore, this command should be used only after confirming the correct drive letters.

SFC can repair protected Windows system files that became corrupted during an interrupted update or other system failure.

14. Solution 8: Check Boot Configuration

If the update coincided with a damaged boot environment, boot configuration may require repair.

From WinRE Command Prompt, an administrator may use diagnostic commands such as:

bootrec /scanos

and:

bootrec /rebuildbcd

However, modern UEFI/GPT Windows systems differ from older BIOS/MBR computers. Avoid blindly following old tutorials that run every bootrec command or modify EFI partitions.

If Windows reaches its logo before restarting, the bootloader may already be functioning and the failure may instead be occurring later during Windows startup.

15. Solution 9: Remove a Problematic Driver

Sometimes the Windows update itself is not directly defective. Instead, an update exposes a compatibility problem with a device driver.

Common suspects include:

• graphics drivers
• storage controller drivers
• chipset drivers
• network drivers
• third-party antivirus filter drivers
• disk encryption software
• endpoint-security software

If Safe Mode works:

1. Open Device Manager.
2. Locate recently changed hardware.
3. Open its properties.
4. Check the Driver tab.
5. Use Roll Back Driver when available.

Alternatively, uninstall the problematic driver and reinstall a compatible version obtained from the computer or hardware manufacturer's official support channel.

16. Solution 10: Reset Windows Update Components

Use this primarily when you can boot Windows normally or into Safe Mode and Windows Update continues failing.

Open Command Prompt or Terminal as Administrator.

Stop update-related services:

net stop wuauserv
net stop bits
net stop cryptsvc

Rename the Windows Update cache folders:

ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old

Restart the services:

net start cryptsvc
net start bits
net start wuauserv

Restart Windows and check for updates again.

This forces Windows to recreate important update-cache structures rather than repeatedly relying on potentially corrupted cached update data.

17. Solution 11: Repair Windows System Files After Successful Boot

Once Windows starts again, run integrity checks before attempting the problematic update again.

Open Terminal/Command Prompt as Administrator and run:

DISM /Online /Cleanup-Image /RestoreHealth

After DISM finishes:

sfc /scannow

Restart Windows.

Then check:

Settings → Windows Update → Update history

Look for:

• failed updates
• repeatedly attempted KB updates
• driver updates installed immediately before the failure

18. Windows 11: Repair by Reinstalling the Current Version Through Windows Update

On supported Windows 11 systems, Microsoft provides:

Settings → System → Recovery → Fix problems using Windows Update → Reinstall now

Microsoft states that this procedure reinstalls the same Windows version, repairs system files and components, and preserves applications, files and settings.

This makes it particularly useful when Windows is bootable but remains unstable after an update.

Keep the computer connected to power and the internet during the repair.

19. Windows 11 Quick Machine Recovery

Current Windows 11 recovery capabilities may also include Quick Machine Recovery (QMR).

Microsoft describes QMR as a recovery capability intended to help devices recover from certain widespread startup problems by obtaining remediation through Windows Update while operating in Windows Recovery Environment.

This is particularly relevant when a known widespread Windows problem prevents systems from booting.

Availability and behavior can depend on Windows version, configuration and recovery environment.

20. Solution 12: Use Windows Installation Media

If the internal recovery environment is damaged or inaccessible, create Windows installation media using another working PC.

Boot the affected computer from the USB media.

Instead of immediately choosing installation, look for:

Repair my PC

Microsoft documents installation media as another method of accessing Windows Recovery Environment when the computer itself cannot boot normally.

You can then access recovery tools such as:

• Startup Repair
• Command Prompt
• System Restore
• Uninstall Updates

This is preferable to immediately deleting partitions or formatting the drive.

21. Last Resort: Reset or Reinstall Windows

If all recovery procedures fail, Windows may need to be reset or reinstalled.

Microsoft's recovery options include Reset and reinstalling Windows from recovery or installation media when startup repair and other recovery methods fail.

Before proceeding:

• back up user documents
• back up Desktop data
• copy Downloads if required
• back up browser data where necessary
• back up Outlook PST files
• back up accounting/business data
• record software licenses
• verify BitLocker recovery information
• ensure application installers are available

For business PCs, additional data such as Tally, BUSY, SQL databases, accounting applications, custom ERP software and locally stored application databases should be identified before reinstalling Windows.

22. Recommended Troubleshooting Order

For technicians, a practical escalation path is:

Stage 1 — Basic

Disconnect external devices → Restart → Observe exact error.

Stage 2 — WinRE

Startup Repair → Uninstall latest quality update.

Stage 3 — Diagnostic

Safe Mode → Disable automatic restart → Record BSOD/error.

Stage 4 — Recovery

System Restore.

Stage 5 — Advanced

Check Windows drive → CHKDSK → offline SFC → DISM RevertPendingActions.

Stage 6 — Post-Recovery

DISM RestoreHealth → SFC → check drivers → inspect Windows Update history.

Stage 7 — Repair/Reinstallation

Windows repair reinstall → Reset Windows → clean installation only when necessary.

This order minimizes unnecessary destructive changes.

23. How to Prevent Windows Update Boot Loops

No method can completely eliminate update failures, but several precautions reduce their impact.

Keep Sufficient Free Disk Space

Avoid running Windows with the system partition nearly full.

Maintain Current Drivers

Pay particular attention to:

• storage
• chipset
• graphics
• firmware
• BIOS/UEFI

Use drivers appropriate for the specific PC model and Windows version.

Keep Important Data Backed Up

A boot problem is much easier to manage when user and business data is already protected.

Maintain BitLocker Recovery Information

If Device Encryption or BitLocker is enabled, ensure the recovery key can be retrieved before a failure occurs.

Do Not Force Power Off During Normal Update Installation

Interrupting servicing operations can create additional recovery complications.

Create Recovery Media

Business environments should maintain suitable Windows installation/recovery media.

Test Updates in Critical Environments

Organizations managing multiple PCs should consider controlled deployment instead of applying major updates simultaneously to every production machine.

24. Important Note About Windows 10

Microsoft states that normal Windows 10 support ended on October 14, 2025. Windows 10 computers can continue to operate, but standard free security updates and technical support ended at that point, subject to Microsoft's applicable extended-support programs and editions.

Organizations still operating Windows 10 systems should evaluate whether those computers can be upgraded to a supported Windows version or covered by an appropriate extended servicing/security arrangement.

Frequently Asked Questions (FAQ)

1. Why does my PC keep restarting after Windows Update?

The update may have failed during installation, introduced an incompatible driver, damaged system files, or left incomplete servicing operations. Windows then encounters the same failure during every startup and restarts.

2. Can Windows Update actually cause a boot loop?

Yes. A startup failure can occur after an update because of update installation problems, driver compatibility, corrupted files or incomplete servicing operations.

3. Will Startup Repair delete my files?

Startup Repair is intended to diagnose and repair startup-related problems rather than erase personal files. Nevertheless, maintaining backups before recovery work is always recommended.

4. How do I enter recovery mode when Windows keeps restarting?

After repeated failed startups Windows may automatically enter WinRE. Microsoft also documents interrupting startup twice so that the third startup enters Automatic Repair.

5. Which update should I uninstall first?

If the problem started after a routine monthly/cumulative update, normally start with the latest quality update through WinRE → Troubleshoot → Advanced options → Uninstall Updates.

6. Can I uninstall an update when Windows doesn't boot?

Yes. Microsoft provides an Uninstall Updates option inside Windows Recovery Environment specifically for this situation.

7. What does DISM RevertPendingActions do?

It attempts to revert pending Windows servicing operations that may be preventing an offline Windows installation from starting. Microsoft documents it specifically for recovery scenarios involving boot failure.

8. What command can fix an update-related boot loop?

There is no single command that fixes every boot loop. For a confirmed servicing-related startup failure, an advanced recovery command may be:

dism /Image:C:\ /Cleanup-Image /RevertPendingActions

The Windows drive letter must be verified first because it may not be C: inside WinRE.

9. Why does Windows say "Preparing Automatic Repair" repeatedly?

Windows has detected startup failures and is attempting to enter its recovery process. If Automatic Repair itself repeatedly loops, use Advanced options to access Startup Repair, update removal, System Restore, Safe Mode or Command Prompt.

10. Can Safe Mode fix the boot loop?

Safe Mode itself may not repair the underlying issue, but it can allow Windows to start with minimal drivers and services so that a problematic driver, application or configuration can be identified.

11. Will System Restore delete documents?

System Restore is designed to roll back system configuration rather than personal documents. Programs, updates and drivers installed after the selected restore point can be affected.

12. Why does Windows boot into Safe Mode but not normally?

This often indicates that something loaded during normal startup—such as a driver, service, security product or startup component—is contributing to the failure.

13. What if the PC shows a blue screen and restarts too quickly to read it?

Use:

WinRE → Troubleshoot → Advanced options → Startup Settings → Disable automatic restart on system failure

Windows can then remain on the error screen so you can record the stop code.

14. Should I delete the SoftwareDistribution folder?

Usually it is safer to stop the appropriate update services and rename the folder first. Windows can then create a fresh update cache, while the old folder remains temporarily available for troubleshooting.

15. Should I disable Windows Update permanently after fixing the problem?

Generally, no. Security updates protect Windows from known vulnerabilities. Resolve the cause of the failed update rather than permanently disabling updates.

16. Can a driver update cause the restart loop?

Yes. Storage, graphics, chipset and security-related drivers are particularly important during startup. If Safe Mode works after an update, recently changed drivers should be investigated.

17. Can low disk space cause update problems?

Yes. Windows requires working space for downloading, staging and installing updates. Keeping adequate free space on the system drive is important.

18. Can I repair Windows without formatting?

Often, yes. Startup Repair, update removal, System Restore, DISM/SFC recovery and Windows repair/reinstallation options should be considered before clean formatting.

19. Should I run CHKDSK if an update caused the boot loop?

It can be useful when file-system corruption or storage problems are suspected. Repeated disk errors, however, may indicate an SSD/HDD problem requiring hardware diagnostics.

20. When should I reinstall Windows?

Reinstallation should generally be considered after reasonable non-destructive recovery methods have failed, or when Windows is severely corrupted. Back up important information before reset or reinstallation.

Conclusion

A Windows Update boot loop is serious, but it does not automatically require formatting the PC.

When the problem begins immediately after an update, the most useful recovery path is generally:

WinRE → Startup Repair → Uninstall Recent Update → Safe Mode → System Restore → Advanced DISM/SFC/Disk Repair → Windows Repair/Reinstallation

The most important principle is to start with the least destructive recovery option and escalate only when necessary.

For technicians supporting business computers, always verify the Windows partition, BitLocker status and availability of critical user/application data before performing advanced offline commands, resetting Windows or modifying boot partitions.

Official Microsoft recovery guidance:

Windows Recovery Options – Microsoft Support

Windows Recovery Environment – Microsoft Support

Windows Startup Repair – Microsoft Support

Uninstall a Windows Update – Microsoft Support

 

#WindowsUpdate #Windows11 #Windows10 #WindowsBootLoop #BootLoop #WindowsRepair #WindowsRecovery #WinRE #WindowsTroubleshooting #WindowsUpdateError #WindowsUpdateFix #StartupRepair #AutomaticRepair #AutomaticRepairLoop #WindowsRestartLoop #WindowsBootProblem #WindowsStartup #WindowsStartupRepair #UninstallWindowsUpdate #RollbackWindowsUpdate #WindowsSafeMode #SafeMode #SystemRestore #WindowsRestore #DISM #DISMRepair #RevertPendingActions #SFC #SystemFileChecker #CHKDSK #WindowsBootRepair #BCDRepair #Bootrec #WindowsRecoveryEnvironment #WindowsAdvancedStartup #WindowsUpdateTroubleshooting #WindowsUpdateFailed #WindowsUpdateLoop #WindowsUpdateRecovery #WindowsUpdateRollback #WindowsUpdateRepair #WindowsBSOD #BlueScreen #Windows11Repair #Windows10Repair #WindowsTechSupport #ComputerRepair #LaptopRepair #WindowsTips #ITSupport