How to Uninstall a Windows 11 Update Safely

A Windows update broke something. Here is how to remove it without making things worse, and when you should leave it alone.

A monthly Windows update lands and something stops working: a printer, a VPN, a headset. Uninstalling the update is a real option, but it is a blunt one. This guide covers the methods in order of safety, plus the cases where Microsoft has a better fix than removal.

If several USB headsets in your office died at once after the September update, that is a known Windows problem. Do not buy new headsets yet. Details are in the example section below.

Before You Uninstall

Removing a security update reopens every vulnerability it patched. Monthly Windows updates are cumulative, so pulling the latest one can also roll back fixes from earlier months. Treat removal as temporary, and plan to reinstall once Microsoft ships a fix.

Check Windows release health first. Microsoft lists known issues for each Windows version, with status and workarounds. If your problem is listed, the entry tells you whether removing the update is even needed. Our October 2026 Patch Tuesday breakdown covers the open issues for this month.

Write down the KB number and confirm the problem started after it installed. A device that broke before the update will not be fixed by removing it.

Method 1: Uninstall From Settings

This is the safest route for a single PC that still boots. Open Settings, select Windows Update, then Update history. Scroll to Related settings and select Uninstall updates. Find the KB number, select Uninstall, and restart when prompted.

If the latest cumulative update is missing from that list or the Uninstall button fails, move to the DISM method.

Method 2: Check for a Known Issue Rollback

Known Issue Rollback is Microsoft’s own way to undo a single bad change without removing the whole update. Microsoft describes it this way: a KIR rolls back a specific change that was applied as part of a nonsecurity Windows Update release, and all other changes from that release remain intact.

For home and unmanaged business PCs, Microsoft pushes the rollback itself, so a restart may be all you need. For domain-joined devices, Microsoft publishes a Group Policy .msi for each rollback that your IT admin deploys. KIRs only cover nonsecurity changes, so they will not help with every issue. When release health lists a KIR for your problem, use it and leave the update installed.

Method 3: Remove the Update With DISM

Windows 11 cumulative updates ship as one package containing the servicing stack update and the latest cumulative update. That combination is why the old command fails. In its note titled “If you want to remove the LCU,” Microsoft says:

“Running Windows Update Standalone Installer (wusa.exe) with the /uninstall switch on the combined package will not work because the combined package contains the SSU. You cannot remove the SSU from the system after installation.”

Microsoft’s instruction is to use DISM /Remove-Package with the LCU package name. Open Command Prompt as administrator and list the installed packages. The cumulative update shows up as a RollupFix package, with the build number in its name:

DISM /Online /Get-Packages /Format:Table | findstr RollupFix

REM Copy the full package identity from the output, then:
DISM /Online /Remove-Package /PackageName:Package_for_RollupFix~31bf3856ad364e35~amd64~~26100.9445.1.0

The package name above is an example. Use the exact name from your own output, matching the build in the KB article, then restart. Check the result with winver. The servicing stack part stays behind, since Microsoft says it cannot be removed.

Method 4: Use Windows Recovery When the PC Will Not Boot

If the update leaves Windows stuck in a boot loop, Windows Recovery Environment starts on its own after repeated failed boots. Choose Troubleshoot, then Advanced options, then Uninstall Updates. Microsoft describes that option as a way to uninstall recently installed updates. Monthly cumulative updates are quality updates, so pick the quality update option.

If BitLocker is on, have the recovery key ready before you start. We walked through a real boot loop in our guide to fixing UNMOUNTABLE_BOOT_VOLUME after KB5074109.

Example: USB Audio Code 10

After the September 8, 2026 security update, some USB Audio Class 1.0 devices stopped working. Device Manager shows This device cannot start (Code 10). Other symptoms Microsoft lists are no audio output, volume controls stuck at zero, and sound settings that do not respond. Older USB headsets, speakers and audio interfaces are the usual suspects.

On Windows 11 24H2 and 25H2, release health names KB5124008 as the originating update, builds 26100.9445 and 26200.9445. The 26H2 page lists the same issue. On Windows 10 22H2 it came with KB5122878, which only reaches devices enrolled in Extended Security Updates.

The status is partly fixed. The September 14 out-of-band update, KB5129195, fixed devices that failed only in 8-channel or 3D audio modes. Microsoft’s entry adds that some customers reported restoring audio in those cases by switching to 2-channel mode. That is a customer report, not an official workaround. The other symptoms are still open. Release health marks the issue Mitigated and says Microsoft is working on the rest. For an immediate workaround, Microsoft tells IT admins to contact Microsoft Support for Business.

Uninstalling is a poor trade here. Every later cumulative update carries the same change, so the device would have to drop both the September and October security fixes. Use a different headset model for now, open a ticket through Support for Business, and watch the release health entry.

Stop It Reinstalling

Windows Update will offer the same update again on its next scan. On a single PC, open Settings, select Windows Update, and use Pause updates. Microsoft lets you pick an end date up to 35 days out and extend it. When the pause ends, Windows installs the latest updates, which should include the fix by then.

Managed devices should not rely on the Settings toggle. Use an Intune update ring to pause quality updates, or decline the update in WSUS. If WSUS clients act strangely after cleanup, see our guide to resetting the WSUS client ID.

Once Microsoft marks the issue resolved, resume updates and confirm the PC is current. A paused machine stays exposed to every vulnerability the skipped update fixed.