If your HP laptop was fine on 23H2 and turned into molasses the day 24H2 installed, you’re not imagining it — and you’re not alone. Feature updates touch everything: drivers, the search index, background services, power plans. When any of those land wrong on specific HP hardware, the result is a system-wide slowdown that feels like the laptop aged three years overnight.

The reassuring part: this is one of the most fixable slowdown patterns there is, because the cause is recent and specific. We’re not hunting a mystery — we’re undoing what the update broke. Work through these in order, and most HP laptops are back to full speed without a rollback.

Why this happens

  • Outdated HP drivers conflicting with 24H2 — storage, chipset, and graphics drivers written for 23H2 can perform badly under 24H2’s changed subsystems.
  • Post-update background activity — re-indexing, cache rebuilds, and drive optimization consume resources for days after the update.
  • Windows Modules Installer stuck — the update’s component servicing can get stuck in a loop, holding CPU indefinitely.
  • Corrupted update components — a partially failed update leaves the servicing stack in a bad state that drags the whole system.
  • Power plan reset by the update — 24H2 can reset custom power plans to balanced defaults with aggressive throttling.
  • Old HP bloatware misbehaving — pre-installed HP utilities that worked on 23H2 can conflict with 24H2’s changed APIs.
  • Search index rebuilt from scratch — the update invalidates the old index, triggering a full reindex that hammers CPU and disk.

How to fix it

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

Fix 1: Give it 72 hours, then judge

I know this sounds like a non-fix, but post-update settling is real and measurable. Don’t start surgery on day one.

Steps:

  1. Note the date the update installed (Settings → Windows Update → Update history).
  2. Use the laptop normally for 2–3 days, keeping it plugged in when possible.
  3. Check Task Manager → Performance periodically — if disk/CPU activity gradually declines, it’s settling.
  4. After 72 hours, if performance is still bad, proceed — the problem is real, not transitional.
  5. During the wait, don’t run “optimizer” tools; they’ll just compete with the background work.

Fix 2: Update all HP drivers for 24H2

This is the fix that resolves the majority of HP-specific 24H2 slowdowns. HP publishes 24H2-tested drivers separately from what Windows Update provides. Get them from HP support for your exact model.

Steps:

  1. Open HP Support Assistant and run a full check — install every driver and firmware update it offers.
  2. Then visit HP’s support site manually for your model and compare — install any newer chipset, storage (IRST/RST), graphics, and BIOS updates.
  3. Pay special attention to the Intel Rapid Storage Technology driver — the old version is a notorious 24H2 slowdown source.
  4. Restart after each driver group, not just at the end.
  5. Test performance after the restarts before moving on.

Fix 3: Check for stuck Windows Modules Installer

TiWorker.exe (Windows Modules Installer) should finish its post-update work and go quiet. If it’s still active days later, it’s stuck.

Steps:

  1. Open Task Manager → Processes and look for “Windows Modules Installer Worker.”
  2. If it’s consistently using high CPU/disk days after the update, open an elevated Command Prompt.
  3. Run DISM /Online /Cleanup-Image /RestoreHealth to repair the component store.
  4. Then run sfc /scannow.
  5. Restart and check whether TiWorker settles down within an hour.

Fix 4: Reset Windows Update components

A corrupted update state keeps background services churning. Resetting the update pipeline clears it.

Steps:

  1. Open an elevated Command Prompt.
  2. Run these commands, one at a time: net stop wuauserv, net stop bits, net stop cryptSvc
  3. Rename the software distribution folders: ren C:\Windows\SoftwareDistribution SoftwareDistribution.old ren C:\Windows\System32\catroot2 catroot2.old
  4. Restart the services: net start wuauserv, net start bits, net start cryptSvc.
  5. Run Windows Update again and install anything pending, then restart.

Fix 5: Restore your power plan

24H2 resets power plans more aggressively than previous updates. Your custom high-performance settings may be gone.

Steps:

  1. Go to Settings → System → Power & battery and set Power mode to Best performance (while plugged in).
  2. Open Control Panel → Power Options → verify your plan is still selected.
  3. Click “Change plan settings” → “Change advanced power settings” and re-apply your processor state tweaks.
  4. If you use HP’s power management features, open them and re-select your preferred thermal profile.
  5. Check that the plan survives a restart — if 24H2 keeps resetting it, that’s a driver issue; revisit Fix 2.

Fix 6: Tame the search indexer rebuild

The update forces a full search reindex. You can let it finish faster by narrowing its scope first.

Steps:

  1. Go to Settings → Privacy & security → Searching Windows and check indexing status.
  2. Open Indexing Options → Modify and uncheck locations you don’t need (see our search indexer CPU guide for the full trimming procedure).
  3. Leave the laptop plugged in and idle overnight to let the reindex complete.
  4. The next day, indexing should show “complete” and stay quiet.

Fix 7: Remove or update misbehaving HP bloatware

Old HP utilities are a common 24H2 conflict source.

Steps:

  1. Go to Settings → Apps → Installed apps and review HP-branded software.
  2. Update HP Support Assistant, HP Audio Switch, and similar tools to their latest versions.
  3. Uninstall HP utilities you never use — but keep anything related to function keys, power, or BIOS updates.
  4. Restart and test.
  5. If a specific HP app is the culprit, check HP’s site for a 24H2-compatible version before reinstalling.

Fix 8: Roll back to 23H2 (last resort)

If nothing else worked and the slowdown is severe, the 10-day rollback window is your escape hatch.

Steps:

  1. Go to Settings → System → Recovery.
  2. Under “Recovery options,” click Go back (only available within 10 days of the update).
  3. Follow the wizard — your files are preserved, but apps installed after the update may need reinstalling.
  4. After rolling back, pause feature updates (Settings → Windows Update → Pause updates) to prevent immediate reinstallation.
  5. Use the pause period to get HP’s 24H2-ready drivers in place, then update again deliberately. Microsoft’s Windows support pages document the rollback process.

Closing

Post-24H2 slowness on HP laptops is frustrating precisely because the laptop was fine yesterday — but that recency is also why it’s so fixable. Updated HP drivers plus a settled update pipeline resolve the overwhelming majority of cases, no rollback required. If your HP is slow for reasons unrelated to the update, our general Windows 11 speed-up guide covers the broader tune-up.

Frequently asked questions

Why is Windows 11 24H2 slower than 23H2 on my HP laptop?
24H2 introduced changes to memory management, the search indexer, and background services that increased idle resource usage on some hardware. HP-specific issues often involve outdated drivers that 24H2 interacts with poorly — particularly storage, chipset, and graphics drivers. Updating those drivers resolves the slowdown for most users without any other changes.
Should I roll back from 24H2 to 23H2?
Rollback is available for 10 days after the update via Settings → System → Recovery → Go back. It is a valid option if the slowdown is severe and nothing else helps, but it is a last resort — you lose newer security improvements, and 23H2 will eventually stop receiving support. Try driver updates and the fixes in this guide first.
How long does 24H2 take to settle after installing?
Give it 48–72 hours of normal use with the laptop plugged in. After a feature update, Windows re-indexes files, rebuilds caches, optimizes the drive, and completes background migrations — all of which consume CPU and disk. If the system is still slow after three days of regular use, the problem is not settling-in activity and needs active fixing.
Can HP Support Assistant fix 24H2 slowness?
Partially. HP Support Assistant is good at finding HP-specific driver and firmware updates, which are often the actual fix for 24H2 performance issues. Run it and install everything it offers. But it won’t fix Windows-level issues like indexer loops or corrupted update components, so use it as one step in the full sequence, not the whole solution.