Windows 11 Slow After Update? 9 Fixes That Work
Short answer: Windows 11 slow after update is almost always caused by background housekeeping that finishes on its own, a driver Windows replaced during the install, or a corrupt update cache. Start with a proper restart (not shutdown), check Task Manager for post-update processes, then work through the fixes below. Most machines are running normally within 30–60 minutes.
Why Does Windows 11 Get Slow After an Update?
Updates don't just patch files—they can swap drivers, re-enable services you turned off, queue background indexing and Defender scans, and drop gigabytes of rollback data onto your drive. Any of those can hammer disk or CPU until the work finishes, or cause lasting slowdowns if something went wrong during the install. It's almost never permanent, and you rarely need to reinstall.
Fix 1: Do a Real Restart, Not a Shutdown
This trips up more people than it should. Windows 11 has Fast Startup enabled by default. When you click Shut Down, Windows saves the kernel state to hiberfil.sys and hibernates it—the kernel never fully reloads. Driver errors, memory accumulation, or partially applied update files carry straight over to the next boot. You can verify this: open Task Manager, go to Performance → CPU, and check Up time. On machines where people click "Shut Down" every night, that counter often reads weeks.
Use Restart specifically. It bypasses Fast Startup completely, reloads every driver from scratch, and finishes applying any patches that require a cold boot. After the update installs, hit Restart — not Shut Down — and let the machine sit for a few minutes before judging performance.
Fix 2: Wait Out the Post-Update Background Work
Immediately after a major update, Windows queues a stack of background tasks: search re-indexing, a full Defender scan, SSD optimization, and .NET assembly recompilation. On most machines this runs for one to two hours.
Open Task Manager (Ctrl+Shift+Esc) and sort the Processes tab by CPU or Disk. If any of these are burning resources, just wait — they will finish on their own:
TiWorker.exe/ Windows Modules Installer WorkerSearchIndexer.exeMsMpEng.exe(Antimalware Service Executable)svchost.exehostingDoSvc(Delivery Optimization)
I've wasted time troubleshooting what turned out to be a Defender scan that finished by itself. Don't start disabling services or rolling back drivers until this settles.
Fix 3: Check Whether a Driver Got Replaced
Updates sometimes swap your GPU, chipset, or NIC driver for a generic Microsoft version. A swapped GPU driver especially tanks graphics performance—windows drag, frame rates drop, and the whole desktop feels unresponsive even at idle.
Open Device Manager (Win+X → Device Manager). Look for yellow warning triangles, and check Display Adapters. If it shows "Microsoft Basic Display Adapter" instead of your actual card, the update clobbered your GPU driver.
To roll back: right-click the device → Properties → Driver tab → Roll Back Driver. If that button is greyed out, there's no stored previous version — download the driver directly from the manufacturer and install it manually. For GPU drivers specifically, always prefer the vendor's package over whatever Windows Update shipped.
Fix 4: Clear the Windows Update Cache
The SoftwareDistribution folder holds downloaded update files. If they're partially corrupt — which happens when an update is interrupted or hits a write error — Windows can keep grinding trying to use them. Renaming the folder forces a fresh download.
Open Command Prompt as Administrator and run these lines one at a time:
net stop wuauserv net stop bits net stop cryptSvc ren C:\Windows\SoftwareDistribution SoftwareDistribution.old ren C:\Windows\System32\catroot2 catroot2.old net start wuauserv net start bits net start cryptSvcRestart, then go to Settings → Windows Update → Check for updates. Windows re-downloads what it needs cleanly. After a week of stable updates, delete SoftwareDistribution.old to reclaim the space.
Fix 5: Run DISM, Then SFC
If the update itself was interrupted or partially applied, the Windows component store may be corrupt. sfc /scannow fixes individual system files but pulls from that component store — if the store itself is damaged, SFC reports it can't fix everything and gives up. DISM repairs the store first, then SFC can finish the job.
Run both in an elevated Command Prompt or Terminal, in this order:
DISM /Online /Cleanup-Image /RestoreHealthThis takes 10–20 minutes. It may appear stuck at 20% or 62% for a while — that's normal, don't close the window. Once it reports success:
sfc /scannowIf DISM returns "The source files could not be found," it can't reach Windows Update to fetch repair files. That's a deeper problem — try the other fixes first. Reboot after both commands finish.
Fix 6: Audit Startup Apps (Updates Re-Enable Them)
Updates reset startup settings more often than most people realize. An app you disabled months ago silently reappears in the boot sequence.
Go to Settings → Apps → Startup. Sort by "Startup impact" and disable anything you don't need immediately on boot — Teams, Spotify, Discord, OneDrive, browser apps, and OEM utilities are all common offenders. Six heavyweight apps fighting for disk I/O during the first two minutes of boot is a genuine performance problem, not just a minor inconvenience.
Fix 7: Adjust Visual Effects and Power Plan
Updates can silently revert visual effect settings and power plans. Search for "Adjust the appearance and performance of Windows" in the Start menu. On the Visual Effects tab, select Adjust for best performance to kill animations, or manually untick the ones that don't matter to you. I always keep "Smooth edges of screen fonts" and thumbnail previews — the rest on older hardware is mostly waste.
Also confirm your power plan. Go to Settings → System → Power & battery and set Power mode to Best performance. On a desktop where battery life is irrelevant, there's also a hidden Ultimate Performance plan:
powercfg -duplicatescheme e9a42b02-d5df-448d-aa00-03f14749eb61Run that in an elevated PowerShell, then open Control Panel → Power Options and select the new plan. Don't use this on a laptop — it disables all CPU throttling and will drain the battery and run hot.
Fix 8: Disable SysMain on SSD Systems
SysMain (the modern name for Superfetch) was designed in 2007 to preload apps into RAM on machines with slow spinning drives. On a modern NVMe SSD it's largely redundant and can cause aggressive RAM spikes and disk activity after waking from sleep or a reboot.
If you're seeing high disk or memory usage from "Service Host: SysMain" in Task Manager, try disabling it in an elevated PowerShell:
Stop-Service -Name "SysMain" Set-Service -Name "SysMain" -StartupType DisabledAlternatively, open services.msc, find SysMain, open Properties, stop it, and set Startup Type to Disabled. Reboot and watch Task Manager for 10 minutes. If disk and RAM behavior improves, leave it off. If there's no change, re-enable it — on low-RAM machines or HDD systems it may still help.
Fix 9: Reclaim Disk Space the Update Left Behind
Feature updates keep a "Previous Windows installation" folder as a rollback safety net. This alone can use 10–20 GB. If your system drive was already near capacity, Windows gets sluggish — it needs free space for virtual memory paging, temp files, and update staging.
Go to Settings → System → Storage → Temporary files. Check and delete:
- Windows Update Cleanup
- Delivery Optimization Files
- Previous Windows installation(s) — once you're confident the update is stable
- Temporary files
You can also run Disk Cleanup as administrator (search it in Start, right-click → Run as administrator) to unlock the full list of cleanup categories, including system files.
When to Just Roll Back the Update
If you've worked through all nine fixes and the system is still broken, Windows gives you 10 days from a feature update to revert cleanly: Settings → Windows Update → Update history → Uninstall updates. After that window closes, a repair install — running setup.exe from a matching Windows 11 ISO and choosing "Keep personal files and apps" — is the next step before a clean reinstall.
Symptom Quick-Reference
| Symptom | Likely Cause | Fix |
|---|---|---|
| Slow for 1–2 hours, then fine | Normal post-update indexing/scanning | Wait (Fix 2) |
| Sluggish graphics, low FPS | Generic GPU driver installed by update | Roll back or reinstall GPU driver (Fix 3) |
| High disk usage, update errors | Corrupt SoftwareDistribution cache | Clear cache (Fix 4) |
| SFC reports files it can't fix | Damaged component store | Run DISM then SFC (Fix 5) |
| Slow boot, familiar apps back at startup | Update reset startup settings | Audit startup apps (Fix 6) |
| RAM spikes, high disk right after boot | SysMain churning on SSD | Disable SysMain (Fix 8) |
| General sluggishness, low free disk | Update left temp/rollback files | Free disk space (Fix 9) |
Frequently Asked Questions
How long does Windows 11 stay slow after an update?
Background processes like indexing and Defender scans typically finish within 1–2 hours after a full restart. If the machine is still slow after that, it's not resolving on its own — work through the fixes above starting with driver and cache checks.
Does uninstalling a Windows update fix slow performance?
Sometimes, especially if the update shipped a bad driver. You have 10 days to revert a feature update from Settings → Windows Update → Update history. For cumulative/security updates the rollback window is shorter and it's riskier — try driver rollback and the SoftwareDistribution cache fix first.
Will disabling SysMain break anything in Windows 11?
No. SysMain is not a required service — it's an optimization layer. Apps open normally without it; you'll either notice steadier memory behavior or no difference at all. On a machine with 16 GB of RAM and an NVMe SSD, there's almost nothing for it to do anyway.
Why did my PC slow down after a Windows update if it used to be fine?
The most common culprits: an update replaced a tuned vendor driver with a generic one, startup apps were re-enabled, visual effect or power plan settings were reset, or the update left behind large temporary files that pushed disk space below a comfortable threshold.
What if DISM returns "The source files could not be found"?
DISM couldn't reach Windows Update to download repair files — usually a firewall or network policy issue. You can supply a local source: download a matching Windows 11 ISO from Microsoft, mount it, and run:
DISM /Online /Cleanup-Image /RestoreHealth /Source:esd:D:\sources\install.esd:1 /LimitAccessReplace D: with your mounted ISO drive letter. The /LimitAccess flag prevents DISM from falling back to Windows Update and failing again.