Windows 11 Slow After an Update? How to Fix It

The update installed overnight, the machine rebooted, and now everything takes a beat longer than it should. Explorer windows hesitate, the Start menu pauses before drawing, and Task Manager shows disk sitting near 100% with nothing obviously running.

Most of the time this resolves on its own within a few hours. Windows does a substantial amount of catch-up work after an update, and it is front-loaded into exactly the period when you have just sat down and are paying attention.

But not always. Some updates ship a driver that does not suit your hardware, or re-enable a startup item you had disabled. This guide separates the two cases. If your machine has been generally slow for months rather than since Tuesday, the broader diagnosis is in why is Windows 11 so slow — this guide is specifically about a change you can date to an update.

Step one: wait, and know what you are waiting for

After a significant update Windows runs several jobs back to back. Each is legitimate and each is heavy.

Open Task Manager (Ctrl+Shift+Esc), go to the Details tab, and look for SearchIndexer.exe, TiWorker.exe, MoUsoCoreWorker.exe or Defrag.exe consuming the resources. If those are the top consumers, the machine is doing expected post-update work and the answer is to leave it plugged in and running for a couple of hours.

On a mechanical hard drive this can realistically take most of a day. On an SSD it should be done well inside three hours.

Step two: check what changed at startup

Updates sometimes re-enable startup entries, and a feature update can reinstall manufacturer software you had removed.

Task Manager → Startup apps. Sort by Startup impact and look at anything marked High. The usual suspects are updater services, cloud sync clients, manufacturer “assistant” utilities and gaming overlays.

Disable what you do not need. Right-click → Disable. Nothing here is dangerous to turn off — these entries only control whether something launches at boot, not whether it is installed.

Reboot and reassess. If the login-to-usable time improved, that was it. More detail on this specific symptom is in fix slow Windows 11 startup.

Step three: drivers, which is the usual real cause

When a genuine post-update slowdown persists, a driver is the most likely explanation. Windows Update ships generic drivers that are stable across a huge range of hardware but are not always the right ones for a specific laptop, and it will happily replace a manufacturer driver with its own.

Reinstall the three that matter most, in this order:

1. Graphics. Download directly from NVIDIA, AMD or Intel. For NVIDIA and AMD, choose the clean-install option in the installer so it removes the previous driver’s settings rather than layering on top.
2. Chipset. From your laptop or motherboard manufacturer’s support page, not from Intel or AMD generically. Chipset drivers govern power management and storage controllers, and the wrong one produces exactly the kind of vague sluggishness being described here.
3. Storage. The AHCI, NVMe or RST driver, again from the manufacturer. A mismatched storage driver is a classic cause of high disk usage after an update.

Avoid Device Manager → Update driver for this. It checks Windows Update, which is the source of the driver you are trying to replace, and will usually report that the best driver is already installed.

If a specific device is at fault, you can roll back just that one: Device Manager, right-click the device, Properties → Driver → Roll Back Driver. The button is greyed out if no previous version was retained.

Step four: check the disk and CPU honestly

If something is still pinning a resource, find out what. Open Task Manager → Performance, then click Open Resource Monitor at the bottom for a per-file breakdown of disk activity.

A few patterns and what they mean:

• MsMpEng.exe high — Windows Defender is running a post-update full scan. Expected once; see Antimalware Service Executable using high CPU if it never stops.
• Disk pinned at 100% on a mechanical drive — common and usually indexing, but it can indicate a failing drive. Covered in 100% disk usage in Task Manager.
• System process with high disk — frequently a storage driver mismatch. Go back to step three.

For a general approach to reading these numbers, see find what is using 100% CPU or disk.

Step five: repair the system files

An interrupted or partially applied update can leave component corruption that produces persistent odd behaviour. Two commands fix most of it. Open Terminal (Admin) and run them in this order:

DISM /Online /Cleanup-Image /RestoreHealth

sfc /scannow

DISM repairs the component store using Windows Update as a source; sfc then uses that repaired store to fix protected system files. Running sfc first is less effective, because it may be repairing from an already-damaged source.

Together they take 15–30 minutes. Neither touches your files or installed programs. Reboot afterwards.

Step six: remove the update

If you have ruled out background work, startup items and drivers, and the slowdown still dates precisely to one update, remove it.

For a quality update (monthly patch, KB number)

1. Settings → Windows Update → Update history.
2. Scroll to the bottom and click Uninstall updates.
3. Find the update by its KB number and install date, click Uninstall.

Not every update can be removed this way. Servicing stack updates in particular are permanent.

Immediately afterwards, pause updates under Settings → Windows Update → Pause updates for one or two weeks. Otherwise Windows reinstalls the same update, often within a day.

For a feature update (version change, e.g. 23H2 to 24H2)

1. Settings → System → Recovery.
2. Click Go back, and follow the prompts.

This is only available for 10 days after the update, and only if the Windows.old folder still exists — so if you cleaned it up to free disk space, this route is gone. See can you safely delete Windows.old.

Before rolling back: the process restores the previous Windows version and can remove applications installed since the update. Your personal files are kept, but back up anything important first. The rollback itself takes 20–60 minutes with several reboots — do not interrupt it.

System Restore as an alternative

If the update is older than ten days and uninstalling is not offered, a restore point from before it may still exist. Win+R → rstrui.exe, pick a point dated before the update. This reverts system files, drivers and registry settings while leaving documents alone. It does remove programs installed after that date.

What not to do

• Do not disable Windows Update permanently. You lose security patches, and the specific update causing trouble is usually revised within weeks. Pause it instead.
• Do not disable Windows Defender to reduce CPU during the post-update scan. The scan ends on its own. Running without protection does not.
• Do not run a registry cleaner after an update. Nothing it does addresses any of the causes above, and it is capable of breaking a working installation.
• Do not reinstall Windows as the first move. Driver reinstallation and a startup audit resolve the large majority of post-update slowdowns in under an hour.
• Do not disable the search indexer permanently to stop the disk activity. You will be waiting on every search instead. Let it finish once.
• Do not interrupt a rollback or a DISM repair. A half-finished operation is considerably worse than the problem you started with.

What to expect

In most cases the answer is simply time — a few hours on an SSD, longer on a hard drive — and the machine returns to its previous speed without intervention.

Where it does not, a clean reinstall of graphics and chipset drivers fixes the majority of the remainder. Uninstalling the update is a real option but a last one, because it is temporary by nature; the same update will arrive again.

If the machine was slow before the update as well and you have been blaming the update, the broader checklist in why is Windows 11 so slow is the better place to start.