How to Uninstall KB5132057 on Windows 11 (Full Step-by-Step Guide)
A complete walkthrough for removing the November 2026 preview update through Settings, Command Prompt, or System Restore — plus what to do if the uninstall option has already disappeared.
Quick Answer
Open Settings > Windows Update > Update history > Uninstall updates, select KB5132057, click Uninstall twice, then restart. This works for roughly ten days after the update installed. Once that window closes, Command Prompt with wusa /uninstall /kb:5132057 becomes the fallback, covered further down this guide.
KB5132057 arrived on November 19, 2026, as an optional, non-security preview for Windows 11 versions 25H2 and 26H2. It is not forced onto a machine the way a monthly security patch is. A person has to go looking for it under Optional updates, which is precisely why removing it later tends to be simpler than removing a cumulative security rollup. Still, a redesigned search experience and a new Run dialog touch two tools that people use dozens of times a day, and not everyone wants that change mid-week. Below is every method that actually works, in the order Microsoft itself recommends trying them.
| Detail | What Microsoft Lists |
|---|---|
| Update type | Optional, non-security preview |
| Release date | November 19, 2026 |
| Affected versions | Windows 11 25H2 and 26H2 (24H2 is excluded; 26H1 devices get a separate package, KB5132265) |
| Build after install | 26200.10075 (25H2) / 26300.10075 (26H2) |
| Servicing stack update | KB5132056 |
| Documented known issue | SQL Server linked-server connections may stay open (server-side only, not consumer PCs) |
Why Someone Would Want to Remove KB5132057
The most frequent reason is simple unfamiliarity. Windows Search now returns results in one merged list instead of separate categories, and it can complete small tasks, such as toggling dark mode or muting audio, without opening Settings at all. On a test 25H2 machine, that change appeared within a few hours of restarting, not instantly, because Microsoft ships it through a gradual rollout. A smaller group of people run into the new Run dialog and find it unfamiliar, since the classic box no longer has a Browse button once the modern version is switched on. Neither of these is a bug; both are deliberate redesigns, and either can be reversed without a full uninstall, which the next section explains.
A second, narrower reason involves the documented known issue. Microsoft states that SQL Server linked-server queries using OLE DB providers, Oracle and PostgreSQL among them, can leave external database connections open after a query finishes, gradually using up server resources. This affects server administrators far more than home users, and Microsoft already offers a mitigation through business support channels rather than requiring removal. Someone running SQL Server on a personal workstation, however, might reasonably choose to uninstall until a permanent fix ships.
A third reason is simply caution. Any update that touches search indexing, sign-in behavior, and Explorer at the same time carries a nonzero chance of friction with specific hardware or third-party software, even when Microsoft’s own testing finds nothing wrong. If a PC behaved differently right after this update landed, removing it is a reasonable first diagnostic step, assuming a quick build check confirms the timing.
Before Uninstalling: Two Checks Worth Doing First
Confirm the update is actually installed before removing it. Press Windows key + R, type winver, and press Enter. A 25H2 machine should read build 26200.10075, while a 26H2 machine should read 26300.10075. If the number is lower, KB5132057 was never applied, and whatever problem is occurring has a different cause.
If the complaint is only about the new Run dialog or the redesigned Search, a full uninstall is not required. The modern Run dialog is off until someone switches it on manually, under Settings > System > Advanced, so turning that same toggle back off restores the classic box immediately. The new Search experience is tied to a server-side rollout rather than a strict on/off switch, and it has not reached every eligible device at the same time regardless of build number, so a person who dislikes it may simply not have it yet, or may see it change again as Microsoft adjusts the rollout.
How to Uninstall KB5132057 From Settings
This is the method Microsoft documents directly, and it is the one most people will use successfully. The steps below match what actually appears on-screen on a current 25H2 build.
- Open the Start menu and click Settings.
- Select Windows Update from the left-hand menu.
- Click Update history.
- Scroll to the bottom and select Uninstall updates.
- Find KB5132057 in the list and click Uninstall beside it.
- Confirm by clicking Uninstall again in the dialog that appears.
- Wait for removal to finish. Do not turn off the PC during this step.
- Restart when prompted, then check
winverto confirm the build number dropped back.
One detail that often causes confusion is a second restart. Because KB5132057 includes a Secure Boot certificate step on some devices, Windows may ask for an additional reboot during the uninstall, not just one. That is expected behavior rather than a stalled process, so letting it finish is the correct response, even when it looks like the PC restarted twice for what seemed like a single update.
Related Walkthrough: Uninstalling KB5132057 (Video)
Video credit: TechFixIt. The process shown applies to any Windows 11 KB number, including KB5132057, since the Settings path does not change between updates.
A problem some readers raise is not finding KB5132057 in the list at all, even though winver confirms the build is current. That usually means the ten-day rollback window has already closed, whether through normal time passing or because Disk Cleanup’s “Windows Update Cleanup” option ran and removed the files needed for reversal. The next two sections cover what remains possible at that point.
Uninstalling With Command Prompt
Command Prompt reaches the same uninstall routine Settings uses, so it tends to succeed in the same window of roughly ten days, though some administrators find it responds slightly longer than the graphical option on managed devices. Open Command Prompt as administrator, then run:
wusa /uninstall /kb:5132057
Windows displays a confirmation dialog before removing anything, identical in substance to the one shown in Settings. A restart follows once the removal completes. If the command returns an error stating the package cannot be found, that is a reliable sign the rollback files have already been cleared, and Settings will show the same absence.
If KB5132057 No Longer Appears in Uninstall Updates
Windows keeps the previous system files needed for rollback for a limited period after a cumulative update installs. Once that period ends, or once a manual cleanup runs, the standard uninstall path is no longer available through either Settings or Command Prompt. At that stage, a System Restore point created before November 19, 2026, is the remaining consumer-level option, provided System Protection was already turned on for the drive. Open Control Panel > Recovery > Open System Restore and choose a restore point dated before the update. This rolls back more than just KB5132057, so it is a broader step than a targeted uninstall, and any software installed since that date will also be removed.
Beyond that point, removal generally requires DISM image servicing, which involves identifying the exact package name through DISM /Online /Get-Packages and removing it with DISM /Online /Remove-Package. This method carries real risk of leaving a system in an inconsistent state if the wrong package is targeted, so it sits outside what most home users should attempt alone. If a managed or business device reaches this stage, involving IT support or Microsoft’s own support channels is the safer route rather than experimenting with image servicing commands on a production machine.
Stopping Windows From Reinstalling It
Because KB5132057 is optional rather than a mandatory security patch, Windows does not reinstall it automatically after a manual uninstall, unlike monthly cumulative security updates, which Microsoft does reoffer. Simply avoiding the Optional updates list under Settings > Windows Update > Advanced options > Optional updates keeps it away. For additional reassurance, pausing updates for up to five weeks through the same Windows Update page prevents any update, optional or otherwise, from installing during that period.
| Method | Works When | Risk Level |
|---|---|---|
| Settings > Uninstall updates | Within about 10 days of install | Low |
Command Prompt (wusa) | Same window as above, including on some managed devices | Low |
| System Restore | After the uninstall window has closed, if System Protection was on | Medium (reverts other changes too) |
| DISM image servicing | Last resort, advanced users or IT staff only | High |
If Removing the Update Does Not Solve the Problem
Sometimes an issue that appeared alongside KB5132057 turns out to be unrelated, and uninstalling simply confirms that rather than fixing anything. If a device still has an external hard drive that will not appear in Disk Management, or if a wireless peripheral started lagging around the same time, driver conflicts are a more likely cause than the update itself; a guide on wireless mouse lag on Windows 11 covers that separately. USB-specific symptoms, including devices that stop being recognized entirely, are worth checking against a dedicated article on USB device not recognized errors, since the fix there does not require touching Windows Update at all. A related but distinct error, USB device descriptor request failed, has its own troubleshooting path as well.
If a system becomes unresponsive rather than merely glitchy, restarting through the normal method may not be possible; steps for that situation are covered in a guide on how to unfreeze a laptop screen. Bluetooth audio that starts cutting out after any Windows update, KB5132057 included, generally traces back to driver timing rather than the update package, and a separate walkthrough addresses Bluetooth audio stuttering on Windows directly. Sign-in trouble following an update, including a forgotten or locked administrator account, is covered in a guide on resetting a Windows 11 admin password. A different and fairly common Windows Update complaint, unrelated to KB5132057 specifically, is documented in a piece on fixing Windows Update error 0x80070002.
When none of the above applies and a machine keeps crashing, fails to boot normally, or shows corruption after the uninstall itself, that is the point to involve a professional rather than continuing to experiment. A local repair technician, the PC manufacturer’s support line, or Microsoft’s own support channel can run diagnostics that go beyond what Settings or Command Prompt expose, and attempting advanced image repairs without that background risks making a recoverable problem permanent.
FAQ
What does KB5132057 actually change?
It redesigns Windows Search into a single results list with inline actions, introduces an optional modern Run dialog, adds a screen-brightness assist to Windows Hello facial recognition, and fixes a set of smaller bugs, including a false “someone else is using this PC” warning at restart.
Is KB5132057 mandatory?
No. It is an optional preview update. A device only receives it if Optional updates are checked manually under Windows Update.
Will uninstalling remove the new Run dialog and Search permanently?
Uninstalling removes the update package and reverts related files, so both features go away. The modern Run dialog can also be turned off individually through its own toggle, without removing the whole update.
Can I stop Windows from offering it again after uninstalling?
Yes. Since it is optional, Windows will not reinstall it automatically. Leaving it unchecked under Optional updates, or pausing updates for a few weeks, keeps it from returning.
Is there a known issue I should worry about?
Microsoft documents one, affecting SQL Server linked-server connections on business servers. It does not affect typical home desktop or laptop use.
How long do I have before the easy uninstall option disappears?
Generally around ten days, though running Disk Cleanup’s “Windows Update Cleanup” option sooner can remove the rollback files earlier than that.
Conclusion
KB5132057 is reversible through the same Settings path Microsoft provides for any recent cumulative update, and for most people that single method, Settings followed by one restart, solves the problem without needing Command Prompt or System Restore at all. The update’s own non-security, optional status also means a removed package will not quietly reappear later, which is not something every Windows update can promise. If a decision has to be made quickly, trying the Settings route first, then Command Prompt if the option has vanished, covers the overwhelming majority of real situations, with System Restore and professional support remaining available for anything that falls outside that pattern.