Modern Setup Host — SetupHost.exe — appears when Windows installs a feature update, and it is supposed to be temporary. But many users find it camped at 60–100 percent CPU for five, eight, even twelve hours, with the update progress bar frozen and the laptop too hot to touch. If you came here after watching a video about the problem, this is the complete written fix list.

Some of that CPU is legitimate: migrating an entire operating system is genuinely heavy work, and on a mechanical hard drive it takes hours. The skill is telling a slow-but-working upgrade from a truly stuck one — because interrupting a working upgrade creates the exact corruption you are trying to avoid.

This guide starts with that judgment call, then works through the blockers in order: disk space, corrupted update cache, driver conflicts, and antivirus interference. If the underlying update queue is the issue more broadly, our Windows Modules Installer guide covers the servicing side.

Why this happens

  • Genuinely slow upgrade on an HDD: feature updates on mechanical drives legitimately take several hours of heavy CPU.

  • Corrupted downloaded update files: a bad download makes the installer retry or stall at the same percentage.

  • Insufficient free disk space: the upgrade stages 15–20 GB of files; without room it stalls instead of failing cleanly.

  • Incompatible storage or display drivers: drivers that fail migration checks block the upgrade mid-process.

  • Third-party antivirus interference: real-time scanning of the installer’s file operations slows or stalls migration.

  • Corrupted SoftwareDistribution cache: bad cached metadata feeds the installer inconsistent state.

  • Pending other updates: a queued cumulative update fighting the feature update for the servicing stack.

  • Failing drive sectors: read errors during file migration cause retries that look like a stall.

How to fix it

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

Fix 1: Decide whether it is stuck or just slow

This judgment call matters more than any fix. A working upgrade on slow hardware looks alarming — high CPU, hot laptop, frozen-seeming progress — but interrupting it guarantees a rollback at best and corruption at worst.

  1. Check the update progress percentage in Settings > Windows Update and write it down.
  2. Wait 60 minutes without touching anything, then check again — any movement means it is working.
  3. Listen for disk activity and check Task Manager’s disk graph: sustained disk I/O means real migration work.
  4. Only treat it as stuck if the percentage has not moved for 3–4 hours with the laptop plugged in.
  5. If it is merely slow, plug in, prevent sleep, and walk away — patience is the fix.

Fix 2: Free up disk space for the staging area

Feature updates need roughly 15–20 GB of free space to stage files, and the installer stalls rather than erroring cleanly when space runs out. This is the most common true blocker and the easiest to fix.

  1. Open Settings > System > Storage and check free space on C:.
  2. Run Cleanup recommendations and remove temporary files, large unused apps, and old downloads.
  3. Delete the Windows.old folder from a previous upgrade if present — it can be 15–25 GB alone.
  4. Empty the Recycle Bin and clear browser download folders of installers you no longer need.
  5. Aim for at least 25 GB free, then restart the stalled upgrade from Windows Update.

Fix 3: Clear the update cache and retry

A corrupted SoftwareDistribution cache feeds the installer bad data, and the installer stalls instead of recovering. Clearing the cache forces a fresh, clean download — slow, but reliable. Microsoft documents update troubleshooting on its Windows support site .

  1. If the upgrade is truly stuck, let the laptop sit until Windows rolls back on its own, or restart once to trigger the rollback.
  2. After rollback completes, open Command Prompt as administrator.
  3. Run net stop wuauserv and net stop bits.
  4. Run ren C:\Windows\SoftwareDistribution SoftwareDistribution.old, then net start wuauserv and net start bits.
  5. Check for updates again and let the feature update download fresh.

Fix 4: Update or remove blocking drivers

SetupHost runs compatibility checks, and drivers that fail them — storage controllers and display drivers most often — stall the migration. Updating from the vendor (not just Windows Update) resolves most blocks.

  1. Open Device Manager and note your storage controller and display adapter models.
  2. Download the latest chipset/storage and GPU drivers from the laptop vendor’s support site.
  3. Install them, restart, and then attempt the feature update again.
  4. If a specific driver is named in the update error history, uninstall that device driver temporarily and let Windows use its inbox driver for the upgrade.
  5. Reinstall the vendor driver after the upgrade completes successfully.

Fix 5: Temporarily disable third-party antivirus

Third-party antivirus products hook file operations at a low level, and their interference with the installer’s migration is a classic stall cause. Windows Security (Defender) is designed to cooperate with upgrades; third-party products sometimes are not.

  1. Open your third-party antivirus and disable real-time protection (note: do not uninstall yet).
  2. Disconnect any VPN, which can also interfere with the installer’s network checks.
  3. Retry the feature update from Settings > Windows Update.
  4. If the upgrade now proceeds, the antivirus was the blocker — re-enable protection after the upgrade finishes.
  5. Consider whether you still need the third-party product: Defender plus the fixes in our Defender CPU guide suit most users.

Fix 6: Install the feature update manually

When Windows Update’s pipeline is the problem rather than your PC, bypassing it with the official Installation Assistant or an ISO often succeeds where the automatic upgrade stalled. Grab the official tool from the Windows 11 download page .

  1. Back up your important files first — manual upgrades are safe, but backups are non-negotiable.
  2. Download the Windows 11 Installation Assistant from Microsoft’s official download page.
  3. Run it and follow the prompts, keeping files and apps when asked.
  4. Keep the laptop plugged in and untouched for the 1–3 hour duration.
  5. After completion, verify in Settings > System > About that the new version is installed.

Closing

Modern Setup Host high CPU demands one skill above all: distinguishing a slow upgrade from a stuck one. Give genuine installs time, then clear the real blockers — disk space, corrupted cache, bad drivers, antivirus interference — in order. Most stalled upgrades trace to one of those four, and fixing it beats every registry trick circulating online. When in doubt, the manual Installation Assistant from Microsoft succeeds where the automatic pipeline stalls.

Frequently asked questions

What is Modern Setup Host?
Modern Setup Host (SetupHost.exe) is the engine that installs Windows feature updates — the big twice-yearly upgrades like moving to 24H2. It runs the compatibility checks, migrates your files and settings, and applies the new Windows image. It is a legitimate Microsoft process that only runs during upgrades. High CPU from SetupHost during an active upgrade is expected; high CPU for many hours with no progress is the problem this guide addresses.
How long should Modern Setup Host run?
A healthy feature update takes 30 minutes to 2 hours of active SetupHost work depending on your drive speed and the update size, with CPU legitimately high during the file-copy and migration phases. Give it at least 2 to 3 hours on AC power before concluding it is stuck. If it has been running at high CPU for 6-plus hours with the progress percentage frozen, the upgrade has stalled and needs intervention.
Is it safe to end Modern Setup Host?
Ending it mid-upgrade is risky: it can leave the installation half-applied, though Windows is designed to roll back to the previous version on the next boot if the upgrade cannot complete. Only end the process after you have given it ample time and confirmed progress is truly frozen. The safer path is usually to let Windows fail and roll back on its own, then fix the underlying blocker before retrying the upgrade.
Why does Modern Setup Host get stuck?
The usual blockers are corrupted update files, too little free disk space for the staging area, incompatible drivers (especially storage and display drivers), third-party antivirus interfering with file operations, or a corrupted software distribution cache feeding the installer bad data. Each has a specific fix, which is why this guide works through them in order rather than recommending a single magic solution.