How to Uninstall a Specific Windows Update That Broke Something

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

You may experience:

• An application refusing to open
• Printers or scanners disappearing
• Wi-Fi or Bluetooth failing
• Audio devices no longer being detected
• External monitors flickering
• Games or creative software crashing
• File Explorer becoming unstable
• Blue-screen errors
• Unexpected restarts
• Severe performance problems

Removing the update may restore normal operation—but it should not be your automatic response to every problem that appears after Windows Update.

Windows updates often arrive alongside application, driver and firmware changes. The timing may be connected, or it may be a coincidence. Before removing anything, identify the exact update, check whether Microsoft has acknowledged a matching issue and establish whether a newer corrective update is already available.

Microsoft does not generally recommend uninstalling security updates because doing so removes the protections they introduced. Microsoft also confirms that some Windows updates cannot be removed. 

The goal is therefore not simply to remove the newest update. It is to:

Identify the right update, remove it safely, confirm whether it caused the problem and restore security protection as quickly as possible.

First: Is the Update Really the Cause?

An update becomes a reasonable suspect when:

• The problem began immediately after installation.
• The affected device or application worked normally beforehand.
• Several computers developed the same problem after receiving the same update.
• Microsoft or the application vendor has documented a matching issue.
• Removing the update restores normal operation.
• The problem returns if that update is installed again.

An update is less likely to be responsible when:

• The problem started before the update.
• A new application or driver was installed at the same time.
• The issue affects only one user profile.
• The storage drive is reporting errors.
• The computer is overheating or unstable outside Windows.
• The fault continues after the update is removed.

Record the exact date and approximate time when the issue began. Compare that with Windows Update history, application updates and recent driver installations.

Find the Exact Update

Open:

Settings > Windows Update > Update history

Look through categories including:

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

Find the entry installed immediately before the fault began.

Record:

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

A monthly Windows update normally has an identifier similar to:

KB50xxxxx

Do not remove an update simply because it is the newest entry. Confirm that the installation time and symptoms correspond.

Record the Current Windows Build

Press:

Windows key + R

Enter:

winver

Press Enter.

Record:

• Windows edition
• Windows version
• Full OS build

For example:

Windows 11 Pro

Version 25H2

OS Build 26200.xxxxx

This provides a baseline so you can confirm whether the servicing revision changed after uninstalling the update.

Check Microsoft’s Known-Issues Information

Before removing the package, check Microsoft’s Windows release-health information using:

• The KB number
• Your Windows version
• The affected application or hardware
• The symptoms you are seeing

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

A documented resolution may tell you to:

• Install a newer cumulative update
• Install an out-of-band fix
• Update a particular driver
• Update the affected application
• Apply a temporary workaround
• Wait for Microsoft’s Known Issue Rollback
• Avoid uninstalling the security package

Installing a corrective update is usually preferable to removing security protection.

Protect the Computer Before Removing the Update

Before beginning:

1. Back up important files.
2. Confirm that the backup can be opened.
3. Save any unsynchronised application data.
4. Close running applications.
5. Connect laptops to reliable mains power.
6. Record the update’s KB number.
7. Take a screenshot of Update history.
8. Verify that the BitLocker recovery key is accessible.
9. Check whether the device is managed by your employer or IT provider.

A BitLocker recovery key is a 48-digit code used when Windows cannot automatically unlock an encrypted drive. Microsoft cannot retrieve or recreate a lost key, so its location should be verified before using recovery tools. 

Removing an ordinary update should not delete personal files, but recovery and servicing operations never replace a verified backup.

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 update you identified and select:

Uninstall

Confirm the action.

Microsoft documents this as the standard method for removing a supported installed update from Windows 11. 

Allow Windows to complete the process and restart when prompted.

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

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

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

Confirm That the Update Was Removed

After Windows starts:

1. Run winver again.
2. Compare the OS build with the number recorded earlier.
3. Return to Windows Update > Update history.
4. Test the exact application or device that was failing.
5. Restart the PC once more.
6. Repeat the original test.

Update history may continue to show that a package was installed at an earlier date. That page records servicing activity and is not always identical to the list of packages Windows currently permits you to uninstall.

The useful evidence is:

• Whether the active OS build changed
• Whether the original fault disappeared
• Whether Windows remains stable after another restart

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

The Update Appears in History but Not Under “Uninstall Updates”

This is common.

Possible reasons include:

• The update is not designed to be removed.
• It has been replaced by a newer cumulative package.
• Its components have been incorporated into another update.
• It is a servicing-stack component.
• It is a Microsoft Defender intelligence update.
• It is a driver rather than a Windows quality update.
• Windows no longer retains the files required for removal.
• It was installed as part of a feature update.

Microsoft explicitly states that not every installed update can be uninstalled. 

Do not manually delete files from:

C:\Windows\WinSxS

C:\Windows\servicing

C:\Windows\SoftwareDistribution

These folders are part of Windows servicing and do not provide a safe manual update-removal method.

Driver Updates Need a Different Approach

If the relevant entry appears under Driver updates, removing a Windows cumulative update may not affect it.

Open:

Device Manager

Find the affected hardware, then:

1. Right-click the device.
2. Select Properties.
3. Open the Driver tab.
4. Record the current driver provider and version.
5. Select Roll Back Driver, where available.
6. Choose the appropriate reason.
7. Restart Windows.

Microsoft recommends driver rollback when hardware worked correctly before a recent driver or Windows update. The option is available only when Windows still retains the previous driver package. 

Typical devices include:

• Graphics adapters
• Network adapters
• Bluetooth radios
• Audio devices
• Storage controllers
• Webcams
• Printers

If Roll Back Driver is unavailable, obtain the correct known-good driver from:

• Windows Update
• The computer manufacturer
• The device manufacturer

Avoid generic driver-updater websites and utilities.

Method Two: Remove the Latest Update Through Windows Recovery Environment

Use the Windows Recovery Environment—WinRE—when Windows no longer reaches the desktop after an update.

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. Choose Restart while continuing to hold Shift.

Then select:

Troubleshoot > Advanced options > Uninstall Updates

Windows provides recovery options for removing the latest applicable quality or feature update. 

Uninstall Latest Quality Update

Choose this when the problem followed a recent:

• Monthly cumulative update
• Security update
• Quality update
• Out-of-band Windows update

Uninstall Latest Feature Update

Choose this when the PC recently moved to a different Windows release and the new version is causing serious compatibility or startup problems.

WinRE normally removes the latest applicable update. It does not provide the same selectable list of historical KB numbers available through Settings.

A BitLocker-protected computer may request the recovery key before allowing access to the Windows installation. 

Returning to the Previous Windows Feature Version

A feature update is different from a normal monthly cumulative update.

For example:

Windows 11 24H2 → Windows 11 25H2

When Windows still starts, open:

Settings > System > Recovery

Look for:

Go back

Microsoft makes the option available only for a limited period after upgrading. The files required for returning to the earlier version are normally retained for approximately ten days unless they are deleted sooner. 

The option may be unavailable when:

• The rollback period has expired.
• Storage cleanup removed the previous Windows files.
• The Windows.old folder has been deleted.
• Windows was clean-installed rather than upgraded.
• Organisational policy controls recovery.

Returning to the previous Windows version may affect applications, drivers and settings changed after the feature update. Back up current work first.

Advanced Removal with DISM

Deployment Image Servicing and Management—DISM—can list and remove certain Windows servicing packages.

This is an advanced method and should not be the first option for an ordinary user.

Microsoft’s release notes for some modern combined servicing-stack and cumulative updates instruct administrators to identify the LCU package name and remove it using DISM. 

Open Terminal as administrator and list packages:

DISM /Online /Get-Packages /Format:Table

A cumulative package identity may look similar to:

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

The removal syntax is:

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

For example:

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

Restart after the process completes.

Use DISM Only When:

• The exact Microsoft release notes support package removal.
• You have identified the complete package name.
• The normal Settings method is unavailable.
• Important data has been backed up.
• The BitLocker recovery key is accessible.
• You understand the recovery plan if Windows no longer starts.

Do not choose a package merely because its version number looks similar to the KB you want to remove.

Removing the wrong component can damage:

• Windows servicing
• Future update installation
• Optional Windows features
• Recovery components
• Startup

For business devices, this work should be performed and documented by an experienced IT engineer.

What If Windows Says the Update Cannot Be Removed?

Windows may report that the package:

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

Do not bypass this by editing package manifests, taking ownership of servicing folders or deleting component-store files.

Safer alternatives include:

• Installing a newer corrective cumulative update
• Rolling back the affected driver
• Using System Restore or point-in-time recovery
• Repairing the affected application
• Repairing the current Windows installation
• Restoring from a known-good backup
• Following Microsoft’s documented workaround

Because Windows quality updates are cumulative, newer packages normally include earlier applicable fixes as well as the latest changes. 

Use System Restore or Point-in-Time Restore

When the update cannot be individually removed, a restore point may be able to return Windows to an earlier state.

Search Start for:

Create a restore point

Open System Restore and select a restore point created before the problem began.

Depending on the Windows version and configuration, point-in-time restore may also be available. Microsoft describes it as restoring the system—including applications, settings and files—to an earlier saved state. Changes made after the selected restore point can be lost. 

Review the affected-programs list before continuing.

A restore operation is broader than uninstalling one KB. It can reverse:

• Recent drivers
• Applications
• Windows settings
• Update-related system changes
• Files changed after the selected point, depending on the recovery method

Make a current backup first.

Repair Windows Instead of Removing the Update

Sometimes an update exposes Windows corruption that was already present rather than directly causing the fault.

Windows 11 provides:

Settings > System > Recovery > Fix problems using Windows Update

Select:

Reinstall now

This reinstalls the current Windows version while attempting to preserve applications, personal files and settings. Microsoft positions it as a repair option for system and Windows Update problems. 

This may be preferable when:

• The package cannot be removed.
• Windows components are damaged.
• Update installations repeatedly fail.
• Removing the update did not fix the fault.
• You want to avoid a full reset or clean installation.

The option may be unavailable on devices managed through organisational update policies.

Pause Updates Temporarily

After removal, Windows may offer the same update again.

Open:

Settings > Windows Update

Use Pause updates temporarily while you:

• Confirm that removal fixed the issue
• Wait for a corrected cumulative update
• Obtain an updated driver
• Install a compatible application version
• Contact the software vendor
• Arrange professional support

Windows 11’s pause control allows a specific resumption date within the supported pause period. Pausing is temporary; updates resume automatically when the selected period expires. 

Do not leave security updates paused indefinitely.

Your long-term resolution should be one of the following:

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

Test the Computer Methodically

After uninstalling the update:

1. Check the Windows build with winver.
2. Open the affected application or connect the affected device.
3. Repeat the exact task that previously failed.
4. Test after another restart.
5. Check Reliability Monitor.
6. Review Event Viewer for repeating errors.
7. Confirm Windows Security remains active.
8. Check whether a newer update is available.
9. Test printing, networking, audio or displays where relevant.
10. Record the outcome.

A good test should recreate the conditions under which the original fault occurred.

For example, if the problem involved a docking station, test:

• Dock connection
• External displays
• Ethernet
• USB devices
• Sleep and wake
• Restart while docked

The Problem Continues After Removing the Update

If the fault remains, the update may not have been the real cause.

Investigate:

• Application updates
• Device drivers
• BIOS or firmware
• Antivirus or endpoint protection
• Browser extensions
• Storage health
• Memory faults
• Thermal throttling
• User-profile corruption
• Network or VPN issues
• Hardware failure

Reinstalling the current cumulative update may then be the safest choice because it restores the security fixes that were removed.

Before reinstalling:

1. Install current manufacturer drivers and application updates.
2. Repair Windows components where necessary.
3. Restart the PC.
4. Check Microsoft’s release-health guidance.
5. Install the latest applicable cumulative update.

Do not search for and reinstall an old package manually when a newer cumulative update has replaced it.

Business Computers Require Additional Care

A managed business computer may receive updates through:

• Microsoft Intune
• Windows Autopatch
• Configuration Manager
• Windows Server Update Services
• Group Policy
• Remote monitoring and management software

Removing the package locally may not resolve the deployment issue. The management system may offer it again, report the device as non-compliant or enforce a deadline.

Before removing a security update across business computers, IT should establish:

• Which devices are affected
• Whether the problem is reproducible
• Whether Microsoft has documented it
• Whether a replacement update exists
• The security risk created by removal
• Whether deployment should be paused centrally
• How and when protection will be restored
• Which users require communication or support

The decision should be documented and time-limited.

Common Mistakes to Avoid

Removing Several Updates at Once

Remove only the package that matches the fault’s timeline. Otherwise, you will not know which action made the difference.

Choosing the Wrong KB Number

Similar KB numbers can apply to different Windows versions, products and architectures.

Removing a Security Update Without Checking for a Fix

A newer cumulative or out-of-band package may correct the issue without creating a security gap.

Deleting Windows Servicing Files

Never manually remove content from WinSxS or Windows servicing folders.

Forcing a Permanent Package to Uninstall

The package may be required by the current Windows servicing state.

Assuming Update History Is the Uninstall List

Update history records previous installation activity. It does not mean every listed item remains individually removable.

Pausing Updates Indefinitely

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

Forgetting BitLocker

Recovery tools may request the 48-digit key.

Resetting Windows Immediately

Driver rollback, update removal, System Restore or a repair reinstall may solve the problem with far less disruption.

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. Identify and record the KB number.
4. Run winver.
5. Record the full OS build.
6. Check Microsoft’s release-health information.
7. Look for a newer corrective update.
8. Back up important files.
9. Verify the BitLocker recovery key.
10. Confirm whether the device is business-managed.
11. Use Update history > Uninstall updates first.
12. Restart normally.
13. Confirm whether the build changed.
14. Reproduce the original problem.
15. Roll back a driver separately where appropriate.
16. Use WinRE when Windows cannot start.
17. Use Go back for a recent feature-version upgrade.
18. Use DISM only when Microsoft’s exact servicing guidance supports it.
19. Consider System Restore when the package cannot be removed.
20. Use a Windows repair reinstall when components are damaged.
21. Pause updates only temporarily.
22. Install the corrected or superseding update promptly.
23. Escalate widespread business issues to your IT provider.

How Hamilton Group Can Help

Removing an update is straightforward when the correct package is available in the uninstall list.

The difficult part is proving that it caused the fault, understanding the security impact and preventing the same issue 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 a related problem
• Whether a corrected package is available

Safe Update Removal

Where appropriate, we can remove or roll back:

• Monthly cumulative updates
• Optional preview updates
• Driver updates
• Feature updates
• DISM packages supported by Microsoft’s servicing guidance

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 an update exposes 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 information
• Test replacement updates
• Manage update rings
• Track remediation
• Restore compliance safely

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

An update appearing immediately before a problem is useful evidence—but it is not final proof.

Start by recording the KB number, complete Windows build and exact symptoms. Check Microsoft’s current known-issue information and use supported removal 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 package, 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.