Windows 11 update stuck? Identify the phase before changing anything

First, name the phase that appears stuck

The same percentage can mean different work in different places. A progress indicator inside Settings is not the same state as an installation screen during restart, a firmware update, or an “Undoing changes” recovery screen.

• Checking for updates: Windows is searching and comparing available updates.
• Downloading: connection speed, network settings, update size, and delivery state can affect progress.
• Installing in Settings: Windows is preparing or applying files while the normal desktop remains available.
• Restarting or working on updates: Windows is applying changes outside the normal desktop. Interruption carries more risk.
• Firmware or vendor update: follow the exact device maker's warning. Do not treat it as an ordinary Windows download.
• Undoing changes: Windows is attempting to return to the prior state after an unsuccessful installation.
• Failed in update history: the active attempt has ended; the error, KB, and time are now the most useful clues.

Build the update evidence card

Capture these details before retrying, deleting files, removing a driver, or changing a service:

• The exact words and progress indicator on screen, plus a photo if safe.
• The last time the percentage, animation, disk light, fan behavior, or status message changed.
• The update name and KB identifier from Windows Update or Update history.
• The full error code, including every leading zero and letter.
• The Windows edition, version, and OS build from winver when the desktop is available.
• Available storage on the system drive and whether Windows prompted for more space.
• Whether the PC is plugged in, the network is stable, and a VPN, proxy, dock, or external storage device is involved.
• Recent driver, firmware, security, storage, or hardware changes.
• Whether the BitLocker recovery key and a current backup are available before recovery work.

There is no reliable universal “stuck” timer

Microsoft says update download time depends primarily on connection speed, network settings, and update size. Installation time also varies with the update, device, storage, and phase. A fixed number of minutes does not prove failure.

Look for recent movement and phase changes instead. Record the last confirmed change, whether the desktop still responds, and whether the update history records a completed failure. An animation alone does not prove useful progress, but an unchanged percentage alone does not prove that the system has stopped.

If Windows still reaches Settings

1. Save work and capture the evidence card. Do not close the only copy of the error or update identity.
2. Check power and the ordinary internet connection. Keep a laptop plugged in. Avoid introducing a new VPN, proxy, hotspot, dock, or network change during diagnosis.
3. Review storage. Open Settings > System > Storage and record the available capacity. Use Windows' Storage Sense or Cleanup recommendations only after reviewing what will be removed.
4. Run the Windows Update troubleshooter. In Windows 11, use Settings > System > Troubleshoot > Other troubleshooters > Windows Update > Run.
5. Restart normally when Windows offers or safely permits it. Record whether the phase changes, the update completes, or an error appears.

The troubleshooter is a supported first diagnostic step, not proof that every update problem is a damaged cache. Keep its result and any error it reports.

If downloading is not moving

Record the connection type, whether other ordinary sites load, whether the network recently changed, and whether the PC is on battery power. Microsoft does not support a universal download-duration threshold because connection speed, network settings, and update size differ.

Do not delete SoftwareDistribution, disable security software, or reconfigure update services as the first response to an unchanged percentage. Those steps remove context or change protected system behavior before you know whether the issue is network, storage, update-specific, or already recorded as an error.

If installation is still inside Settings

Keep the PC powered, save other work, and note whether storage, CPU, or disk activity changes. If the phase eventually produces an error, preserve that code and the matching KB. If the desktop remains usable, the normal restart option and the Windows Update troubleshooter are safer first routes than an abrupt shutdown.

For sustained storage activity, use the separate guide to Windows 11 disk usage at 100%. High activity during an update can be expected for a period; the process, duration, errors, and whether activity settles matter more than the percentage alone.

If the PC is restarting, installing, or undoing changes

Do not interrupt firmware or an explicit “do not turn off” phase. Keep stable power connected and avoid pressing keys or disconnecting storage without exact vendor guidance. A repeated boot loop, a frozen firmware screen, power loss, storage warnings, or unavailable recovery key is a support boundary rather than a reason to guess at shutdown timing.

If Windows returns to the desktop after undoing changes, immediately preserve the update history, error, KB, build, and time. That completed rollback provides better evidence than trying the same installation repeatedly.

Match the build and KB to Windows release health

Microsoft's Windows release health site lists known issues, resolved issues, release notes, and safeguards by supported Windows version. Match the device's version and build first, then look for the exact KB or symptom. Do not assume a headline about another build, preview channel, manufacturer, or update applies to this PC.

This article intentionally does not summarize a current July 2026 update incident. Release-health information changes, while the evidence workflow remains useful. Record the official issue page and access date if a true match exists.

Use error codes as routes, not diagnoses

Microsoft maps different update codes to potential file, interruption, storage, permission, service, or driver paths. Preserve the full code and follow the current official page for that code. Similar-looking codes can require different action, and one code does not prove which file, driver, or component failed.

Do not uninstall broad driver groups, disable antivirus, resize partitions, edit the registry, or remove an update based only on a generic code summary. Model-specific drivers, encryption, storage layout, and recovery access can materially change the risk.

Keep advanced repair steps behind a recovery boundary

Microsoft labels command-line update repair procedures as advanced. Cache deletion, service resets, system-file repair, update removal, in-place reinstall, and recovery-environment changes require administrator access and a clear reversal plan. Before any of them, preserve the evidence card, back up important data, and confirm the BitLocker recovery key where encryption is enabled.

If Windows cannot reach the desktop, repeatedly loops, or cannot enter supported recovery options, hand off with the exact phase and evidence. Avoid stacking several fixes; changing one variable at a time is the only way to know what altered the result.

What to keep for the next diagnostic decision

Keep the screen photo, phase, movement timeline, KB, build, error code, storage state, power and network conditions, release-health match, troubleshooter result, and any rollback or boot-loop behavior. For nearby symptoms, see the guides to Windows 11 freezes and a black screen after login, or browse the OmniMend blog.

If those details are difficult to keep together, OmniMend can help collect and organize the diagnostic clues for review. It does not bypass Windows Update, alter protected services automatically, recover an unavailable BitLocker key, or guarantee that an update will install.