If your laptop slowed down after the Windows 11 24H2 update and you want the fix without the fluff, this is the prioritized playbook. Not every “speed up Windows” tip is worth your time — some are placebo, some are risky, and a few genuinely work. Here’s the order that gets results, based on what actually causes post-24H2 slowdowns.

The short version: wait out the background storm, update drivers from the manufacturer, reclaim your settings, repair the servicing stack. That sequence resolves the overwhelming majority of cases. Everything below is that sequence, expanded with the details that make each step work.

For the full diagnostic version, see the complete 24H2 troubleshooting guide ; for sleep-related aftermath, fixing slow wake from sleep .

Why this happens

  • Driver friction: 24H2’s changed internals clash with old or generic drivers — the top real cause.
  • Background maintenance storm: Indexing, Defender, and optimization saturate the system for 1–3 days.
  • Reset configurations: Power plans, startup apps, and OEM thermal profiles revert to defaults.
  • Stuck servicing tasks: Partially applied update components retry endlessly in the background.
  • Incompatible utilities: Old OEM tools and third-party drivers misbehave on the new build.
  • Disk space pressure: 24H2 needs working room; full drives make post-update tasks thrash.
  • Firmware lag: Outdated BIOS/UEFI interacting poorly with 24H2’s hardware layer.

How to fix it

Work through these in order — diagnose first, then act.

Fix 1: Do nothing for 48 hours (strategically)

The best first fix is patience — but informed patience.

  1. Confirm the 24H2 install date in Settings > System > About and Windows Update > Update history.
  2. Keep the laptop plugged in, connected to Wi-Fi, and powered on (not sleeping) as much as practical for two days — idle time is when the maintenance storm does its work.
  3. Peek at Task Manager occasionally: busy SearchIndexer, MsMpEng, TiWorker, or .NET Optimization processes are the storm, and they’re supposed to be there.
  4. Don’t install “optimizer” tools or kill these processes during this window — interrupting servicing is how stuck states are born.
  5. After 48 hours, take stock: if Task Manager is calm at idle but the machine still feels slow, proceed — the storm has passed and what remains is real.

Fix 2: Update all drivers from the manufacturer (the big one)

This is the step that fixes most 24H2 slowdowns.

  1. Find your exact model number (sticker on the bottom or msinfo32) and visit the manufacturer’s support page: Dell , HP , Lenovo .
  2. Download and install in order: chipset, Management Engine (Intel) / chipset (AMD), storage/NVMe, graphics (NVIDIA , AMD , or Intel ), audio, Wi-Fi/Bluetooth.
  3. Check the BIOS/UEFI section — install any firmware update released around or after 24H2’s release; firmware mismatches cause subtle throttling and sleep bugs.
  4. After installing, open Device Manager and confirm zero yellow warning triangles.
  5. Restart and test for a full day of normal use before judging — driver changes sometimes need a boot cycle plus idle time to fully settle.

Fix 3: Reclaim power and startup settings

Undo what the update reset.

  1. Settings > System > Power & battery > Power mode → Best performance while plugged in.
  2. Open your OEM utility (Vantage, MyASUS, Armoury Crate, Dell Optimizer, NitroSense) and restore your performance/thermal profile — updates frequently reset these to balanced or quiet.
  3. Task Manager > Startup apps — re-disable everything the update resurrected. Sort by Startup impact; High-impact non-essentials go first.
  4. Settings > Privacy & security — review background app permissions and turn off what you don’t use.
  5. Restart and compare boot time and first-five-minutes responsiveness against your memory of pre-update behavior.

Fix 4: Repair servicing and clear stuck update state

For the invisible background load.

  1. Settings > System > Troubleshoot > Other troubleshooters > run the Windows Update troubleshooter.
  2. Elevated terminal: DISM /Online /Cleanup-Image /RestoreHealth then sfc /scannow.
  3. Clear the update cache: stop wuauserv and bits, rename C:\Windows\SoftwareDistribution to .old, restart the services.
  4. Settings > Windows Update > install everything pending, including optional driver updates, so the system reaches a fully settled state.
  5. Monitor Task Manager for an hour — phantom load from TiWorker and friends should be gone. Official servicing guidance: Windows support .

Fix 5: Remove software that 24H2 broke

Old utilities are common casualties.

  1. Settings > Apps > Installed apps — uninstall expired antivirus trials, old OEM utilities you don’t use, “driver boosters,” and anything unfamiliar.
  2. Update third-party antivirus to the latest version, or test with Microsoft Defender alone — outdated AV filter drivers are a leading cause of post-24H2 stutter and high CPU.
  3. Update VPN clients, virtualization software, and RGB/fan controllers to 24H2-compatible versions — these install kernel drivers that the update can destabilize.
  4. Check Task Scheduler for leftover tasks from uninstalled software still firing and failing.
  5. Reboot and re-baseline: compare idle CPU, boot time, and app launch speed to your Fix 1 notes.

Fix 6: Free disk space aggressively

Give the system room to work.

  1. Settings > System > Storage — target 20%+ free on C:.
  2. Disk Cleanup as admin > Clean up system files: Windows Update Cleanup, temporary Windows installation files, Delivery Optimization files, old driver packages.
  3. Uninstall large unused apps and games; move media libraries off the system drive.
  4. Check for a bloated C:\Windows\SoftwareDistribution\Download or leftover $Windows.~BT folders if the update was recent.
  5. After cleanup, restart — low-space thrashing affects everything from SysMain to the pagefile, so this step’s benefits are broad. Memory issues too? See fixing Windows 11 memory leaks .

Fix 7: Escalate only if needed — repair install, rollback, reset

In order of increasing disruption.

  1. In-place repair install: download the 24H2 ISO from the Windows 11 download page , mount it, run setup, keep files and apps. Fixes deep corruption without data loss.
  2. Rollback (within 10 days of the feature update): Settings > System > Recovery > Go back. Then pause updates, update all drivers, and reinstall 24H2 deliberately via the Installation Assistant.
  3. Reset this PC (Keep my files): the cleanest non-destructive option. Back up first anyway.
  4. After any escalation, immediately install manufacturer drivers before letting Windows Update run wild — this prevents the same driver friction from recurring.
  5. Document what worked. Next feature update, you’ll do Fix 2 proactively and likely skip this entire guide.

Closing

The best way to fix 24H2 slowness isn’t a magic tweak — it’s a sequence: let the storm pass, update every driver from the manufacturer, reclaim your settings, repair servicing, remove broken software, free space. Do it in that order and you’ll fix the actual problem instead of chasing symptoms. Most laptops come back to full speed in an afternoon, no reinstall required.

Frequently asked questions

What is the single best fix for 24H2 slowness?
Updating all drivers from your laptop manufacturer’s support site. 24H2 changes enough under the hood that old or generic drivers cause the majority of real performance regressions — stutter, high CPU, broken sleep, throttled boosting. One focused driver-update session (chipset, graphics, storage, network, BIOS) resolves more post-24H2 slowdowns than every other fix combined.
How long does 24H2 take to settle down on its own?
Typically 24 to 72 hours of normal use while plugged in. During this window Windows rebuilds the search index, Defender re-baselines, .NET optimizes assemblies, and SysMain relearns your patterns. Judge the update’s true performance only after this settles. Troubleshooting before the storm passes wastes effort on symptoms that would have vanished alone.
Is a clean install better than troubleshooting 24H2 issues?
A clean install is the most thorough fix and guarantees no leftover conflicts, but it costs hours of reinstalling apps and restoring settings. For most users the middle path wins: targeted driver updates, servicing repairs, and settings reclamation fix the problem in under an hour. Reserve clean installs for systems with years of accumulated cruft or corruption that resists every targeted repair.
Should I delay future feature updates to avoid this?
A short delay is sensible. Pause feature updates for two to four weeks after release to let early driver and compatibility issues surface and get fixed. But don’t defer indefinitely — feature updates include security improvements, and very old builds eventually lose support. The best strategy is prompt driver preparation, then installing the update deliberately rather than letting it surprise you mid-work.