Ninety-nine percent. The Update Assistant has been sitting there for hours, one agonizing percent from done, and you are afraid to touch anything. This is one of the most common feature-update complaints — and one of the most misunderstood, because at 99% the assistant is often still working, just on the slowest part of the job.

The final percent covers driver migration, app compatibility checks, and the handoff to the restart phase — all disk-heavy, all slow on older hardware. But sometimes it genuinely is stuck: a hung driver migration or a locked file holding the whole process hostage. This guide shows how to tell the difference and how to unstick it safely.

Video sites are full of clips about this exact problem, which tells you how common it is — and how many of the suggested fixes are folklore. Disabling random services, deleting system folders by hand, and editing the registry mid-update cause more harm than the stall itself. The sequence below sticks to safe, reversible steps in the order that actually resolves the hang.

Why this happens

  • Driver migration is slow: The final phase migrates every device driver to the new build. On laptops with many devices or old drivers, this legitimately takes a long time with no visible progress.
  • Antivirus scanning every file: Real-time protection can scan each migrated file, multiplying the final phase’s duration severalfold on systems with heavy security suites.
  • Disk bottleneck: The 99% phase is write-intensive. Slow or nearly full disks stretch it from minutes into hours, looking exactly like a freeze.
  • Hung device driver: A single misbehaving driver can hang the migration thread indefinitely — progress stops for real, not just apparently.
  • Pending restart from earlier updates: Unresolved pending operations from previous updates can deadlock the assistant’s final phase.
  • Corrupted assistant download: If the feature update payload itself is damaged, the assistant can stall while repeatedly failing to verify the final files.
  • External devices interfering: USB devices with problematic drivers can stall migration when the assistant tries to bring them across to the new build.

How to fix it

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

Fix 1: Verify whether it is actually stuck

Patience is a legitimate fix at 99%. Check Task Manager for genuine activity before intervening — interrupting a working migration corrupts the install, while a truly hung one needs the steps below.

  1. Open Task Manager and check disk and CPU activity.
  2. Steady disk writes mean migration is progressing — wait at least two more hours.
  3. If the assistant’s processes show zero activity for over an hour, it is genuinely stuck.
  4. Only proceed with intervention once stuck is confirmed.

Fix 2: Disconnect external devices

USB peripherals are a notorious cause of migration hangs. Removing them eliminates an entire class of stall with thirty seconds of effort — do this before anything invasive.

  1. Unplug all USB devices except keyboard and mouse if needed.
  2. Disconnect docks, external drives, and printers.
  3. Eject any SD cards or USB sticks.
  4. Wait 30 minutes to see whether the assistant resumes on its own.

Fix 3: Restart the assistant cleanly

If the process is truly hung, kill it and restart rather than rebooting mid-migration. The Update Assistant resumes feature updates gracefully in most cases. Pipeline stalls rather than assistant stalls are the subject of Windows Update stuck on restarting .

  1. In Task Manager, end the Windows 11 Update Assistant process.
  2. Restart the laptop normally.
  3. Re-run the Update Assistant from Microsoft’s software download page .
  4. The assistant typically resumes near where it stopped rather than starting over.

Fix 4: Clear the assistant’s temporary files

A corrupted payload stalls verification at the final phase. Clearing the assistant’s working files forces a fresh, verified download of the feature update package.

  1. Open Disk Cleanup as administrator.
  2. Select the system drive and check Temporary Windows installation files.
  3. Click OK to remove the partially downloaded update files.
  4. Re-run the Update Assistant to download a clean copy.

Fix 5: Update drivers before the final push

Stale storage, chipset, and display drivers are the usual suspects behind migration hangs. Updating them from the manufacturer’s site before retrying removes the hang source. Feature update failures that produce stop codes follow the error 0xc1900101 pattern and its driver suspects.

  1. Visit your laptop manufacturer’s support site for the latest chipset, storage, and display drivers.
  2. Install them and restart.
  3. For Intel systems, Intel’s driver detection tool finds the correct versions automatically.
  4. Run the Update Assistant again with fresh drivers in place.

Fix 6: Use installation media instead

When the assistant repeatedly stalls, the Media Creation Tool’s ISO provides an alternative install path for the same feature update — often succeeding where the assistant’s migration logic hangs.

  1. Create Windows 11 installation media with the Media Creation Tool.
  2. Mount the ISO and run setup.exe.
  3. Choose to keep files and apps, then proceed with the upgrade.
  4. This performs the feature update through the standard setup engine instead of the assistant.

Fix 7: Let it finish overnight as the final option

When every intervention fails and the assistant shows genuine activity, the remaining option is time. Some 99% stalls on old hardware resolve after six to ten hours of grinding through migration — slow, but real. This is the last resort before abandoning the assistant for installation media.

  1. Confirm real disk and CPU activity in Task Manager first.
  2. Plug in AC power and set the sleep timer to Never.
  3. Leave the laptop alone overnight, untouched.
  4. If it is still at 99% in the morning, switch to installation media.

Closing

Ninety-nine percent is the Update Assistant’s hardest phase, not its broken phase — but when it truly hangs, you now know how to confirm it, what to unplug, and which alternative path finishes the job. Verify activity before acting, clear corrupted payloads, refresh the drivers, and use installation media when the assistant itself is the problem. The last percent always yields eventually.

Frequently asked questions

How long should the Update Assistant stay at 99%?
On a healthy system with an SSD, the final percent typically takes 20 minutes to an hour. On older hardware or nearly full disks, two to three hours of apparent stillness can still be normal migration work. Only treat it as stuck when Task Manager shows no disk or CPU activity from the assistant’s processes for over an hour — activity means progress, even without the number changing.
Is it safe to close the Update Assistant at 99%?
If it is genuinely hung — no activity for over an hour — closing it via Task Manager and restarting is reasonably safe; the assistant is designed to resume. Do not force a shutdown or power off mid-migration, though: killing the process is far safer than cutting power, because the process can roll back cleanly while a power cut cannot.
Why does the assistant always stall at 99% and not earlier?
The final percent is when driver migration, compatibility remediation, and the pre-restart handoff happen — the most complex, least parallelizable part of the update. Earlier phases are mostly downloading and file copying, which report smooth progress. The 99% phase does intricate per-device work that neither parallelizes well nor reports granular progress.
Should I use the Update Assistant or Windows Update for feature updates?
Windows Update is the smoother path when it offers the feature update — it handles everything in the background. The Update Assistant is the manual alternative for forcing a feature update Windows Update has not offered yet. If the assistant repeatedly stalls, switching to installation media (setup.exe from an ISO) gives you a third path using the standard setup engine.