Update Installs, Then Rolls Itself Back — Breaking the Loop

25 Aug 2026

Windows Update downloads successfully, reaches 100%, restarts the computer and appears to begin installing normally.

Then something goes wrong.

You may see messages such as:

Undoing changes made to your computer
We couldn’t complete the updates
Restoring your previous version of Windows
Installation failed
Something didn’t go as planned
Your PC will restart several times

Windows eventually returns to the desktop, but the update is still listed as failed. A day or two later, it downloads again and repeats the same process.

This is an update rollback loop.

The rollback itself is a safety mechanism. Windows has detected that the updated installation cannot start or complete reliably, so it restores the previous working state rather than leaving the computer unusable. The repeated attempts happen because the underlying problem remains and Windows Update continues offering the same applicable update.

Common causes include:

An incompatible or damaged driver
Corrupted Windows servicing components
Insufficient temporary storage
Security or backup software interfering with installation
A connected USB device or docking station
An outdated BIOS or firmware package
A damaged user or system file
A failing SSD
An update-specific known issue
An unsuitable Windows configuration
A problem migrating applications or settings during a feature update

The solution is not to keep pressing Retry.

You need to identify the failed update, record its error code and work through the likely causes in a controlled order.

First: Is It a Quality Update or a Feature Update?

The repair approach depends partly on what Windows is trying to install.

Quality or cumulative update

These are the regular Windows security and reliability packages. They normally retain the same broad Windows version while increasing the complete OS build number.

A failed quality update may be identified by a Knowledge Base number such as:

KB50XXXXX

Feature update

A feature update moves Windows to another release, such as:

Windows 11 24H2 → Windows 11 25H2

Feature updates perform a much larger migration involving:

Windows system files
Installed applications
Drivers
User profiles
Settings
Recovery components
Boot files

When a feature update fails, Windows Setup normally rolls the computer back to the previous version. Microsoft provides SetupDiag and detailed Windows Setup logs specifically for investigating these unsuccessful upgrades.

Find the Exact Failed Update

Open:

Settings > Windows Update > Update history

Look under:

Quality Updates
Feature Updates
Driver Updates
Definition Updates
Other Updates

Find the entry marked Failed to install.

Record:

The update’s KB number
The installation date
The error code
The Windows version currently installed
How far installation progressed
Whether the rollback happened before or after a restart

Microsoft recommends checking Update history and noting the failed update and error code before proceeding with upgrade or installation troubleshooting.

Check the Current Windows Version

Press:

Windows key + R

Enter:

winver

Record the version and complete OS build.

This confirms whether the update genuinely rolled back or partially installed.

A support record might look like:

Current version: Windows 11 25H2

Current OS build: 26200.xxxxx

Failed update: KB50xxxxx

Error: 0x800f0922

Rollback begins: Approximately 92% after restart

That is much more useful than saying, “Windows Update keeps failing.”

Check Microsoft’s Known-Issues Information

Before modifying the computer, check whether Microsoft has acknowledged a problem with the specific update.

Microsoft publishes update-history and Windows release-health information covering:

Known issues
Resolved issues
Workarounds
Known Issue Rollback
Out-of-band updates
Installation problems
Compatibility holds

Recent Windows updates have occasionally had documented installation failures or restart-related issues that required a later fix or a specific workaround.

When Microsoft has already confirmed that the update is faulty on a particular configuration, repeatedly resetting Windows Update is unlikely to help.

Follow the official workaround or wait for the corrected update rather than applying unrelated Registry fixes from a forum.

Protect the Computer Before Troubleshooting

Before making substantial changes:

Back up important files.
Confirm that the backup opens.
Check whether OneDrive or another backup service is genuinely synchronised.
Save the BitLocker recovery key.
Record the current Windows version and build.
Record installed security and backup applications.
Create a list of recent driver, firmware or software changes.
Check whether the PC is managed by an employer or IT provider.

Microsoft recommends backing up important data before using Windows recovery options. BitLocker-protected computers may request their 48-digit recovery key following certain hardware, startup or security changes, and Microsoft cannot recreate a lost key.

Do not clear the TPM, disable Secure Boot or change storage-controller settings to fix an ordinary update failure.

Step One: Restart Properly

Begin with one deliberate restart:

Start > Power > Restart

Do not select Shut down and power the computer back on.

Restarting allows Windows to:

Complete pending servicing
Release locked update files
Reinitialise drivers
Complete an earlier restart requirement
Clear temporary installation state

After the restart:

Wait several minutes for Windows activity to settle.
Open Windows Update.
Check whether another smaller servicing or security update is offered.
Install the available updates.
Restart again when requested.
Retry the failed update once.

Microsoft includes restarting the PC among its first recommended actions for several common Windows Update errors.

If it rolls back again, stop retrying and continue diagnosing.

Step Two: Run the Windows Update Troubleshooter

Open:

Settings > System > Troubleshoot > Other troubleshooters

Find Windows Update and select Run.

On current Windows 11 configurations, the troubleshooting process may open through the Get Help application.

Restart the computer after it finishes, then check for updates again. Microsoft recommends this as an early step for update download and installation errors.

The troubleshooter may correct problems involving:

Update-service configuration
Pending restart state
Update database settings
Permissions
Damaged temporary update information
Common Windows Update configuration faults

Record anything it reports rather than simply selecting Close.

Step Three: Check Free Storage Space

Windows requires space not only for the downloaded update but also for:

Extracting installation files
Creating temporary working data
Migrating features and language packs
Preserving rollback information
Retaining the previous Windows installation temporarily

Microsoft notes that feature updates can require substantially more temporary space than their download size, and the amount varies according to the device’s update path and installed optional content.

Open:

Settings > System > Storage

Review:

Free capacity on the Windows drive
Temporary files
Cleanup recommendations
Installed applications
Downloads
Recycle Bin
Previous Windows installation files

Use Cleanup recommendations or Storage Sense rather than manually deleting files from Windows system folders.

Do Not Delete Windows.old Too Early

The Windows.old folder can contain the files needed to return to the previous Windows version.

Deleting it can remove the normal rollback option.

When an update is repeatedly failing, preserve the rollback files until you have:

Confirmed the current Windows installation is stable
Backed up important data
Decided that returning to the previous version is unnecessary

Step Four: Disconnect Non-Essential Hardware

Turn the computer off and disconnect hardware that is not required for the update.

Remove:

USB flash drives
External hard drives
Memory-card readers
Printers
Scanners
Webcams
Game controllers
Audio interfaces
USB hubs
Docking stations
Additional displays where practical
Bluetooth receivers
Unnecessary expansion devices

Keep connected only:

Power
One display
Keyboard
Mouse
Network connection where required

Microsoft lists removing non-essential external hardware among its recommended actions for Windows upgrade and installation failures.

A connected device can cause a rollback when:

Its driver cannot migrate
Windows cannot initialise it during the new boot phase
Its storage is mistaken for an installation or boot device
Its firmware is incompatible
The device disconnects during setup

Reconnect devices only after the update has completed and Windows has started normally.

Step Five: Check Device Manager

Right-click Start and select:

Device Manager

Look for:

Yellow warning symbols
Unknown devices
Disabled devices
Duplicate devices
Old storage or network adapters
Hardware that is no longer connected

Pay particular attention to:

Storage controllers
Graphics adapters
Network adapters
Bluetooth
USB and Thunderbolt controllers
Sound devices
System devices

Install supported drivers through:

Windows Update
The computer manufacturer
The component manufacturer where appropriate

Avoid generic third-party driver-update programs.

The Importance of Error 0xC1900101

For feature upgrades, an error beginning with:

0xC1900101

usually indicates that a rollback occurred and is most commonly associated with driver compatibility. The digits after the hyphen identify the phase and operation during which setup failed.

For example:

0xC1900101 - 0x40017

suggests that the failure occurred during a later Windows Setup boot phase.

Do not replace every driver blindly. Use SetupDiag and the installation logs to narrow down the responsible component.

Step Six: Update BIOS, Firmware and Manufacturer Drivers

Check the official support service for the exact laptop, desktop or motherboard model.

Look for current versions of:

BIOS or UEFI
Chipset drivers
Storage-controller drivers
Intel RST or VMD drivers
Graphics drivers
USB-C or Thunderbolt firmware
Docking-station firmware
Network drivers
Embedded-controller firmware
SSD firmware

A feature update may expose a compatibility problem that did not affect the previous Windows build.

Before updating firmware:

Connect a reliable charger.
Save the BitLocker recovery key.
Confirm the update is for the exact model.
Close applications.
Do not interrupt the process.

Do not update firmware while the computer has unstable power, is overheating or is already stuck in a restart loop.

Step Seven: Review Third-Party Antivirus, Encryption and Backup Software

Third-party software operating deeply inside Windows can interfere with updates.

Examples include:

Non-Microsoft antivirus
Endpoint-security agents
Disk-encryption tools
Backup snapshot drivers
VPN clients
Disk-cloning software
Drive-filter utilities
Old firewall products
System optimisation software

Microsoft’s official upgrade guidance recommends uninstalling non-Microsoft antivirus software when investigating persistent installation errors, then reinstalling a current compatible version after the upgrade.

Do not simply switch an antivirus interface to “off”. Its drivers and services may still load.

On a business-managed computer, do not uninstall:

Endpoint protection
Remote monitoring
Backup agents
Microsoft Intune components
VPN software
Encryption products

without authorisation from the organisation’s IT provider.

The correct approach is to confirm whether the installed version supports the target Windows build and whether an updated package is available.

Step Eight: Repair Windows Components

Corrupted Windows components can prevent an update from installing successfully.

Open Terminal or Command Prompt as administrator.

First run:

DISM.exe /Online /Cleanup-Image /RestoreHealth

Allow it to complete.

Then run:

sfc /scannow

Microsoft recommends running DISM before System File Checker. DISM repairs the Windows component source, while SFC checks protected system files and replaces damaged copies where possible.

Restart Windows after both commands finish.

Possible DISM Results

The restore operation completed successfully

Proceed to SFC, restart and retry the update once.

Source files could not be found

DISM may be unable to retrieve a healthy repair source through Windows Update. An experienced technician may need to provide a matching Windows installation source.

DISM reports corruption it cannot repair

Do not continue repeatedly retrying the update. Consider the Windows repair-reinstallation option later in this guide.

Possible SFC Results

Windows Resource Protection did not find integrity violations

Protected system-file corruption was not identified.

Windows Resource Protection found corrupt files and repaired them

Restart and test the update.

Windows Resource Protection found corrupt files but could not fix some of them

Further component repair or a repair installation may be required.

Step Nine: Perform a Clean Boot

A clean boot starts Windows with essential drivers and a controlled set of startup software.

This helps identify whether a third-party service is blocking installation.

Press:

Windows key + R

Enter:

msconfig

Then:

Open the Services tab.
Select Hide all Microsoft services.
Select Disable all.
Select Apply.
Open the Startup tab.
Select Open Task Manager.
Disable enabled startup items.
Close Task Manager.
Select OK.
Restart Windows.
Retry the update.

Always select Hide all Microsoft services before disabling services.

Microsoft describes clean boot as a troubleshooting state that helps isolate background software conflicts and specifically recommends retrying a failed update while in that state.

The Update Installs Successfully

One of the disabled third-party services or startup applications was probably involved.

Restore the items gradually and identify which software needs:

Updating
Reconfiguration
Removal
Replacement

The Update Still Rolls Back

Restore normal startup and continue with the deeper diagnostic steps.

Do not leave an employee’s PC permanently operating in clean-boot mode.

Step Ten: Reset the Windows Update Cache

Use this only after the basic troubleshooting has failed.

A damaged update download or Windows Update database can cause the same package to fail repeatedly. Microsoft includes clearing the Windows Update cache and resetting update components among its recommended actions for certain installation errors.

Open Command Prompt as administrator and run:

net stop bits

net stop wuauserv

net stop cryptsvc

Rename the update folders:

ren %systemroot%\SoftwareDistribution SoftwareDistribution.old

ren %systemroot%\System32\catroot2 catroot2.old

Restart the services:

net start cryptsvc

net start wuauserv

net start bits

Restart Windows and check for updates.

What This Does

Renaming the folders causes Windows to create fresh update-cache and catalogue folders.

It does not uninstall the Windows updates already installed.

However, it may clear the locally displayed update-download history and require Windows Update to rebuild its information.

Do not delete the folders immediately. Retaining the .old versions temporarily provides a fallback while testing.

On managed business computers using WSUS, Configuration Manager or specialist patching tools, have the IT provider investigate the deployment before resetting components locally.

Step Eleven: Use SetupDiag for Feature-Update Rollbacks

If a feature update installs, restarts and then returns to the previous Windows version, run Microsoft’s SetupDiag.

SetupDiag examines Windows Setup logs and attempts to identify why the upgrade failed. It is included with Windows Setup on supported Windows versions, and Microsoft recommends using the latest SetupDiag version when running it manually.

Run it as administrator after the rollback.

Review the generated results file, commonly:

SetupDiagResults.log

Depending on the failure, it may identify:

A driver
An application
A migration plug-in
A service
A corrupted file
A disk-layout issue
The setup phase that failed
The operation being performed
The result and extended error codes

Do not publish the complete report publicly without reviewing it. It can contain:

Computer names
User-profile paths
Application information
Driver names
Organisational details

Check the Windows Setup Logs

For feature-upgrade failures, important logs may exist under:

C:\$Windows.~BT\Sources\Panther

and:

C:\$Windows.~BT\Sources\Rollback

Useful files can include:

setupact.log

setuperr.log

setupapi.dev.log

setupmem.dmp

The Rollback folder records activity associated with the failed installation and restoration of the previous Windows state. Microsoft documents these logs and recommends identifying the result code, extended code, failed phase and relevant error entries when analysing an upgrade failure.

Understand Result and Extended Codes

An upgrade error may look like:

0xC1900101 - 0x4000D

The first part is the result code.

The second part helps identify the setup phase and operation.

This can distinguish failures involving:

Down-level preparation
SafeOS
First boot
Second boot
Data migration
Driver installation
Finalisation
Out-of-box setup

Setup logs are complex and frequently contain warnings unrelated to the final failure. Look for the last meaningful failure before rollback rather than assuming every line marked Error is the cause.

Step Twelve: Try “Fix Problems Using Windows Update”

Windows 11 includes a repair option that reinstalls the current Windows version while preserving:

Applications
Personal files
Settings

Open:

Settings > System > Recovery

Under Fix problems using Windows Update, select:

Reinstall now

Microsoft designed this option particularly for problems involving damaged system files and Windows Update components. It downloads and installs a repair copy of the current Windows version.

Before starting:

Back up important files.
Connect reliable mains power.
Ensure sufficient free space.
Save the BitLocker recovery key.
Close applications.
Allow adequate time for the download and installation.

The option may be unavailable when:

The PC is managed by an organisation
The required Windows version or servicing configuration is not present
A recovery policy disables it
Windows Update itself cannot obtain the repair package

This repair reinstall is generally preferable to resetting the PC when you want to preserve installed applications.

If Windows Cannot Reach the Desktop

Sometimes the update fails so badly that Windows repeatedly displays:

Automatic Repair
Undoing changes
Restoring your previous version
A BitLocker recovery prompt
A restart loop

Enter the Windows Recovery Environment, or WinRE.

You may reach it automatically after repeated failed starts. You can also use official Windows installation media and select:

Repair your computer

Windows RE contains built-in recovery tools for diagnosing startup and update failures. Encrypted devices may require the BitLocker recovery key before certain tools can access Windows.

Uninstall the Latest Update

Select:

Troubleshoot > Advanced options > Uninstall Updates

You may be offered:

Uninstall latest quality update
Uninstall latest feature update

Microsoft provides this route specifically for computers that cannot access normal Windows after an update.

Choose the update type that matches the failure.

Startup Repair

Select:

Troubleshoot > Advanced options > Startup Repair

This can help when the failed installation has damaged startup configuration.

It will not fix an incompatible driver or failing storage device, but it may restore access to Windows.

System Restore or Point-in-Time Restore

When an appropriate restore point exists, Windows may be able to return system files, drivers and settings to an earlier state.

Personal documents are not intended to be the target of System Restore, but applications and drivers installed after the selected point may be affected.

If BitLocker is active, the recovery key may be required.

Should You Uninstall the Update After Windows Starts?

When the update completed but caused crashes or other severe problems, open:

Settings > Windows Update > Update history > Uninstall updates

Select the affected update where Windows allows removal.

Microsoft recommends trying the Windows repair-reinstallation option first on Windows 11 where appropriate, but also documents update removal through Settings and Windows RE.

Do not repeatedly uninstall important security updates as a permanent solution.

Instead:

Record the problematic KB.
Check its release-health information.
Install any corrected or superseding update.
Update the affected driver or application.
Report the failure to the IT provider.

When the SSD May Be Responsible

A failing storage drive can cause updates to:

Fail at different percentages
Roll back unpredictably
Produce corrupted-file errors
Take unusually long
Trigger freezes or blue screens
Fail to retain downloaded files
Disappear during a restart

Warning signs include:

Disk or NTFS errors in Event Viewer
Critical storage warnings
Manufacturer diagnostics reporting failure
Repeated file corruption
Unusual clicking from a hard drive
The SSD intermittently disappearing from firmware
Windows becoming read-only or unresponsive

Back up important files immediately when storage failure is suspected.

Do not reset or clean-install Windows onto a drive that has failed hardware diagnostics. The installation may overwrite recoverable data without correcting the hardware problem.

Why Pausing Updates Is Not a Real Fix

Pausing Windows Update can temporarily stop the computer from downloading and retrying the failed update.

This can be useful while you:

Back up data
Obtain updated drivers
Wait for a Microsoft fix
Arrange support
Investigate a business-wide issue

However, pausing does not resolve the cause. When the pause expires, Windows will normally offer the applicable update again.

Security updates should not be postponed indefinitely.

For business environments, use managed update rings, deployment controls or an approved hold rather than repeatedly pausing individual devices.

Common Mistakes to Avoid

Pressing Retry Over and Over

Repeated installation attempts rarely fix an unchanged driver, storage or servicing problem.

Deleting Random Registry Keys

Update error codes often identify a broad category rather than one universal Registry fix.

Disabling Secure Boot

A normal Windows update failure is not a reason to weaken boot security.

Clearing the TPM

This can create BitLocker and authentication complications without repairing Windows Update.

Deleting the Recovery or EFI Partition

These partitions are important for Windows startup and recovery.

Disabling Antivirus Permanently

Update or temporarily remove a confirmed incompatible third-party product, then restore appropriate protection.

Running Several “Windows Repair” Utilities

Unverified tools can modify update services, permissions and system files in unsupported ways.

Resetting Windows Too Early

A repair reinstall, SetupDiag investigation or driver fix may resolve the issue while preserving applications.

Ignoring the Error Code

The code and setup phase often provide the strongest clue to the underlying cause.

Updating Every Driver from an Unknown Website

Use Windows Update and the official computer or component manufacturer.

A Practical Rollback-Loop Checklist

When an update repeatedly installs and rolls itself back:

Stop retrying the update continuously.
Back up important files.
Save the BitLocker recovery key.
Run winver and record the current build.
Open Update history.
Record the failed KB and error code.
Check Microsoft’s known-issues information.
Restart Windows properly.
Run the Windows Update troubleshooter.
Check free storage space.
Disconnect non-essential hardware.
Check Device Manager for errors.
Install official driver and firmware updates.
Review incompatible antivirus, backup and encryption tools.
Run DISM.
Run SFC.
Perform a clean boot.
Reset the Windows Update cache where appropriate.
Retry the update once.
Use SetupDiag for a failed feature upgrade.
Review Panther and Rollback logs.
Use Fix problems using Windows Update for servicing corruption.
Use Windows RE if Windows cannot start.
Uninstall the latest update from recovery when necessary.
Test the SSD when corruption or inconsistent failures continue.
Escalate managed business devices to the IT provider.

How Hamilton Group Can Help

A rollback message tells you that Windows protected the computer by restoring its earlier state. It does not explain what caused the installation to fail.

Hamilton Group’s experienced IT team can identify the actual cause rather than repeatedly resetting Windows Update.

Update-Failure Diagnosis

We can analyse:

Failed KB numbers
Windows Update error codes
SetupDiag results
Panther and Rollback logs
CBS and DISM servicing logs
Event Viewer
Installation phases and operations

Driver and Firmware Remediation

Our engineers can identify and correct incompatible:

Storage drivers
Graphics drivers
Network adapters
USB and Thunderbolt components
Docking stations
BIOS or UEFI firmware
SSD firmware

Windows Repair

We can repair:

Component-store corruption
Damaged system files
Windows Update services
Recovery Environment problems
Failed feature-upgrade state
Boot configuration

Where appropriate, we can reinstall the current Windows version while preserving applications, settings and files.

Business Update Management

For managed environments, Hamilton Group can investigate:

Microsoft Intune update rings
Feature-update policies
Windows Autopatch
WSUS or Configuration Manager deployments
Safeguard holds
Endpoint-security conflicts
BitLocker readiness
Devices repeatedly failing the same update

We can pause or stage deployments safely while the cause is investigated, rather than leaving every user to fight the same rollback loop individually.

Hardware and Storage Testing

When installation failures indicate a physical problem, we can test:

SSD health
Memory
Storage controllers
Motherboards
Power systems
Cooling and stability

Hamilton Group aims to make first contact on IT support requests within 15 minutes, helping businesses address repeated update failures before they create security gaps or extended downtime.

Break the Loop by Finding the Cause

When an update installs and then rolls itself back, Windows is telling you that the new state could not be completed safely.

The correct sequence is:

Identify the update, record the error, protect the data, check known issues, repair Windows, isolate drivers and software, and then retry once.

When the failure involves a feature update, SetupDiag and the Windows Setup logs are often far more valuable than another blind installation attempt.

Call 0330 043 0069, book a meeting with one of our experts or visit hgmssp.com for experienced help resolving Windows Update failures and rollback loops.

Previous Next