Fix Windows 11 Slow After Update (2026 Guide)

Restart your PC. Not shut down — restart. These are different things on Windows 11 and about a quarter of the post-update slowdown cases I handle could’ve been solved by pressing the right button. Windows 11 uses Fast Startup by default, so “Shut down” hibernates the kernel session to disk and boots you back into a stale state that hasn’t fully processed the update. Click Start, Power, Restart. That forces a clean reinitialization. If you’re still slow two hours after a proper restart, something permanent changed and waiting it out won’t fix it.

A customer called about a Dell Inspiron 15 that had been running fine for two years — woke up one morning and Chrome took a full minute to open. She was already shopping for a replacement. I pulled up Task Manager remotely and had the answer in ninety seconds. The May 2026 cumulative update had flipped SysMain back on, Widgets had reappeared on the taskbar pulling news data in the background, and post-install cleanup was still chewing through temp files because her C: drive only had 9 GB free. Disabled SysMain, killed Widgets, ran Disk Cleanup, and the machine was back to normal in fifteen minutes.

Diagnose It in Task Manager

Open Task Manager with Ctrl+Shift+Esc and go to the Performance tab. You’re looking for which resource is pegged while the others look normal.

Disk pinned at 100% with CPU and memory looking fine is the classic post-update scenario on machines with spinning hard drives. TiWorker.exe — the Windows Modules Installer Worker — handles post-restart finalization and on a 5400 RPM drive it can lock the disk for one to three hours straight. SSDs almost never see this because they handle random I/O thousands of times faster. If this is you, the cleanup section below should help, and our 100% disk usage guide covers every other cause.

CPU sitting at 50-90% while idle means the update re-enabled something. A service, a background feature, a startup program you’d previously disabled. The features section below covers the sneaky ones. Our high CPU usage guide goes process-by-process if you need to chase down an exact culprit.

Memory above 80% with nothing open — check for re-enabled background apps or a known leak. The April 2026 cumulative update (KB5055627) shipped a Delivery Optimization bug that leaked memory until the following month’s patch.

Everything looks normal but the machine still feels sluggish? Updates sometimes reset your power mode. Check Power & battery settings and make sure you’re on Balanced or Best performance, not Power saver.

Clean Up Update Debris

Cumulative updates dump a shocking amount of temporary data. Rollback files alone can eat 10-20 GB. Open Settings, System, Storage, Temporary files. You’ll see categories like “Previous Windows installation(s),” “Windows Update Cleanup,” “Delivery Optimization Files.” Check them all and remove. Most machines get back 8-25 GB.

For a deeper pass, search Disk Cleanup in Start, right-click it, run as administrator. The admin version surfaces cleanup categories the normal one hides. If your C: drive was already tight before the update, that’s likely a big part of why things struggled — Windows needs 15-20% free space to manage the page file and stage future updates. Drop below that and everything grinds. Our disk space guide walks through recovering 30-80 GB if you need serious breathing room.

Features Windows Quietly Turned Back On

This is the part nobody else mentions. Microsoft treats certain features as part of the Windows 11 experience, so major updates re-enable them even if you turned them off six months ago.

Widgets is the worst. It runs Widgets.exe and WidgetService.exe constantly in the background pulling content from Microsoft’s servers. On a machine with 4-8 GB RAM and a budget processor, it eats 3-8% CPU just sitting there. Right-click the taskbar, uncheck Widgets if you see it.

Copilot keeps background processes running even when you never open it. Taskbar settings, toggle it off. If your machine shipped with Recall on a Copilot+ PC, check Privacy & security settings — an update could have re-enabled it, and Recall puts sustained load on the system by constantly capturing and indexing screen content.

SysMain — the application preloading service. On an SSD it’s harmless. On a hard drive it’s brutal, and updates turn it back on. Open services.msc, find SysMain, set it to Disabled if you’d previously turned it off. Background app permissions also flip back — in the Installed apps settings, click the three dots on any app, Advanced options, verify background permissions are set to Never for apps you don’t need running. Our speed optimization guide covers the full list of services worth disabling.

Drivers

Windows updates sometimes swap your manufacturer-specific drivers for generic Microsoft versions. These generic drivers work but they’re slower — the default Microsoft GPU driver doesn’t do hardware acceleration properly, their storage controller driver handles I/O queuing less efficiently.

Three drivers worth checking after any major update: GPU, chipset, and storage controller. For GPU go directly to nvidia.com or amd.com or intel.com. Don’t use “Update driver” in Device Manager — it finds the same generic Microsoft driver causing the problem. For chipset and storage, grab your laptop manufacturer’s model-specific package from their support page.

If a fresh driver from the update is causing trouble, you can roll it back in Device Manager — find the device, double-click, Driver tab, Roll Back Driver. You have 10 days before the previous version gets cleaned up. System Restore is another option — if a restore point exists from before the update, it reverts everything the update touched in one shot. Failing that, remove the update entirely through Windows Update, Update history, Uninstall updates. That also has a 10-day window by default, though you can extend it to 30 days by running DISM /Online /Set-OSUninstallWindow /Value:30 in an admin Command Prompt. If the slowdown also comes with freezing or blue screens, it’s almost certainly a driver conflict, and we can pull Event Viewer logs and boot traces remotely to pinpoint the exact version causing the problem.