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 external monitors
application crashes
blue screens
severe performance issues
unexpected restarts
Removing the latest update may fix the problem.
But don't immediately uninstall every recent Windows update.
The first job is to establish what actually changed.
A Windows Update session can install:
quality updates
security updates
feature updates
drivers
Microsoft Defender updates
and an application or firmware update may have happened at roughly the same time.
So the goal is not:
“Remove the newest update.”
It is:
“Identify the change that actually caused the problem, reverse it safely, and restore current security protection as quickly as possible.”
First: Was the Windows Update Really the Cause?
An update becomes a reasonable suspect when:
the problem began immediately afterwards
the affected hardware or application worked normally before
several similar computers developed the same issue
Microsoft or the vendor has documented the same behaviour
removing the update restores normal operation
An update is less convincing when:
the problem started beforehand
only one user profile is affected
a driver or application changed at the same time
hardware is unstable independently of Windows
the problem remains after removing the update
Record the approximate time the fault began before changing anything.
That timeline is valuable evidence.
Step 1: Identify the Exact Update
Open:
Settings > Windows Update > Update history
Look at the updates installed immediately before the problem began.
Record:
update name
KB number
installation date
update type
A typical monthly cumulative update has an identifier such as:
KB50xxxxx
Microsoft recommends using Update history to identify installed Windows updates before attempting removal.
Also Record Your Windows Build
Press:
Windows + R
Enter:
winver
Record the:
Windows edition
version
OS build
This gives you a baseline so you can confirm later whether the active servicing level actually changed.
Step 2: Check Whether Microsoft Already Knows About the Problem
Before removing a security update, check Microsoft's Windows release health information using:
KB number
Windows version
affected hardware/application
symptom
Microsoft uses Windows release health to publish current known issues, safeguards and resolutions.
You may discover that the correct fix is:
a newer cumulative update
an out-of-band update
a corrected driver
an application update
a documented workaround
That is usually preferable to removing security fixes.
Microsoft also uses safeguard holds to prevent feature updates being offered to devices where known compatibility problems exist. Microsoft specifically warns organisations against bypassing those holds casually.
Before Removing Anything
Take a few basic precautions.
Make sure:
important files are backed up
unsynchronised work is saved
the laptop is connected to mains power
you have recorded the KB number
your BitLocker recovery key is available
you know whether the PC is managed by your employer or IT provider
Removing an ordinary update should not normally delete personal documents, but servicing and recovery work should never be treated as a substitute for having a backup.
Method 1: Uninstall a Quality Update Through Settings
If Windows still starts normally, this is the preferred method.
Go to:
Settings > Windows Update > Update history
Then:
Uninstall updates
Find the update you identified.
Select:
Uninstall
Microsoft documents this as the standard Windows 11 method for removing supported installed updates.
Restart when prompted.
Do not force the PC off while Windows is removing or configuring updates.
Then Test the Original Problem
After Windows starts:
1. Run winver again.
2. Check whether the build changed.
3. Reproduce the exact original fault.
4. Restart once more.
5. Test again.
If the printer problem disappeared, test printing.
If the dock caused trouble, reconnect the dock and test:
monitors
USB
Ethernet
sleep/wake
Don't declare victory because one application opened successfully once.
What If the Update Is Listed but Cannot Be Uninstalled?
This is normal.
Microsoft explicitly states that some Windows updates cannot be removed.
Reasons can include:
the update is permanent
it has been superseded
it is part of the current servicing baseline
it is a Defender intelligence update
it is actually a driver update
Windows no longer retains the files needed to reverse it
Do not try to bypass this by manually deleting files from:
C:\Windows\WinSxS
or:
C:\Windows\servicing
Those are critical Windows servicing locations.
Driver Update? Roll Back the Driver Instead
This is one of the most important distinctions.
If the fault involves:
graphics
Wi-Fi
Bluetooth
audio
storage
webcam
printer
the problem may be a driver update, not the cumulative Windows package.
Open:
Device Manager
Find the affected device.
Then:
Properties > Driver
Record the current driver version.
If available, choose:
Roll Back Driver
and restart.
Your existing article rightly separates driver rollback from cumulative-update removal.
If Roll Back Driver is unavailable, obtain the correct known-good driver from:
Windows Update
the computer manufacturer
the hardware manufacturer
Avoid generic driver-updater utilities.
Method 2: Windows Will Not Boot — Use WinRE
If the update leaves Windows unable to reach the desktop, use Windows Recovery Environment.
From the sign-in screen, hold Shift while choosing:
Power > Restart
Then select:
Troubleshoot > Advanced options > Uninstall Updates
Microsoft documents this recovery route for removing a recent Windows update when normal Windows access is unavailable.
You can choose the appropriate recent:
quality update
or:
feature update
depending on what changed.
A BitLocker-protected PC may request the recovery key.
Feature Update? Use “Go Back”
A feature upgrade is different from a monthly cumulative update.
For example:
Windows 11 24H2 → Windows 11 25H2
If Windows still starts, go to:
Settings > System > Recovery
and look for:
Go back
This option is available only for a limited period after upgrading and disappears if the required previous-version files have been removed.
A feature rollback can also reverse drivers, applications and settings changed after the upgrade, so back up current work before proceeding.
Don't Reach for DISM First
DISM can remove particular Windows servicing packages, but this should be an advanced administrative option, not the normal way to uninstall an update.
Your existing article currently includes commands such as:
DISM /Online /Get-Packages /Format:Table
and package removal with:
DISM /Online /Remove-Package /PackageName:<package-name>
I would keep this information only as a short advanced note.
Use DISM for package removal only when:
Microsoft's specific release documentation supports it
you have positively identified the complete package name
the normal uninstall route is unavailable
you have a recovery plan
Removing the wrong servicing package can damage future Windows updating or startup.
What If Removing the Update Isn't Possible?
If Windows refuses to remove it, don't start hacking servicing manifests.
Better options include:
install a newer corrective update
roll back the affected driver
repair the affected application
use System Restore
repair Windows itself
Because Windows quality updates are cumulative, a later cumulative update can often replace the troublesome package while restoring current security fixes.
Consider System Restore
If the fault started after a combination of:
Windows update
driver change
application installation
configuration change
System Restore may be useful.
Search for:
Create a restore point
then open:
System Restore
and select a restore point from before the problem began.
System Restore is broader than uninstalling one KB because it can reverse several system-level changes at once.
Repair Windows Instead of Removing the Update
Sometimes the update isn't actually defective.
It may simply expose Windows corruption that was already present.
Windows 11 provides:
Settings > System > Recovery > Fix problems using Windows Update > Reinstall now
Microsoft says this reinstalls the current version of Windows while preserving applications, personal files and settings.
That can be a much better solution when:
update removal did not fix the issue
Windows servicing is damaged
updates repeatedly fail
the package cannot be removed
Pause Updates Only Temporarily
After removing an update, Windows may attempt to install it again.
You can temporarily use:
Settings > Windows Update > Pause updates
while you:
confirm the diagnosis
install a corrected driver
wait for a superseding update
obtain a vendor fix
But don't leave security updating paused indefinitely.
The long-term fix should restore the PC to a current supported servicing state.
If Removing the Update Does Not Fix the Problem
That is valuable evidence.
The update may simply have been blamed because of timing.
Investigate:
device drivers
BIOS/firmware
application updates
endpoint security
storage
memory
user-profile corruption
VPN/networking
hardware failure
If the fault remains, reinstalling the latest cumulative update may actually be safer because it restores the security fixes you removed.
Business PCs Need a Different Approach
A managed business computer may receive Windows updates through systems such as:
Microsoft Intune
Windows Autopatch
Configuration Manager
WSUS
Group Policy
RMM software
Removing an update locally may therefore only be temporary.
The management system might:
reinstall it
report the device non-compliant
enforce another installation deadline
Your current article already makes this point well.
For widespread problems, IT should first establish:
which models are affected
whether the issue is reproducible
whether Microsoft has acknowledged it
whether deployment should be paused centrally
whether a replacement update exists
what security risk removal creates
If 60 identical laptops fail after the same update, don't manually uninstall it from 60 machines and hope for the best.
Treat it as a deployment issue.
The Quick Decision Tree
Use this:
Windows still starts + cumulative update suspected
→ Update history > Uninstall updates
Hardware stopped working after a driver update
→ Device Manager > Roll Back Driver
Windows will not start
→ WinRE > Uninstall Updates
Recent Windows feature-version upgrade
→ Settings > System > Recovery > Go back
Update cannot be removed
→ Check newer fix / System Restore / Windows repair reinstall
Business-wide problem
→ Pause or remediate deployment centrally
That is the useful core of the article.
What Not to Do
Avoid:
removing several updates simultaneously
deleting Windows servicing files
forcing permanent packages to uninstall
assuming every Update History entry can be removed
disabling security updates indefinitely
resetting Windows immediately
manually installing an obsolete cumulative package that has already been superseded
Change one thing at a time and keep enough evidence to know whether it worked.
How Hamilton Group Can Help
Removing a Windows update is usually straightforward.
Knowing whether you should remove it is the harder part.
Hamilton Group can help with:
Windows 11 update problems
identifying problem KB updates
Windows Update rollback
driver rollback
Windows Recovery Environment
Microsoft Intune
Windows Autopatch
update rings
BitLocker recovery
Windows repair
business patch management
For business environments, we can also determine whether a problem is isolated or affecting a wider device group and manage the response centrally rather than manually repairing computers one at a time.
Visit hgmssp.com or call 0330 043 0069 to speak with Hamilton Group.