There’s a special kind of dread in watching SetupHost.exe — Modern Setup Host — consume 70–100% of your HP laptop’s CPU for hours while a Windows upgrade inches along at 12%. Your laptop is hot, loud, and unusable, and you can’t tell whether it’s making progress or just suffering. Here’s the reassuring truth first: during a Windows feature update, this is normal. Modern Setup Host is migrating your entire system to a new Windows build, and that’s genuinely CPU-intensive work.

The problem cases are when it never finishes — stuck at the same percentage for hours, or failing and rolling back repeatedly. HP laptops have a few specific wrinkles: HP’s own driver packages sometimes conflict with the upgrade, and older HP models with spinning hard drives turn a one-hour upgrade into an all-day affair.

For the broader post-update slowdown picture, see Windows 11 slow after an update , and to keep background apps from competing with the upgrade, disabling startup programs helps.

Why this happens

  • A feature update actively installing: The normal case — SetupHost.exe works hard migrating your system to the new Windows build.
  • The upgrade is stuck on a phase: Driver migration or app compatibility checks can hang indefinitely on specific configurations.
  • Conflicting HP drivers or software: Outdated HP drivers, especially storage and chipset drivers, can block upgrade phases.
  • Insufficient disk space: Feature updates need 20+ GB of working room; a nearly full drive stalls the process.
  • Corrupt update download: A damaged downloaded upgrade package causes repeated failed attempts.
  • Third-party antivirus interference: Some security products hook into setup phases and slow or block them.
  • Peripheral devices confusing setup: USB devices (especially storage and docks) can hang the driver-migration phase.

How to fix it

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

Fix 1: Determine whether it’s progressing or stuck

The most important diagnostic step — don’t intervene in a working upgrade.

  1. Open Settings > Windows Update and look at the current status — it should show the feature update name and a progress percentage.
  2. Write down the percentage, wait 30 minutes without using the laptop heavily, and check again. Any movement — even 12% to 14% — means it’s working. Leave it alone.
  3. Check Task Manager: SetupHost.exe with accompanying disk activity is working; SetupHost.exe at flat 25% CPU with zero disk activity for over an hour is stuck.
  4. Look at C:\$Windows.~BT\Sources\Panther\setupact.log (the setup log) — recent timestamps mean active progress; a log that hasn’t updated in hours confirms a hang.
  5. Rule of thumb: under 3 hours on an SSD-based HP laptop, let it run. Over 4 hours with zero progress, treat it as stuck.

Fix 2: Give the upgrade ideal conditions to finish

If it’s progressing slowly, help it along instead of fighting it.

  1. Plug in the laptop and remove the battery-saver throttling — setup runs faster on AC power with the Best performance power mode selected.
  2. Disconnect all USB peripherals except keyboard/mouse — external drives, docks, printers, and USB hubs are notorious for hanging the driver-migration phase.
  3. Close all your applications — every open app is something setup must migrate, and heavy apps compete for the CPU setup needs.
  4. Free up disk space: you want 25+ GB free on C:. Run Disk Cleanup and empty the Recycle Bin. A cramped drive is the top reason upgrades crawl.
  5. Ensure a stable internet connection — setup phones home during the upgrade, and a dropping Wi-Fi connection can stall phases. Prefer ethernet or sit close to the router.

Fix 3: Update HP drivers before retrying the upgrade

HP-specific conflicts are a leading cause of stuck upgrades.

  1. Visit HP’s official support site , enter your exact model, and download the latest chipset, storage/RAID, and BIOS drivers — install them and restart.
  2. Open the HP Support Assistant (preinstalled on most HP laptops) and install every recommended driver and firmware update it offers.
  3. Pay special attention to storage controller drivers — outdated Intel RST or AMD storage drivers are the classic SetupHost.exe hang culprit on HP machines.
  4. Update your BIOS if HP offers a newer version — BIOS updates frequently fix the low-level incompatibilities that stall Windows setup. Keep the laptop plugged in during the flash.
  5. After driver updates, go to Settings > Windows Update and retry the feature update — with current drivers, previously stuck upgrades often sail through.

Fix 4: Run the Windows Update troubleshooter and clear the cache

For upgrades stuck due to corrupt download or update components.

  1. Go to Settings > System > Troubleshoot > Other troubleshooters > Windows Update > Run.
  2. If the upgrade download itself is corrupt, clear it: open Terminal (Admin), run net stop wuauserv and net stop bits, then rename C:\Windows\SoftwareDistribution to SoftwareDistribution.old, then net start wuauserv and net start bits.
  3. Check for updates again — Windows re-downloads the feature update package cleanly, which resolves corruption-induced hangs.
  4. Check Microsoft’s official Windows support page for known issues with your specific feature update version — some builds have documented blocks with workarounds.
  5. If a specific KB is failing repeatedly, search for it on the Microsoft Update Catalog — standalone installers sometimes succeed where Windows Update fails.

Fix 5: Temporarily disable third-party security software

Antivirus hooks are a documented upgrade blocker.

  1. If you run third-party antivirus, disable its real-time protection temporarily — or better, uninstall it completely before the upgrade and reinstall after (most vendors’ tools leave filter drivers behind even when “disabled”).
  2. Disconnect from any VPN — VPN filter drivers have caused setup hangs, particularly during the network-migration phase.
  3. Windows Security (Defender) can stay on — it’s designed to cooperate with setup. Only third-party products need attention.
  4. After the upgrade completes successfully, reinstall your security software and verify it’s the latest version compatible with the new Windows build.
  5. If you were running a third-party firewall with custom rules, back up the rules first — the uninstall/reinstall cycle can wipe them.

Fix 6: Repair system files, then retry

Corruption in the current installation sabotages the upgrade.

  1. Open Terminal (Admin) and run DISM /Online /Cleanup-Image /RestoreHealth followed by sfc /scannow.
  2. Uninstall any software you don’t need — fewer apps means less migration work and fewer compatibility blocks. Check Settings > Apps > Installed apps for old toolbars, duplicate utilities, and abandoned software.
  3. Run the PC Health Check app (from Microsoft) to confirm your HP laptop still meets the requirements for the target Windows build — requirement changes between builds occasionally block upgrades.
  4. If setup previously failed, check C:\$Windows.~BT\Sources\Panther\setuperr.log for specific error codes — searching the exact code usually reveals the blocking component.
  5. With repairs done and cruft removed, retry the update from Settings > Windows Update.

Fix 7: Abort cleanly and use the Installation Assistant

When Windows Update just won’t complete the upgrade.

  1. If SetupHost.exe has been frozen for 6+ hours: end it in Task Manager, then immediately run the Windows Update troubleshooter to clean up the aborted state.
  2. Pause Windows updates for 7 days (Settings > Windows Update > Pause updates) to stop the broken retry loop and get your laptop back.
  3. Download the Windows 11 Installation Assistant from Microsoft’s software download page — it performs the same upgrade through a different, often more reliable path.
  4. Run the assistant with peripherals disconnected and antivirus handled as in Fix 5 — it will take over the upgrade process.
  5. If even the assistant fails, the fallback is an in-place repair install from a USB created with the Media Creation Tool — boot from USB, choose Upgrade, keep files and apps.

Closing

Modern Setup Host high CPU during a Windows upgrade is usually the sound of progress — give it time, good conditions, and current HP drivers, and it finishes. When it’s genuinely stuck, the fix is unblocking the upgrade (drivers, disk space, corrupt downloads) rather than fighting the process itself. Patience first, troubleshooting second, and you’ll get to the other side of the upgrade with your files and sanity intact.

Frequently asked questions

What is Modern Setup Host (SetupHost.exe)?
Modern Setup Host is the engine behind Windows feature updates and in-place upgrades — when Windows installs a new version (like moving to Windows 11 24H2), SetupHost.exe does the work: migrating your files, settings, apps, and drivers to the new build. High CPU from it during an active upgrade is completely normal and expected. It only becomes a problem when the upgrade stalls and SetupHost.exe burns CPU for many hours without progress.
How long should Modern Setup Host run?
A typical feature update takes 30 minutes to 2 hours of active SetupHost.exe work on a modern HP laptop with an SSD — longer on older machines or hard drives. The process runs in phases (downloading, preparing, installing, migrating), and CPU spikes during the install and migration phases. If it’s been running at high CPU for more than 4–6 hours with the progress percentage frozen, the upgrade is likely stuck.
Can I end Modern Setup Host in Task Manager?
You can, but it’s risky mid-upgrade — killing SetupHost.exe during the install phase can leave Windows in a half-migrated state, though Windows is designed to roll back to the previous build if setup is interrupted. Only end it if the upgrade is clearly frozen (no progress for hours) and you’ve decided to abort. After killing it, run the Windows Update troubleshooter and check for the update again rather than leaving things half-done.
Why does Modern Setup Host keep coming back after I kill it?
Because Windows Update re-launches it — the pending feature update is still queued, so the system keeps retrying the upgrade. Killing the process treats the symptom; the update remains. To stop the cycle, either let the upgrade complete (the real fix), pause Windows updates temporarily, or resolve whatever is blocking the upgrade using the troubleshooting steps below.