Sixty-one percent. If you’ve watched a Windows feature update crawl and die, it was probably there — the number so infamous it has its own Reddit lore. The cruel part is that 61% is both the most common place for a harmless-but-slow phase and the most common place for a genuine driver-conflict stall. Telling the difference is the whole game, and this guide shows you how.

At 61%, the upgrade is in the driver migration and offline image-application phase: heavy disk I/O, minimal UI updates, real vulnerability to bad drivers. The fixes below start with ‘verify it’s actually stuck’ (because interrupting a healthy 61% is the worst move), then remove the usual stall causes — USB devices, third-party drivers, antivirus, disk pressure — in order. For black-screen variants of failed upgrades, see fixing the 24H2 black screen after update .

Plug in the charger now. Every step below assumes AC power — battery-saver throttling during an upgrade is its own stall cause.

Why this happens

  • Driver migration phase is disk-heavy and quiet: The 61% phase does enormous I/O with rare progress updates — it looks dead while healthy. Watch disk activity, not the percentage: sustained I/O means it is working.
  • Incompatible storage/chipset drivers: Drivers that cannot migrate to the new build halt the phase silently. Updating BIOS, chipset, and storage drivers before retrying removes this entire cause.
  • USB peripherals confusing migration: External drives, docks, and exotic USB devices can stall device enumeration. Unplug everything non-essential; stalled enumeration often resumes on its own within 30 minutes.
  • Antivirus blocking driver staging: Security products intercepting driver file operations during migration. Pausing real-time protection during the retry eliminates this interference cleanly.
  • Insufficient disk space for the offline phase: The new image needs staging room; tight SSDs stall without clear errors. Keep 20+ GB free — the offline phase is the most space-hungry part of the upgrade.
  • Corrupted prior download: A damaged ESD means the offline phase works with bad data and wedges. Clearing $WINDOWS.~BT and the download cache forces a byte-fresh payload.
  • Power/battery throttling: Laptops on battery throttle the I/O-heavy migration to a crawl. Run the entire upgrade on AC power with sleep disabled — throttling stalls are the most avoidable kind.

How to fix it

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

Fix 1: Verify the stall with disk activity, not the percentage

The percentage lies by omission. Disk activity tells the truth. The percentage lies by omission. Disk activity tells the truth.

  1. If you can reach Task Manager (Ctrl + Shift + Esc), check disk activity — sustained I/O means it’s working.
  2. No Task Manager? Listen for drive activity and watch the drive LED; feel for SSD warmth on thin laptops.
  3. Give it a full three hours on AC power before concluding anything.
  4. Only when disk has been flat-zero for 90+ minutes is it genuinely stuck — proceed then.
  5. If the machine has no disk LED, open Resource Monitor’s Disk tab on another attempt — it shows the same truth.

Fix 2: Disconnect all non-essential USB devices

The simplest real fix for 61% stalls, and the most skipped. The simplest real fix for 61 percent stalls, and the most skipped.

  1. If the upgrade screen is responsive enough, don’t touch it — instead physically unplug USB drives, docks, printers, and adapters.
  2. Leave only the charger (and the built-in keyboard/trackpad, obviously).
  3. Wait 30 minutes after disconnecting — stalled enumeration often resumes on its own.
  4. If it was going to unstick from this, it does so without any reboot.
  5. Reconnect devices only after the upgrade completes — mid-upgrade reconnection re-triggers enumeration stalls.

Fix 3: Ensure AC power and disable sleep/battery throttling

Power state during the offline phase matters more than people think. Power state during the offline phase matters more than people think.

  1. Confirm the charger is connected and the battery is actually charging.
  2. If you can access Settings (or did before starting), ensure sleep is disabled during the upgrade window.
  3. Remove any manufacturer ‘battery saver’ or ‘quiet mode’ that throttles disk I/O.
  4. Give the unthrottled system another hour — throttling-induced stalls resolve with surprising speed once lifted.
  5. If the battery was low when the upgrade started, that alone may explain a stall — note it for the retry.

Fix 4: Wait it out once more, then hard-reset only as a last resort

Patience is a fix. Interruption is a gamble. Sequence them correctly. Patience is a fix. Interruption is a gamble. Sequence them correctly. Microsoft documents the expected upgrade durations — compare before forcing anything.

  1. After Fixes 1–3, grant one more two-hour window of untouched waiting.
  2. If still flat-zero: press and hold the power button to force shutdown (last resort).
  3. Power on — Windows should detect the failed upgrade and roll back to your previous build automatically.
  4. Once back in Windows, do NOT immediately retry; work Fixes 5–7 first to remove the cause.
  5. After a rollback, wait a full day before retrying — the system needs time to clean up staged files.

Fix 5: Update BIOS, chipset, and storage drivers before retrying

The 61% stall is a driver-migration stall — so fix the drivers, then migrate. The 61 percent stall is a driver-migration stall — so fix the drivers, then migrate.

  1. From the manufacturer’s support site, update BIOS, chipset, and storage/IRST drivers to the latest.
  2. Update the graphics driver too (Intel/NVIDIA/AMD as applicable).
  3. In Device Manager, resolve any warning icons — unknown devices are migration poison.
  4. Retry the feature update only after the driver stack is fully current.
  5. Prioritize storage and chipset drivers over graphics here — migration stalls are usually storage-stack, not GPU.

Fix 6: Clean-boot and disable antivirus for the retry

Minimize what the migration phase has to chew through. Minimize what the migration phase has to chew through.

  1. msconfig → Services → check ‘Hide all Microsoft services’ → Disable all → Task Manager Startup → disable non-Microsoft entries → restart.
  2. Temporarily disable third-party antivirus real-time protection.
  3. Ensure 20+ GB free on C: (the offline phase is space-hungry).
  4. Launch the feature update from Settings → Windows Update in this clean state.
  5. Disconnect from the network during the offline phase if the installer allows — it prevents driver-fetch interruptions.

Fix 7: Use the Installation Assistant or ISO as an alternate engine

If Settings-based upgrade stalls at 61% twice, change the delivery vehicle. If Settings-based upgrade stalls at 61 percent twice, change the delivery vehicle.

  1. Download the Windows 11 Installation Assistant from the Windows 11 download page .
  2. Run it with USB devices disconnected and antivirus paused.
  3. Alternatively, mount a fresh ISO and run setup.exe — the in-place upgrade uses a slightly different staging path.
  4. Both install the identical final build; the stall was in the delivery, not the destination.
  5. The ISO path also lets you disconnect the network entirely, eliminating half the stall variables at once.

Closing

The 61% stall is famous because it’s where the upgrade does its hardest quiet work — and where bad drivers go to die. Verify with disk activity, strip the USB variables, feed it power, update the drivers, and retry clean. Respect the three-hour rule, and you’ll never interrupt a healthy upgrade again. Related guides: fixing the 24H2 black screen after update and reset Windows Update components on Windows 11 .

Frequently asked questions

Why do feature updates always seem to stall at 61%?
The 61% mark sits in the driver-migration and second-boot phase of the upgrade, where Windows is moving drivers and applying the new OS image. It’s a long, disk-heavy phase with infrequent progress updates, so it looks frozen while working — and it’s also where real driver conflicts halt progress. Both the illusion and the reality concentrate at 61%.
How long should I wait at 61% before intervening?
Give it at least three hours with the charger plugged in. Check Task Manager’s disk activity (via Ctrl+Shift+Esc if the upgrade screen allows, or just listen/feel for drive activity): sustained disk I/O means it’s working. Flat zero activity for 90+ minutes means it’s genuinely stuck.
Will forcing a shutdown at 61% break my laptop?
Windows feature updates are designed with rollback: interrupting usually returns you to the previous build intact. But ‘usually’ isn’t ‘always’ — there’s a small risk of an unbootable state requiring recovery media. Exhaust the non-interrupt fixes first, and only hard-power-off as a last resort with recovery media handy.
Why does safe mode or clean boot help a stuck feature update?
The 61% phase migrates drivers — third-party drivers and startup software are the most common things it chokes on. A clean boot minimizes what’s loaded during the migration, removing the conflict candidates. It’s the same logic as disconnecting USB devices: fewer variables, fewer stalls.