How to Uninstall a Problematic Windows Update Manually (Windows 11/10)

uninstall problematic windows update manually

If you want to uninstall a problematic Windows update manually, you’re probably here because something broke right after an update installed — your laptop freezes every few minutes, the taskbar stops responding, or it won’t even get past the boot screen anymore. If this happened right after an update, you’re not imagining things—Microsoft ships patches to over a billion devices, and every few months, one of them causes more problems than it fixes.

The good news is you don’t have to wait for Microsoft to push a fix. You can manually uninstall the update yourself and get your system back to where it was working fine. This guide covers every practical way to do that on both Windows 11 and Windows 10 — including what to do when your PC won’t even boot into the desktop.

Before You Uninstall Anything {#before-you-uninstall-anything}

A few minutes of prep can save you a much bigger headache later.

  • Write down the KB number. Every Windows update has one (like KB5044384). You’ll need it for the command-line methods, and it helps you confirm you’re removing the right one.
  • Create a restore point if you can. If Windows still boots, go to Settings > System > Recovery, or search “Create a restore point” in the Start menu. This gives you a fallback if the uninstall itself causes problems.
  • Check Microsoft’s release notes first. Search the KB number plus “known issues” — sometimes Microsoft has already shipped a fix, and reinstalling a newer patch is quicker than uninstalling.
  • Pause updates before you remove anything. Go to Settings > Windows Update > Pause updates. Otherwise Windows may silently reinstall the exact update you just removed.

With that out of the way, here are the methods, roughly in order of how likely they are to work without a fight.

Method 1: Uninstall via Windows Settings {#method-1-settings}

This is the path most people should try first.

  1. Open Settings with Windows key + I.
  2. Click Windows Update (Windows 11) or Update & Security > Windows Update (Windows 10).
  3. Click Update history, then scroll down to Uninstall updates.
  4. Look for the update by date — the one installed right before your problems started — and select Uninstall.
  5. Confirm, then restart when prompted.

This works for most quality updates and optional updates, but not for every type — some feature updates and driver packages don’t show up here at all.

Method 2: Uninstall via Control Panel {#method-2-control-panel}

If Settings feels sluggish or the update doesn’t show up there, Control Panel sometimes lists it anyway.

  1. Press Windows key + R, type appwiz.cpl, and hit Enter.
  2. Click View installed updates in the left sidebar.
  3. Find the entry, click Uninstall, confirm, and restart.

It’s essentially the same database as settings, so if one doesn’t show the update, the other often won’t either — but it’s worth the 30 seconds to check.

Method 3: Uninstall via Command Prompt (WUSA) {#method-3-wusa}

When you already know the KB number and want to skip the UI entirely, WUSA (Windows Update Standalone Installer) gets it done in one line.

  1. Search for Command Prompt, right-click it, and choose Run as administrator.
  2. Type the following, replacing the number with your actual KB number (drop the “KB” prefix):
wusa /uninstall /kb:5044384
  1. Confirm the prompt and restart your PC.

This is the fastest option once you have the KB number in hand, but it fails silently on combined servicing stack and cumulative update packages—more on that below.

Method 4: Uninstall via PowerShell {#method-4-powershell}

Not sure which update to target? PowerShell can list your recent updates before you remove anything.

  1. Open PowerShell as Administrator.
  2. Run this to see what’s installed and when:
Get-HotFix | Select-Object HotFixID, InstalledOn, Description | Sort-Object InstalledOn -Descending
  1. Once you’ve spotted the KB number, you can uninstall it directly from PowerShell too:
wusa /uninstall /kb:5044384 /quiet /norestart

This is handy if you’re troubleshooting on a machine where you don’t remember exactly what installed last.

Method 5: Uninstall When Windows Won’t Boot (WinRE) {#method-5-winre}

If the update left your PC stuck on a black screen, a boot loop, or an endless spinning logo, none of the above will help — you need the Windows Recovery Environment.

  1. Force a shutdown by holding the power button for 10 seconds.
  2. Turn the PC back on, and the moment you see the manufacturer or Windows logo, hold the power button again for 10 seconds to force another shutdown.
  3. Repeat this once more. After three interrupted boots, Windows automatically triggers automatic repair and drops you into WinRE.
  4. On the blue screen, go to Troubleshoot > Advanced options > Uninstall Updates.
  5. Pick either ‘Uninstall latest quality update‘ or ‘Uninstall latest feature update’, depending on which one you installed most recently.
  6. Follow the prompts, then let the PC restart normally.

This is the only reliable route when the desktop itself is unreachable, and it’s built specifically for this scenario — you’re not doing anything unsupported here.

Method 6: Force-Remove with DISM {#method-6-dism}

For the stubborn cases WUSA won’t touch, DISM works directly on the update package rather than going through the standard uninstaller.

  1. Open Command Prompt as Administrator.
  2. Find the exact package name:
dism /online /get-packages | findstr KB5044384
  1. Copy the full package identity from the output.
  2. Remove it:
dism /online /remove-package /packagename:Package_for_KB5044384~31bf3856ad364e35~amd64~~19041.5044384.1.9
  1. Let it finish, then restart.

This is a last-resort method — it’s more error-prone than the others, so only reach for it if Settings, Control Panel, and WUSA have all failed.

Update Won’t Uninstall? Try This {#update-wont-uninstall}

If every method above throws an error, a few specific culprits are usually behind it:

  • Windows Sandbox is enabled. It creates a base container image that can lock certain update files in place. Search “Turn Windows features on or off”, uncheck Windows Sandbox, restart, and try again.
  • The update was superseded. If a newer cumulative update replaced the one causing trouble, you may need to uninstall the newer one instead — Windows often rolls several fixes into one package.
  • It’s a combined SSU + LCU package. Microsoft frequently bundles Servicing Stack Updates with Cumulative Updates. The SSU portion is permanent by design once installed, so WUSA can fail on the whole package even though only the LCU part is causing your issue. DISM’s /remove-package can sometimes target just the LCU, but if it doesn’t, that particular update genuinely can’t be rolled back — you’re better off troubleshooting the underlying symptom instead (a driver, corrupted files, or a conflicting app) rather than fighting the update itself.

It’s also worth ruling out that the update is actually the cause. Run System File Checker, check Event Viewer for the exact error around the time of the crash, and test in Safe Mode—sometimes a driver conflict or a third-party app is the real trigger, and the update just happened to expose it.

FAQs {#faqs}

Can I uninstall a Windows update after 10 days? Windows keeps most quality updates uninstallable for 10 days after installation by default. After that window, the update files are typically cleaned up automatically, and Settings/Control Panel won’t show it anymore—DISM may still work if the package files are present, but it’s not guaranteed.

Does uninstalling a Windows update delete my files? No. Uninstalling an update only reverts system files back to their previous version — it doesn’t touch your personal documents, photos, or installed apps.

Will Windows just reinstall the update again? Yes, unless you pause updates first. Go to Settings > Windows Update > Pause updates before or immediately after uninstalling, so you have time to confirm the issue is actually fixed.

Is it safe to skip a security update permanently? Generally, no — security updates patch real vulnerabilities. If a security update is the one causing problems, keep an eye on Microsoft’s release notes for a follow-up fix and reinstall it as soon as one’s available.

Final Thoughts

Uninstalling a Windows update isn’t something you should reach for casually, but when a patch is genuinely breaking your system, you shouldn’t have to just wait it out either. Start with Settings or Control Panel for the easy cases, drop to WUSA or PowerShell once you know the KB number, and keep WinRE and DISM in your back pocket for when things get stubborn. Whichever method gets you there, the goal is the same: a stable PC today, and the option to reinstall the fix once Microsoft sorts it out.

Read More: Our Latest Blog

Leave a Reply

Your email address will not be published. Required fields are marked *

Back To Top Img