How to Fix Windows 11 Update Failure: Error Codes and Stalls

Match the failure mode first, then use the fix that fits that stage: download failures usually point to component-store damage or a disabled update service, install failures often point to drivers or compatibility blocks, and if the code is 0x800F081F, the repair source is missing, so DISM needs a valid source path before anything else will stick. Microsoft documents DISM as an advanced manual method for supported versions of Windows Server, and the same standard Windows repair command is used here on Windows 11.

What Windows 11 update failure means

Windows Update can fail before the download finishes, during installation, or after the files are already on the PC. The fastest first step is to identify the stage, then match the error code or stall pattern to the branch below instead of trying random fixes.

Likely causes, from most to least likely

• Corrupted update files or component store damage.
• Driver conflicts or incompatible devices.
• Missing repair source.
• Disabled Windows Update service.

Windows 11 update failure decision table

Is Windows Update stuck or not finishing?

If the progress bar sits near the end, the failure is often an install stall rather than a download problem. Start by saving the setup logs from the failed attempt, then retry the Windows 11 Installation Assistant. A frozen 99% screen can still advance when the setup completes its last stage, so capture the logs and the exact code before you decide the next step.

1. Close open apps and save your work.
2. Run the Windows 11 Installation Assistant again.
3. If the stall returns, save the setup logs from the failed attempt.
4. Record whether it stops at 98% or 99%.
5. Note the exact error code, if one is shown.

Suppose the installer reaches 99% and sits there after the same setup is tried again. That pattern points more to a late-stage setup stall than to a bad download, so the next move is to save the logs and record the code and stage before changing anything else.

Does the error point to corruption?

Corruption errors usually need repair first, not another blind retry. Run DISM from an elevated Command Prompt, then run SFC after DISM completes. If DISM cannot get a repair source, the failure is 0x800F081F and you need a source path before the repair can finish.

1. Open Command Prompt as administrator.
2. Run DISM.exe /Online /Cleanup-image /Restorehealth.
3. Wait until the command finishes, even if it pauses for a while.
4. Run sfc /scannow.
5. Review %windir%\Logs\CBS\CBS.log for items DISM found, fixed, or could not repair.

If Microsoft Update is unavailable during the repair, use the source-based DISM form with /LimitAccess and a valid source. Microsoft also places DISM results in CBS.log, which is the file to save when the repair path fails or reports missing files.

Common error codes and fixes

Use the code to choose the next action. The fastest path is usually the one that matches the meaning of the code, not the one that sounds closest to the symptom. If a code points to corruption, repair the image first; if it points to a disabled service, fix the service path before anything else.

Do you need to remove a conflicting app or driver?

If the failure points to a block from software or hardware, remove the item before another upgrade attempt. A driver issue can show up as 0xC1900101 in several variants, and a compatibility block often appears as 0x800F0923. Use Device Manager to update, roll back, or uninstall the driver linked to the failure, and remove a named app if the setup message identifies one.

1. Open Device Manager and update, roll back, or uninstall the driver linked to the failure.
2. If a specific app is named in the block, uninstall that app.
3. Restart the PC.
4. Retry Windows Update or the Windows 11 Installation Assistant.
5. If the same code returns, save the logs and move to the next branch.

A common first-timer mistake is to keep retrying the upgrade while the same printer, storage, or driver package remains in place. If the same code returns after the change, stop repeating the install and move to log-based escalation.

What to collect before you escalate

If the update still fails, collect evidence before another attempt changes the trail. The useful items are the exact code, the stage where it failed, the Windows build, SetupDiag output, and CBS.log. Those details turn a vague failure into something a support team or repair workflow can act on.

1. Open Settings > System > About and record the exact Windows build.
2. Save the full error code exactly as shown.
3. Note whether the failure happened during download, install, restart, or first boot.
4. Run SetupDiag after the failed upgrade and save its output.
5. Copy %windir%\Logs\CBS\CBS.log before you try again.

If DISM reports a missing source or SetupDiag points to a blocked upgrade, that is the point to move to a repair install or clean install. Do not skip the build number or the log files; those are the details that separate a one-off failure from a repeatable block.

Still not working?

If the branch-specific fix did not clear the problem, the next step is a repair install or clean install, but only after you have the code, the Windows build, and the setup logs. If the PC is stuck in a reboot loop, keep the logs and stop repeating the same upgrade path until the blocking driver or app is removed.

1. Save the setup logs and CBS.log.
2. Record the exact error code and failure stage.
3. Confirm the installed Windows build in Settings > System > About.
4. Use SetupDiag to identify the block if the upgrade failed after downloading.
5. Only then move to a repair install or clean install.

Prevent the next failure by removing easy blockers before the upgrade starts: free up storage with Settings > System > Storage > Temporary files, or by uninstalling apps you no longer need, and let Windows Security finish a scan before you retry.

Frequently asked questions

How do I fix a Windows 11 update failure?

Start by matching the failure stage, then use the branch that fits it. Download failures usually need DISM and SFC, install failures often need driver cleanup, and a stall near 99% usually needs log collection before you decide the next step. Save the code and logs before any third retry.

How do I fix a Windows 11 update error?

Use the exact code first. For 0x800F081F, run DISM.exe /Online /Cleanup-image /Restorehealth with a valid source, then sfc /scannow. For 0x80073712, repair the component store first. For 0x8024002E, check whether the Windows Update service is disabled and re-enable it before retrying.

How do I fix Windows 11 update error code 0x800f0991?

There is no standard Windows Update meaning for 0x800F0991 in the Microsoft error list used here, so treat it as an unverified code and collect more data first. Save the full message, the update stage, the Windows build, SetupDiag output, and CBS.log, then compare the issue against the closest known code family.

How do I fix Windows 11 update error code 0x800f081f?

0x800F081F means CBS_E_SOURCE_MISSING. Run DISM.exe /Online /Cleanup-image /Restorehealth from an elevated Command Prompt with a valid source available, then run sfc /scannow. If Microsoft Update is unavailable, use the DISM option with /LimitAccess and a known-good source. (Microsoft Support)

Why does Windows 11 update keep failing?

The same update keeps failing when the blocker is still present, such as corrupted update files, a disabled Windows Update service, an incompatible driver, or a conflicting app. The fix is to identify the stage, match the code, and remove the cause before you retry. Repeating the same install without a change usually repeats the same failure.

What should I do when Windows 11 update is stuck?

Save the setup logs, record the exact error code and failure stage, and retry the Windows 11 Installation Assistant once. If it still freezes near 98% or 99%, keep the logs and check whether a driver or device is blocking the final stage. A second freeze after another attempt is a sign to collect logs and switch to a repair path.