Windows 11 Running Slow After an Update? What to Try
The timing makes it feel obvious — the update finished, and now everything crawls. But the update itself is rarely the actual cause. More often it's a wave of background tasks the update triggers, all competing for the same CPU and disk resources at once, or a driver that got swapped out in the process. Here's how to tell whether you're looking at something temporary or something worth actually fixing, and what to do for each — starting with the step most people skip past too quickly.
Most post-update sluggishness is background maintenance racing to finish, not a sign anything actually broke.
Restart, Then Genuinely Wait a Few Hours
This sounds almost too simple, but a full restart — not just closing the lid or letting the PC sleep — is the single most effective first step. Updates sometimes leave background installation processes mid-flight, and a proper shutdown-and-restart gives Windows a clean slate to finish whatever it was doing.
After restarting, give it a genuine window of a few hours before assuming something's actually wrong. Immediately following a major update, Windows runs file indexing, a full Windows Defender scan, SSD optimization passes, and sometimes .NET framework recompilation, all in the background. These tasks are legitimately resource-heavy and can make everything else feel sluggish until they finish — usually within two or three hours on a modern machine, though it can stretch longer on older or slower hardware.
Check What's Actually Using Resources
Task Manager quickly tells you whether the problem is a background process still finishing up, or something that's actually stuck.
If the slowdown persists past that window, open Task Manager (Ctrl+Shift+Esc) and check the Processes tab, sorted by CPU or Disk usage. If a specific process — Windows Defender's scan service, the Search Indexer, or a Delivery Optimization service — is pinned near 100%, that confirms background work is still the cause, and it's worth letting it finish rather than force-stopping it, which can leave things in a worse, half-finished state.
If nothing obvious is using heavy resources and it's still slow regardless, that's a stronger signal something else is going on — most commonly a driver issue, which the update can trigger without you realizing it.
Check Your Graphics and Chipset Drivers
Windows updates occasionally replace a manufacturer's optimized driver — particularly graphics drivers — with a generic Microsoft one as part of the update process. This can noticeably tank performance, especially for anything graphics-heavy, even though the rest of the system runs fine.
Open Device Manager, expand Display adapters, and check for a yellow warning icon next to your graphics card. Even without a warning icon, it's worth visiting your graphics card manufacturer's site directly (NVIDIA, AMD, or Intel) and reinstalling the latest driver manually, since Windows' automatic driver selection doesn't always pick the best-performing option after a major update.
| Symptom | Likely Cause | What to Check |
|---|---|---|
| Slow for a few hours, then fine | Background update maintenance | Nothing — let it finish |
| Graphics-heavy tasks feel worse than before | Generic driver replaced optimized one | Device Manager, manufacturer's driver page |
| Everything is uniformly slow, no clear pattern | Startup apps re-enabled by the update | Task Manager > Startup apps tab |
| Storage warnings appeared alongside slowness | Update rollback data filling the drive | Settings > Storage > Temporary files |
Startup Apps the Update Quietly Re-Enabled
Feature updates sometimes reset a handful of settings to their defaults, including which apps are allowed to launch automatically at startup. If you'd previously trimmed your startup list and performance felt fine before the update, it's worth checking Settings > Apps > Startup again — an app or two you'd disabled may have quietly turned back on, adding to what's competing for resources every time you boot.
When to Actually Consider Rolling Back
- A full restart, followed by a few hours of patience
- Checking Task Manager for what's actually using resources
- Reinstalling graphics and chipset drivers from the manufacturer directly
- Reviewing the Startup apps list for anything re-enabled
- Roll back via Settings > System > Recovery (available for 10 days post-update)
- Run System File Checker (
sfc /scannow) to repair corrupted files - Check Windows Update's release health dashboard for known issues with that specific update
Running System File Checker and DISM
If drivers check out fine and startup apps aren't the issue, a corrupted system file from an interrupted or imperfect update install can also cause broad slowness. Windows has two built-in repair tools for exactly this. Open Command Prompt as administrator and run sfc /scannow first — this scans protected system files and automatically repairs any it finds damaged, which can take 10-15 minutes.
If SFC reports it found corruption it couldn't fix, follow up with DISM /Online /Cleanup-Image /RestoreHealth, which repairs the underlying system image SFC draws its healthy files from — this one needs an internet connection since it may download replacement files directly from Microsoft. Run SFC again afterward to confirm the fix stuck. Both commands are safe, official Microsoft tools that don't touch personal files — they exist specifically to catch problems standard troubleshooting misses.
Check If Others Are Seeing the Same Thing
Before deciding a slowdown is unique to your machine, it's worth a quick search for your specific update's KB number alongside "slow" or "performance" — widespread issues tied to a specific update get documented quickly, and Microsoft's own release health dashboard tracks known problems along with expected fix timelines. If it turns out to be a known, widely reported issue, the fix is often just waiting for Microsoft's follow-up patch rather than troubleshooting something that isn't actually specific to your setup.
Antivirus Scans Triggered by the Update
It's also worth knowing that a major update can trigger a full, rather than quick, scan from Windows Defender or a third-party antivirus product as part of its post-install verification. A full scan reads every file on the drive and is meaningfully more resource-intensive than the routine background scans you're used to. Check Windows Security > Virus & threat protection to see if a scan is currently running — if so, that alone can explain slowness that has nothing to do with drivers, startup apps, or corrupted files, and simply needs time to finish.
Frequently Asked Questions
How long does Windows 11 stay slow after an update?
Typically a few hours, sometimes up to a full day on older or slower hardware. Windows runs background tasks like file indexing, security scans, and driver reconfiguration right after a major update, and these compete for CPU and disk resources until they finish. If it's still slow after 24 hours and a full restart, it's worth troubleshooting rather than waiting further.
Should I roll back an update that made my PC slow?
Only if you've already tried restarting, waiting out background tasks, and checking for driver updates, and the slowdown persists beyond a day or two. Rolling back is available for 10 days after a feature update through Settings > System > Recovery, but it should be a later step, not the first response, since most post-update slowness resolves on its own.
Can outdated drivers cause slowness after a Windows update?
Yes, this is one of the more common causes. A Windows update can replace a manufacturer's optimized graphics or chipset driver with a generic Microsoft one, which can noticeably hurt performance, especially graphics-heavy tasks. Checking Device Manager for driver issues and reinstalling drivers from the manufacturer's site directly often resolves this.
More Windows Guides, Written Clearly
Browse our full library of software and troubleshooting explainers, updated as Windows changes.
More from the creator
Explore two other projects from the same creator.