How to Uninstall a Specific Windows Update That Broke Something

A Windows update installs successfully, the computer restarts—and something that worked yesterday suddenly stops working.

You might experience:

• Applications refusing to open
• Printers or scanners disappearing
• Wi-Fi or Bluetooth failures
• Games crashing or performing poorly
• File Explorer freezing
• Blue-screen errors
• Problems with sound, displays or docking stations
• Unexpected restarts
• Windows becoming unusually slow

Removing the update may restore normal operation, but it should not be the first reaction to every problem that appears after Patch Tuesday.

Windows updates frequently arrive alongside application updates, driver changes and firmware installations. The timing may be connected—or it may be a coincidence.

Before uninstalling anything, confirm which update was installed, check whether Microsoft has acknowledged the issue and determine whether a newer corrective update is already available. Microsoft does not generally recommend removing installed updates, and some updates cannot be uninstalled at all. 

The objective is not simply to make the problem disappear temporarily. It is to restore stability without leaving the computer unnecessarily exposed or causing a larger Windows servicing problem.

First: Confirm That the Update Is the Likely Cause

An update becomes a reasonable suspect when:

• The problem began immediately after its installation.
• The affected feature worked normally beforehand.
• Several computers developed the same problem after receiving the same update.
• Microsoft has documented a matching known issue.
• Removing or replacing the update resolves the behaviour.
• The issue returns when that update is installed again.

An update is less likely to be responsible when:

• The problem began before the update.
• Only one application is affected and that application also updated.
• A new device or driver was installed at the same time.
• The SSD is reporting errors.
• The computer is overheating or unstable outside Windows.
• The issue continues after the update is removed.

Record the exact time the problem started and compare it with Windows Update history, application-update records and any recent hardware changes.

Find the Exact Update

Open:

Settings > Windows Update > Update history

The page separates installed items into categories such as:

• Quality updates
• Driver updates
• Definition updates
• Other updates
• Feature updates

Find the update installed immediately before the problem appeared.

Record:

• Its full name
• Its KB number
• The installation date
• Whether it is a quality, driver or feature update
• The current Windows version and build

A monthly update usually has a number such as:

KB5091234

Do not remove an update simply because it is the newest entry. Confirm that its installation time matches the beginning of the fault.

Record the Current Windows Build

Press:

Windows key + R

Enter:

winver

Then press Enter.

Record the:

• Windows edition
• Version
• Complete OS build

For example:

Windows 11 Pro

Version 25H2

OS Build 26200.xxxxx

This gives you a baseline for confirming whether the build changes after removing the update.

Check Microsoft’s Known-Issues Information

Before uninstalling the update, search Microsoft’s Windows release-health information for:

• The KB number
• Your Windows version
• The specific application or device affected
• A known workaround
• An out-of-band update
• A resolved-issue notice

Microsoft’s Windows release-health service publishes current information about known issues, safeguards and servicing status for supported Windows releases. 

This check is important because the best solution may be to install a newer corrective update rather than remove the original security update.

For example, Microsoft may advise users to:

• Install an out-of-band fix
• Update a particular driver
• Restart an affected service
• Change a temporary setting
• Wait for a Known Issue Rollback
• Install the next cumulative update

Do not rely on an old forum post discussing a different Windows build.

Protect the Computer Before Removing Anything

Before uninstalling an update:

1. Back up important files.
2. Confirm that the backup can be opened.
3. Save the BitLocker recovery key.
4. Close applications.
5. Connect a laptop to reliable mains power.
6. Record the update’s KB number.
7. Create a screenshot of Update history.
8. Check whether the device is managed by your employer.

Removing a normal monthly update should not delete personal files, but Windows servicing, startup and recovery operations are never a substitute for a proper backup.

A BitLocker-protected device may ask for its recovery key after certain recovery or startup changes.

Method One: Uninstall the Update Through Settings

This is the preferred method when Windows still starts normally.

Open:

Settings > Windows Update > Update history

Scroll to Related settings, then select:

Uninstall updates

Find the relevant update and select:

Uninstall

Confirm the action and allow Windows to complete the removal.

Microsoft documents this as the standard Windows 11 method for removing an installed update. It also notes that some updates do not provide an uninstall option. 

Restart the computer when prompted.

Do not force the computer off while Windows displays messages such as:

• Working on updates
• Removing updates
• Preparing Windows
• Do not turn off your computer

The removal process may take several minutes and can involve more than one restart.

Check Whether the Update Was Actually Removed

After Windows starts:

1. Run winver again.
2. Compare the full OS build with the number recorded earlier.
3. Return to Windows Update > Update history.
4. Check whether the affected update still appears as installed.
5. Reproduce the original problem.

The update may remain visible in historical records even though the active package or current build has changed. Update history records previous servicing activity and is not always the same as the current uninstallable-package list.

The most important evidence is:

• The current build
• The active installed packages
• Whether the fault has disappeared

The Update Is in History but Not in “Uninstall Updates”

This is common and does not necessarily indicate that Windows Update is broken.

Possible explanations include:

• The update is not designed to be removable.
• It has been superseded by a newer cumulative update.
• Its contents are now part of another package.
• It is a servicing-stack component.
• It was a Defender intelligence or platform update.
• It was a driver rather than a normal Windows quality update.
• Component cleanup has removed the files required for rollback.
• The update was part of a feature-version installation.

Microsoft explicitly states that some Windows updates cannot be uninstalled. 

Do not start deleting files from:

C:\Windows\SoftwareDistribution

C:\Windows\WinSxS

C:\Windows\servicing

These folders do not provide a safe manual method for reversing an installed update.

Driver Updates Require a Different Approach

When Update history shows the change under Driver updates, removing a Windows quality update may not affect it.

Open:

Device Manager

Locate the affected device, then:

1. Right-click the device.
2. Select Properties.
3. Open the Driver tab.
4. Select Roll Back Driver, when available.
5. Choose the reason for the rollback.
6. Restart the computer.

The button may be unavailable when Windows no longer retains the previous driver package.

In that situation, obtain the correct driver from:

• The computer manufacturer
• The device manufacturer
• Windows Update

Do not download drivers from an unknown “driver update” website.

Optional Preview Updates

Windows may offer non-security preview updates before their fixes are included in a later regular cumulative update.

When the problem began after installing an optional preview:

1. Record its KB number.
2. Check Microsoft’s release notes.
3. Remove it through Uninstall updates when available.
4. Restart and test.
5. Avoid reinstalling the same preview while the problem is unresolved.

You can also turn off the option that requests eligible non-security updates as soon as they are available, if you do not need early access to those changes. Microsoft describes this Windows Update option as controlling how quickly eligible feature and non-security updates are offered. 

Method Two: Use Windows Recovery Environment

When Windows no longer reaches the desktop after the update, remove the latest update from the Windows Recovery Environment, or WinRE.

You may enter WinRE automatically after repeated failed starts.

When you can reach the sign-in screen:

1. Hold Shift.
2. Select the power icon.
3. Select Restart while continuing to hold Shift.

Then select:

Troubleshoot > Advanced options > Uninstall Updates

Windows normally offers:

• Uninstall latest quality update
• Uninstall latest feature update

Microsoft documents this recovery route for computers that cannot access normal Windows after an update. 

Uninstall Latest Quality Update

Choose this when a recent:

• Security update
• Monthly cumulative update
• Quality update

has prevented Windows from working properly.

Uninstall Latest Feature Update

Choose this when the computer has moved to a new Windows release, such as from 24H2 to 25H2, and the new version is causing serious problems.

WinRE generally targets the most recent applicable update. It does not provide the same long list of selectable KB numbers found in Settings.

An encrypted device may request the BitLocker recovery key before continuing.

Removing a Feature Update Through Settings

A feature update is different from a monthly quality update.

After upgrading Windows to a new version, open:

Settings > System > Recovery

Look for:

Go back

Microsoft states that this option is normally available for a limited period—typically ten days after upgrading. Applications added, removed or changed after the upgrade may be affected by returning to the previous version. 

The option may be missing when:

• The rollback period has expired.
• The previous Windows files have been deleted.
• Windows.old is no longer present.
• Storage cleanup removed the required files.
• Organisational policy controls the recovery option.

Deleting the previous Windows installation removes the normal ability to go back. 

Advanced Method: Removing a Package with DISM

DISM can service Windows packages, but it should not be the first method used by an ordinary user.

For some modern cumulative updates containing combined servicing-stack and cumulative-update components, Microsoft’s individual release notes instruct administrators to remove the LCU using DISM and the full package name. 

Open Terminal as administrator and list packages:

DISM /Online /Get-Packages /Format:Table

Locate the package that corresponds to the affected update.

The package name may look similar to:

Package_for_RollupFix~31bf3856ad364e35~amd64~~26200.xxxx.1.0

The removal command is:

DISM /Online /Remove-Package /PackageName:<full-package-name>

For example:

DISM /Online /Remove-Package /PackageName:Package_for_RollupFix~31bf3856ad364e35~amd64~~26200.xxxx.1.0

Restart after the operation completes.

Important DISM Warnings

Use this method only when:

• You have identified the exact package.
• Microsoft’s release notes support its removal.
• Settings cannot remove it.
• You have a verified backup.
• You understand the potential servicing impact.

Do not remove packages based only on similar-looking version numbers.

Selecting the wrong component can damage:

• Windows servicing
• Recovery functions
• Optional features
• Future update installation
• Windows startup

For business devices, an experienced IT engineer should perform and document the removal.

What About WUSA?

You may see instructions using:

wusa /uninstall /kb:1234567

WUSA is the Windows Update Standalone Installer and has historically supported uninstalling applicable standalone updates.

However, modern cumulative-update servicing may package updates differently, and a KB number in Update history does not guarantee that WUSA can remove it directly. Microsoft’s current Intune guidance uses DISM package removal for managed update packages rather than assuming that a KB-number-based WUSA uninstall will work universally. 

Use the Settings interface first.

When the exact update’s Microsoft release notes specify a DISM procedure, follow those instructions rather than repeatedly trying WUSA commands.

If Windows Says the Update Is Required

Windows may report that the update:

• Is required by the computer
• Cannot be uninstalled
• Is permanent
• Is not installed
• Has already been superseded

Do not try to bypass the restriction by changing package-manifest files or Registry ownership.

Instead, consider:

• Installing a newer corrective update
• Rolling back the affected driver
• Using System Restore
• Repairing the affected application
• Reinstalling the current Windows version
• Restoring from a known-good backup
• Waiting for an official resolution

A newer cumulative update normally contains previous servicing content alongside its newer fixes, so attempting to remove an older superseded package may not be meaningful.

Use System Restore When the Update Cannot Be Removed

System Restore can return Windows system files, settings, drivers and installed-program configuration to an earlier restore point without targeting ordinary personal documents.

Open Start and search for:

Create a restore point

Select System Restore, then choose a restore point created before the fault began.

When Windows cannot start, use:

WinRE > Troubleshoot > Advanced options > System Restore

Microsoft describes System Restore as a method of reversing recent system changes without affecting personal files. BitLocker-protected systems may require the recovery key in WinRE. 

System Restore may remove or roll back:

• Recently installed drivers
• Applications
• Windows settings
• Update-related system changes

It does not replace a file backup.

Repair Windows Instead of Removing the Update

Sometimes the update exposed corruption that already existed in Windows rather than directly causing the problem.

Windows 11 provides a recovery option under:

Settings > System > Recovery > Fix problems using Windows Update

Select:

Reinstall now

This reinstalls the current Windows version while preserving applications, personal files and settings on supported devices. 

This may be appropriate when:

• The update cannot be uninstalled.
• Windows components are damaged.
• Update installation repeatedly fails.
• Removing the package did not fix the issue.
• The system needs repair without a full reset.

The option may be unavailable on devices managed by an organisation.

Pause the Update Temporarily

After uninstalling the update, Windows may offer it again.

Open:

Settings > Windows Update

Use the Pause updates control to delay updates temporarily while you:

• Confirm that the removal fixed the problem
• Wait for Microsoft’s corrected update
• Obtain a compatible driver
• Contact the software vendor
• Arrange professional support

Pausing updates delays them only until the selected date. When updates resume, Windows checks again and may download the package or a newer replacement. 

Do not leave security updates paused indefinitely.

The safer long-term resolution is to install:

• A superseding cumulative update
• An out-of-band fix
• A corrected driver
• A compatible application release
• Microsoft’s documented workaround

Test Methodically After Removal

Once Windows has restarted:

1. Run winver.
2. Confirm the current OS build.
3. Open the affected application or device.
4. Repeat the exact activity that previously failed.
5. Check Reliability Monitor.
6. Review Event Viewer for recurring faults.
7. Restart the computer again.
8. Test shutdown and startup.
9. Confirm Windows Security remains active.
10. Check Windows Update for a newer replacement.

Do not declare the problem resolved after one successful application launch.

A useful test should reproduce the original conditions.

The Problem Continues After Removing the Update

When the issue remains, the update may not have been the actual cause.

Investigate:

• Application updates
• Device drivers
• Firmware
• Antivirus or endpoint protection
• Browser extensions
• Storage health
• Memory
• Thermal throttling
• User-profile corruption
• Network or VPN problems

Reinstalling the update may then be appropriate, particularly when it contains important security fixes.

Before reinstalling it:

1. Install current drivers and application updates.
2. Repair Windows components where necessary.
3. Restart the computer.
4. Check Microsoft’s release-health information.
5. Install the latest cumulative update rather than searching for an old package manually.

Business Computers Need Additional Care

On a managed business computer, updates may be controlled through:

• Microsoft Intune
• Windows Autopatch
• Configuration Manager
• WSUS
• Group Policy
• Remote monitoring and management software

Removing an update locally may not resolve the deployment issue. The management platform may offer it again or report the device as non-compliant.

Before uninstalling security updates on a company device, IT should establish:

• Which users and devices are affected
• Whether the issue is widespread
• Whether Microsoft has published a mitigation
• Whether a replacement update exists
• The security risk of removal
• Whether the deployment should be paused centrally
• How and when the update will be restored

The action should be documented, time-limited and tested.

Common Mistakes to Avoid

Removing several updates at once

Remove only the update that matches the fault’s timeline.

Choosing the wrong KB

Similar-looking KB numbers can apply to different products, Windows versions or components.

Removing a security update without checking for a fix

A newer cumulative or out-of-band update may solve the problem without creating a security gap.

Deleting Windows servicing files

Never manually remove packages from WinSxS or the servicing folders.

Forcing a permanent package to uninstall

The restriction may exist because Windows depends on that component.

Treating Update history as the active package list

Historical entries can remain even when a package has been replaced or removed.

Pausing updates permanently

Use the pause only while investigating and obtaining a safe resolution.

Resetting Windows immediately

Driver rollback, System Restore or a repair reinstall may resolve the issue with less disruption.

Forgetting BitLocker

Recovery operations can request the 48-digit recovery key.

A Practical Update-Removal Checklist

When a specific Windows update appears to have broken something:

1. Record exactly when the problem began.
2. Check Windows Update history.
3. Record the KB number.
4. Run winver.
5. Record the complete OS build.
6. Check Microsoft’s release-health information.
7. Look for a newer corrective update.
8. Back up important files.
9. Save the BitLocker recovery key.
10. Confirm whether the device is business-managed.
11. Use Settings > Windows Update > Update history > Uninstall updates.
12. Restart normally.
13. Check whether the build changed.
14. Reproduce the original problem.
15. Roll back a driver separately when appropriate.
16. Use WinRE when Windows cannot start.
17. Use Go back for a recent feature-version upgrade.
18. Use DISM only when the exact Microsoft instructions support it.
19. Consider System Restore when the update cannot be removed.
20. Consider a Windows repair reinstall when components are damaged.
21. Pause updates only temporarily.
22. Install the corrected or superseding update promptly.
23. Escalate business-wide problems to the IT provider.

How Hamilton Group Can Help

Removing a Windows update is easy when the correct update appears in the uninstall list.

The difficult part is proving that it caused the fault, understanding the security impact and preventing the same problem from returning.

Hamilton Group’s experienced IT team can help with:

Update Identification

We can establish:

• Which KB was installed
• Which Windows build is active
• Whether the update is removable
• Whether Microsoft has acknowledged the issue
• Whether a corrected package is available

Safe Update Removal

We can remove supported:

• Monthly cumulative updates
• Optional preview updates
• Driver updates
• Feature updates
• DISM packages where Microsoft’s servicing guidance requires it

Recovery When Windows Will Not Start

Hamilton Group can work through:

• Windows Recovery Environment
• Uninstall Updates
• System Restore
• Startup Repair
• BitLocker recovery
• Boot and servicing repair

Driver and Application Compatibility

When the update has exposed an incompatible application or driver, we can update, repair or replace the actual component rather than leaving Windows unpatched indefinitely.

Business Update Management

For managed organisations, we can:

• Pause a problematic deployment centrally
• Identify affected devices
• Review Microsoft release-health alerts
• Test replacement updates
• Manage update rings
• Track remediation
• Restore compliance safely

Windows Repair

Where uninstalling the update is not possible or does not solve the issue, we can repair the Windows installation while protecting applications, settings and data.

Hamilton Group aims to make first contact on IT support requests within 15 minutes, helping businesses respond quickly when a Windows update disrupts important work.

Remove the Right Update for the Right Reason

A Windows update appearing immediately before a problem is useful evidence—but not final proof.

Start by recording the KB number, Windows build and exact symptoms. Check Microsoft’s current known-issues information, then use the supported Windows uninstall tools rather than deleting servicing files or applying random Registry changes.

When removing the update restores stability, pause it only long enough to obtain the corrected update, driver or application fix.

Call 0330 043 0069, book a meeting with one of our experts or visit hgmssp.com for experienced help with problematic Windows updates, recovery and business patch management.