How to Uninstall a Specific Windows Update That Broke Something

A Windows update installs.

The PC restarts.

Then something that worked perfectly yesterday suddenly stops working.

You might see:

Wi-Fi or Bluetooth problems

disappearing printers

broken audio

flickering monitors

application crashes

blue screens

severe performance problems

unexpected restarts

Removing the latest update may fix the problem.

But don't immediately uninstall every recent Windows update.

Windows Update can install quality updates, drivers and feature updates around the same time, while applications and firmware may also have changed independently.

The objective is:

Identify exactly what changed, reverse the right change safely and restore current security protection as quickly as possible.

First: Was the Update Really the Cause?

A Windows update becomes a reasonable suspect when:

the problem started immediately afterwards

the affected feature worked normally before

several similar PCs developed the same fault

Microsoft has documented a matching problem

removing the update restores normal behaviour

It becomes less convincing when the fault existed beforehand, only one application is affected and that application also updated, or the problem remains after the Windows update is removed.

Record when the problem started before changing anything.

Identify the Exact Update

Open:

Settings > Windows Update > Update history

Find what installed immediately before the problem began.

Record:

KB number

installation date

update type

Windows version/build

Press:

Windows + R

and enter:

winver

Keep the complete OS build number.

This gives you something concrete to compare after rollback.

Check Microsoft Before Removing It

Before uninstalling a security update, check Microsoft's current release-health information.

Microsoft publishes known Windows issues and uses safeguard holds to prevent feature upgrades reaching systems with known compatibility problems.

There may already be:

a newer cumulative update

an out-of-band fix

a corrected driver

an application update

a documented workaround

Installing Microsoft's fix is generally preferable to leaving a security update removed.

Method 1: Uninstall a Quality Update Normally

If Windows still starts:

Settings > Windows Update > Update history > Uninstall updates

Find the relevant update and choose:

Uninstall

Microsoft documents this as the standard Windows method for removing supported installed updates. Some updates cannot be uninstalled.

Restart when requested.

Then reproduce the exact original problem.

Don't just check whether Windows starts.

If printing was broken, print.

If Bluetooth failed, reconnect the device.

If the dock was affected, test its displays, Ethernet and USB.

Driver Update? Roll Back the Driver Instead

If the fault involves:

graphics

networking

Bluetooth

audio

storage

webcam

printer

check whether Windows installed a driver update.

Open:

Device Manager > affected device > Properties > Driver

If available, choose:

Roll Back Driver

Removing a cumulative Windows update may achieve nothing if the actual change was the network, graphics or audio driver.

If rollback is unavailable, obtain an appropriate driver from:

Windows Update

the PC manufacturer

the hardware manufacturer

Avoid generic driver-updater websites.

Windows Won't Boot? Use WinRE

If the update leaves Windows unable to reach the desktop, use Windows Recovery Environment.

From WinRE choose:

Troubleshoot > Advanced options > Uninstall Updates

Microsoft currently provides options for removing the latest applicable quality or feature update from recovery.

A BitLocker-protected machine may request its recovery key.

Feature Update? Use Go Back

A feature-version upgrade is different from an ordinary cumulative update.

If a recent major Windows upgrade caused the fault and Windows still starts, check:

Settings > System > Recovery > Go back

The option exists only while Windows still has the files needed to return to the previous release.

This is much broader than removing one KB because applications, drivers and Windows configuration may also have changed during the upgrade.

Some Updates Need DISM

This is the advanced exception worth retaining in the article.

For some modern Windows 11 cumulative updates that combine servicing-stack and cumulative-update components, Microsoft's own release notes instruct administrators to use DISM.

First list packages:

DISM /Online /Get-Packages /Format:Table

Then, only after identifying the exact package Microsoft says should be removed:

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

Microsoft's April 2026 cumulative-update documentation explicitly gives this procedure for removing applicable LCUs.

This is not the normal starting point.

Use DISM package removal only when:

the exact Microsoft release notes support it

you have positively identified the package

the normal uninstall method is unavailable

important data is backed up

you understand the servicing implications

Do not guess package names.

Don't Assume WUSA Will Remove Every Modern Update

You may still find guides recommending:

wusa /uninstall /kb:1234567

WUSA has historically been useful for applicable standalone update packages.

Modern Windows servicing is more complicated.

A KB appearing in Update History does not guarantee that a simple WUSA command can reverse it.

Use:

Settings first

and then follow the specific Microsoft removal instructions for that update if additional steps are required.

What If Windows Says the Update Cannot Be Removed?

Do not start deleting files from:

C:\Windows\WinSxS

or:

C:\Windows\servicing

Instead consider:

installing a newer corrective update

rolling back the driver

System Restore

repairing the affected application

repairing Windows

Microsoft states that some updates cannot be uninstalled.

Use System Restore When Appropriate

If several system-level changes happened at once, System Restore may be more useful than trying to identify one package.

It can reverse recent:

drivers

applications

Windows configuration

system changes

without being intended as a personal-file backup.

Repair Windows Instead of Removing Security Updates

Windows 11 also provides:

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

Microsoft says this reinstalls the current version of Windows and repairs system files and components while preserving installed applications, files and settings.

This can be a better escalation path where:

update removal didn't help

servicing itself is damaged

updates repeatedly fail

Windows components are corrupted

Pause Updates Only Temporarily

If removing an update proves that it caused the problem, you may need to temporarily pause Windows Update while waiting for:

Microsoft's corrected cumulative update

an application fix

a compatible driver

But do not leave security updates paused indefinitely.

The goal is to return the computer to a fully supported and current patch level, not preserve the broken update state forever.

Business PCs Need Central Control

If a company has 50 laptops and the same KB breaks 20 of them, don't treat that as 20 unrelated support calls.

Investigate:

affected hardware models

driver versions

Windows builds

Microsoft-known issues

update ring

Intune/Autopatch deployment

Then decide whether the update should be paused or remediated centrally.

A locally removed update may simply be redeployed by the organisation's management system.

The Quick Decision Tree

Windows starts + monthly update suspected
→ Update history > Uninstall updates

Hardware broke after driver update
→ Device Manager > Roll Back Driver

Windows will not start
→ WinRE > Uninstall Updates

Major Windows version upgrade caused it
→ Recovery > Go back

Microsoft says the LCU requires package removal
→ Use the documented DISM procedure

Update cannot be removed
→ Check newer fix / System Restore / repair reinstall

Many business PCs affected
→ Manage the deployment centrally

What Not to Do

Avoid:

removing several updates at once

deleting Windows servicing files

forcing permanent packages to uninstall

assuming every Update History entry is removable

leaving security updates disabled indefinitely

resetting Windows before trying safer recovery options

Make one controlled change and test whether it actually solved the original fault.

How Hamilton Group Can Help

Hamilton Group can help identify whether a Windows update genuinely caused a problem before removing security fixes unnecessarily.

We can assist with:

Windows 11 update troubleshooting

KB identification

cumulative-update removal

driver rollback

WinRE

BitLocker recovery

DISM servicing

Windows repair

Microsoft Intune

Windows Autopatch

managed patching

If the same update affects several company devices, we can investigate and control the response centrally rather than manually repairing every PC.

Visit hgmssp.com or call 0330 043 0069.