Windows updates are supposed to make your computer more secure and more stable. Most of the time, they do. But occasionally a patch introduces a new audio driver conflict, breaks a VPN client, or causes the system to hang on the login screen. When that happens, Windows gives you a few ways to undo the damage, and knowing which one to reach for first saves a lot of time.
How to tell if an update caused the problem
Before removing anything, confirm the update is actually the culprit. The clearest signal is timing: the problem appeared shortly after Windows installed an update and restarted. You can check your update history by opening Settings, going to Windows Update, and clicking Update history. The list shows every patch with the date it was applied. If a Quality Update or Driver Update landed on the same day your problem started, that's your likely candidate.
Device Manager is also worth checking if the fault is hardware-related. Right-click the Start button, open Device Manager, and look for any devices with a yellow warning triangle. A recently updated driver frequently shows up here.
Method 1: Uninstall through Windows Update history
This is the fastest route for recent updates. Open Settings > Windows Update > Update history, then scroll to the bottom and click Uninstall updates. Windows shows a list of recently installed updates. Find the one you want to remove, right-click it, and select Uninstall. The system will restart to complete the removal.
Not every update appears in this list. Microsoft removes some from the uninstall interface once they've been superseded by a later patch. If the update you want isn't listed, move to one of the methods below.
Method 2: Use the recovery option to go back
If a feature update (a full version upgrade, not just a monthly patch) caused the problem, Windows keeps a copy of the previous installation for a limited time. Go to Settings > System > Recovery and look for Go back under Recovery options. If the option is available, it means the previous version files are still on the drive. Click it, answer the brief questionnaire, and Windows restores the earlier build.
Microsoft keeps this rollback window open for 10 days after a feature update. After that, the previous installation files are automatically deleted to free up disk space. If you're outside that window, the Go back option will be greyed out.
Method 3: Roll back a driver through Device Manager
Driver updates are a common source of post-update problems, particularly for graphics cards, audio hardware, and network adapters. Device Manager handles driver rollbacks separately from the Windows Update interface.
Right-click the Start button and open Device Manager. Find the device that's misbehaving, right-click it, and choose Properties. Under the Driver tab, click Roll Back Driver. Windows reinstalls the previous driver version and prompts you to restart. If the button is greyed out, Windows doesn't have a previous driver stored and you'll need to download one manually from the manufacturer's site.
Method 4: Use System Restore
System Restore takes your Windows configuration back to an earlier snapshot called a restore point. It doesn't delete your personal files, but it does undo driver changes, registry edits, and software installs that happened after the restore point was created.
Search for Create a restore point in the Start menu, open it, and click System Restore. The wizard walks you through selecting a restore point, with dates shown so you can pick one from before the update landed. The process takes around 20 minutes and ends with a restart.
System Restore only works if it was enabled before the problem occurred. Many PCs have it turned off by default. If no restore points are listed, this option isn't available.
What to do if Windows won't boot at all
A broken update occasionally stops Windows from starting. When that happens, you can't reach Settings in the normal way. Instead, force the Advanced Startup Options menu by holding down the power button until the PC shuts off, then powering it back on. After 2 or 3 forced shutdowns, Windows automatically opens the recovery environment.
From there, choose Troubleshoot > Advanced options. You'll see options for System Restore, Startup Repair, and Uninstall Updates. The Uninstall Updates option in this menu covers both Quality Updates and Feature Updates as separate choices.
If the recovery environment itself won't load, you'll need a Windows 11 bootable USB drive to access it externally. Microsoft provides the Windows 11 Media Creation Tool on its official download page, which builds a bootable USB in a few clicks.
Preventing Windows from reinstalling the same update
Once you've removed a problematic update, Windows will often try to reinstall it at the next update cycle. Microsoft offers the Show or hide updates troubleshooter as a downloadable tool that lets you block specific updates from reinstalling. Use it immediately after the rollback, before the next automatic update check runs.
Keep in mind that blocking a security patch does carry risk. This is a short-term fix while you wait for Microsoft to release a corrected version, not a permanent configuration. If the blocked update contains a critical security fix, the exposure window matters. You can read more about how those risks stack up in our article on why keeping your software updated is important for security.
When to get help instead of doing it yourself
Most update rollbacks take under 30 minutes if Windows is still starting correctly. The process gets harder when the system won't boot, when recovery options are disabled, or when the rollback itself fails partway through. At that point, pushing further without experience risks corrupting the Windows installation entirely.
Common update-related failures, including crashes, broken drivers, and failed rollbacks, are well within the scope of what a technician can fix without touching your machine in person. For a full picture of what that kind of remote session looks like, see our guide on what to expect during a remote computer troubleshooting session.
If you're seeing a blue screen error code as part of the problem, the specific stop code usually identifies the failing component precisely. That's worth noting down before you do anything else, since it narrows the diagnosis considerably.