Windows Update still fails: use “Fix problems using Windows Update”

Eligible Windows 11 systems include a recovery option named Fix problems using Windows Update. Microsoft documents it for Windows 11 22H2 or later when the February 2024 optional update or a later update is installed; device-management policy can hide it. The feature downloads and reinstalls a repair version of the current Windows installation to repair system files and components while preserving apps, files, and settings. It is a higher-impact step than an ordinary update retry or troubleshooter, but it is more bounded than Reset this PC or a clean installation.

This writeup is for a normally starting Windows 11 computer on which a specific update continues to fail after basic, code-appropriate checks. It is not a universal response to the first Windows Update error. The procedure records the exact KB, code, service state, component-store state, device-management state, and repair result so a successful reinstall is not confused with an unverified retry.

Searchable Windows error codes and exact messages

Use the complete code together with the update title/KB and current OS build. Do not merge 0x80070422, 0x800F081F, and 0x800F0991 into one diagnosis merely because the same repair facility can eventually resolve more than one damaged Windows state.

Use this procedure when all of the following are true:

• Windows 11 starts and can remain connected to stable power and Internet;
• one or more applicable Windows updates repeatedly fail after a restart and controlled retry;
• the exact error code, KB/update title, and failure date are recorded;
• direct causes such as a disabled Windows Update service, insufficient disk space, a known safeguard hold, or a withdrawn/superseded update have been checked;
• ordinary Windows Update troubleshooting or code-specific DISM/SFC repair did not resolve the failure; and
• Settings > System > Recovery > Fix problems using Windows Update > Reinstall now is present and not blocked by device management.

This article also applies when Windows Update explicitly displays Reinstall your current version of Windows to repair system files and components.

Do not use this procedure on Windows 10. The specific Settings repair-reinstall facility covered here is a Windows 11 feature. Windows 10 requires its own code-specific repair or a matching in-place repair installation.

It also does not apply when:

• the update failed only once;
• Windows does not start or storage is unstable;
• the update is optional/preview and no longer offered;
• the device is managed by work or school and the option is unavailable or policy controls update repair;
• the objective is to leave or change a Windows Insider channel rather than repair the currently installed build;
• 0x80070422 is explained by an intentionally disabled service or organizational policy;
• the failing package is a driver, firmware, Microsoft Store app, optional feature, language pack, or third-party updater rather than a Windows operating-system update;
• a known Microsoft/OEM issue requires a specific mitigation or newer update; or
• the repair option is absent.

Do not substitute Reset this PC. Reset can remove applications and settings and is a different recovery operation.

The precise corrupted component, the event that damaged it, and why the ordinary update repair did not replace it may remain unknown. The repair-reinstall facility is designed to restore system files/components without requiring a manual package-by-package reconstruction.

The following may not remain unknown:

• the current Windows 11 version/build;
• the exact failed update title/KB and visible error code;
• whether the update is still offered and applicable;
• the Windows Update, BITS, and Cryptographic Services state when a service code is involved;
• whether the device is managed;
• whether DISM/SFC found or repaired corruption;
• whether Reinstall now is present;
• whether the PC is enrolled in a Windows Insider channel and, if so, which channel/build it is expected to retain; and
• whether the user backup, power, network, and free-space requirements are met.

• Windows 11 22H2 or later with the February 2024 optional update or a later update installed, and Fix problems using Windows Update visible under Settings > System > Recovery
• Local administrator rights
• A verified backup of important files and application-specific data
• Stable AC power
• A reliable, unmetered Internet connection when possible
• Adequate free space on %SystemDrive%
• The failed update/error recorded
• Time for a large download, installation, and one or more restarts
• Local access to the computer during recovery
• For the fallback ISO path, official Microsoft media matching the installed edition, architecture, system/default UI or install language, and Windows feature release, with a build/repair level not older than the installed OS

The option might be absent on a work/school-managed PC, on an earlier Windows 11 release, or when the February 2024 optional update or a later update has not supplied the feature. Its absence is a stop condition for this page, not authorization to force-enable it.

1. Restart Windows once and save all work.

2. Open Settings > Windows Update > Update history. Record each relevant failed update, its KB number, failure date, and displayed code.

3. Run:

   winver
   

   Record the edition/version/build.

4. Check the update page again. If the failed update is no longer offered and a newer cumulative update is available, attempt the newer applicable cumulative update once before a repair reinstall.

5. Create a local evidence folder from an elevated Command Prompt:

   md "%USERPROFILE%\Desktop\WindowsUpdate-repair-before"
   systeminfo > "%USERPROFILE%\Desktop\WindowsUpdate-repair-before\systeminfo.txt"
   fsutil volume diskfree %SystemDrive% > "%USERPROFILE%\Desktop\WindowsUpdate-repair-before\diskfree.txt"
   sc query wuauserv > "%USERPROFILE%\Desktop\WindowsUpdate-repair-before\wuauserv-query.txt"
   sc qc wuauserv > "%USERPROFILE%\Desktop\WindowsUpdate-repair-before\wuauserv-config.txt"
   sc query bits > "%USERPROFILE%\Desktop\WindowsUpdate-repair-before\bits-query.txt"
   sc query cryptsvc > "%USERPROFILE%\Desktop\WindowsUpdate-repair-before\cryptsvc-query.txt"
   

6. Copy the readable servicing logs:

   copy "%SystemRoot%\Logs\CBS\CBS.log" "%USERPROFILE%\Desktop\WindowsUpdate-repair-before\CBS-before.log"
   copy "%SystemRoot%\Logs\DISM\dism.log" "%USERPROFILE%\Desktop\WindowsUpdate-repair-before\DISM-before.log"
   

7. Open Settings > Accounts > Access work or school. Record any organizational connection. Do not disconnect it.

8. Open Settings > Windows Update > Windows Insider Program. Record the channel and build if the PC is enrolled. This repair is not a method for leaving an Insider channel or changing build tracks.

9. Verify the backup. Disconnect nonessential external storage/docks, close applications, and connect AC power.

1. Confirm that a Windows operating-system update—not an app/driver/firmware updater—has failed at least twice with the same code after a restart.

2. Interpret direct error codes before selecting the broad repair:

   • For 0x80070422, inspect the saved sc output. If wuauserv is disabled, determine whether policy, an administrator, security software, or corruption disabled it. Use the managed/default service correction first. Do not hard-code every service to Automatic.
   • For 0x800F081F, use FIX-084 to capture CBS_E_SOURCE_MISSING and perform one DISM/SFC pass.
   • For 0x800F0991, preserve the exact KB/build and CBS lines; do not invent a symbolic cause.

3. Run the Windows Update troubleshooter through Settings > System > Troubleshoot > Other troubleshooters > Windows Update > Run, or the Get Help flow offered by the current Windows build. Record what it reports and changes.

4. Restart and retry the exact update once after the troubleshooter. If it succeeds, stop; do not reinstall Windows.

5. Check the component store without repair:

   DISM.exe /Online /Cleanup-Image /ScanHealth
   sfc /verifyonly
   

6. If the scans find corruption, complete the code-specific DISM/SFC repair before this broad step unless Windows Update explicitly recommends reinstalling the current version.

7. Confirm free space is adequate for a repair download and temporary installation. Do not proceed with a nearly full system volume.

8. Open Settings > System > Recovery.

9. Confirm Fix problems using Windows Update is visible and offers Reinstall now. Read any warning or management notice in full.

10. Establish the evidence threshold. Proceed when the same operating-system update remains applicable and fails after restart/troubleshooter/code-specific checks, or when Windows Update itself recommends the current-version reinstall.

11. Stop if the code or update changes, the target becomes superseded, a service/policy cause remains unresolved, the option is absent, or the device is managed and the administrator has not approved the action.

Branch A — Run Fix problems using Windows Update

1. Confirm the backup, stable power, reliable network, local access, and free space one final time.

2. Open Start > Settings > System > Recovery.

3. Under Fix problems using Windows Update, select Reinstall now.

4. In the confirmation window, choose whether the PC may restart automatically 15 minutes after the installation completes. This does not remove the need to save work.

5. Select OK to begin.

6. Windows moves to the Windows Update page, downloads a repair version of the last successfully installed operating-system update, and installs it.

7. Leave the computer connected to AC power and the network. Do not run disk cleanup, shut down, reset, force-restart, or start another installer.

8. If download or installation pauses, verify that the network and power remain stable. Do not cancel based only on a stationary percentage.

9. Restart when prompted if automatic restart was not selected.

10. Sign in and wait for post-install processing to finish.

11. Run winver and confirm the expected Windows edition/version remains installed.

12. If the PC was enrolled in Windows Insider, confirm the expected channel remains selected before accepting another preview build.

13. Open Settings > Windows Update and select Check for updates.

14. Install the original failed update if it remains applicable, or the newer superseding cumulative update that Windows offers.

15. Restart again when required.

Branch B — Reinstall now is missing or blocked

1. Do not change registry keys, Group Policy, update rings, or management enrollment to expose the feature.

2. Confirm the Windows version and work/school management state.

3. If the PC is managed, contact the administrator with the exact KB, code, build, DISM/SFC result, and saved logs.

4. If it is an unmanaged Windows 11 PC that lacks the option, use matching official in-place repair media only after verifying edition, system/default UI or install language, architecture, the intended Windows feature release, and a media build/repair level not older than the installed OS. Keep personal files and apps remains a separate final Setup gate.

5. Before starting Setup, capture the installed build and revision from an elevated Command Prompt:

   reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v CurrentBuildNumber > "%USERPROFILE%\Desktop\WindowsUpdate-repair-before\installed-build.txt"
   reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v UBR >> "%USERPROFILE%\Desktop\WindowsUpdate-repair-before\installed-build.txt"
   dism /Online /Get-CurrentEdition >> "%USERPROFILE%\Desktop\WindowsUpdate-repair-before\installed-build.txt"
   dism /Online /Get-Intl > "%USERPROFILE%\Desktop\WindowsUpdate-repair-before\installed-language.txt"
   type "%USERPROFILE%\Desktop\WindowsUpdate-repair-before\installed-build.txt"
   

   Combine CurrentBuildNumber and UBR as the installed comparison value.

6. Mount the ISO, replace <ISO-letter> with its actual letter, and determine which image container exists:

   dir <ISO-letter>:\sources\install.wim
   dir <ISO-letter>:\sources\install.esd
   

7. List the contained images, identify the index matching the installed edition, and save detailed metadata for that exact index. Use only the WIM or ESD pair that matches step 6:

   dism /English /Get-WimInfo /WimFile:<ISO-letter>:\sources\install.wim > "%USERPROFILE%\Desktop\WindowsUpdate-repair-before\media-images.txt"
   dism /English /Get-WimInfo /WimFile:<ISO-letter>:\sources\install.wim /Index:<matching-index> > "%USERPROFILE%\Desktop\WindowsUpdate-repair-before\media-selected-image.txt"
   

   Or:

   dism /English /Get-WimInfo /WimFile:<ISO-letter>:\sources\install.esd > "%USERPROFILE%\Desktop\WindowsUpdate-repair-before\media-images.txt"
   dism /English /Get-WimInfo /WimFile:<ISO-letter>:\sources\install.esd /Index:<matching-index> > "%USERPROFILE%\Desktop\WindowsUpdate-repair-before\media-selected-image.txt"
   

8. Require the selected image's Version build component to equal the installed CurrentBuildNumber and its ServicePack Build/revision to be equal to or greater than the installed UBR. If the media is older, belongs to another feature release, lacks the matching edition/index, or cannot be compared unambiguously, stop and obtain current matching media. Do not treat an enabled Keep personal files and apps choice as proof that the media passed this build gate.

9. Only after that comparison passes, run <ISO-letter>:\setup.exe from the running Windows installation. At Ready to install, require the intended edition and feature release and Keep personal files and apps. Cancel if any item differs. If available media would install a newer feature release, route it as a feature upgrade with separate compatibility and safeguard checks rather than calling it a repair reinstall.

10. For Windows 10, use the in-place branch of the appropriate code-specific writeup; this Settings feature does not apply.

Branch C — The repair download or install fails

1. Record the new displayed error and phase. Do not assume it is the original Windows Update code.

2. Preserve the updated CBS/DISM logs and any Setup/Panther logs created.

3. Restart normally once if Windows requests it.

4. Do not repeatedly select Reinstall now. Route the new failure to its code-specific repair path.

• The repair version installs and the same target update succeeds: this supports the prior Windows system-file/component state as the likely blocker; it does not prove the exact damaged component.
• The repair version installs and only a superseding update succeeds: servicing is working, but supersedence or package changes may be decisive. Do not claim that the prior component state was proven causal.
• The repair completes but the same update still fails with the same code: preserve post-repair logs and use a package-specific servicing analysis; do not repeat the repair.
• The code changes: treat the new code and update phase as new evidence.
• The option disappears after device management is applied: the administrator controls the path; do not bypass it.
• The update is no longer offered: determine whether it was superseded, withdrawn, or blocked before claiming success.
• Windows starts but an application/device regresses: record the exact regression and driver/app version; separate it from whether the update installed.
• Windows does not start after repair/update: use WinRE and the saved backup/evidence; do not reset or clean-install immediately.

• Do not use this feature for the first unexplained update failure.
• Do not use it to bypass 0x80070422 caused by an intentionally disabled service or policy.
• Do not force-enable the feature on a managed or ineligible device.
• Do not confuse Fix problems using Windows Update with Reset this PC.
• Do not select Reset/Remove everything, clean install, or boot-from-USB paths for this repair.
• Do not delete SoftwareDistribution, catroot2, WinSxS, manifests, or servicing registry keys without a separate validated procedure.
• Do not run an unreviewed Windows Update reset script.
• Do not disable security controls, Secure Boot, BitLocker, VPN, or endpoint management to make the repair run.
• Do not interrupt the repair based only on elapsed time or a stationary percentage.
• Do not claim success merely because the repair finished; the previously failing update or its superseding update must install and survive restart.

There is no guaranteed direct undo for the current-version repair reinstall. Prepare rollback before starting.

1. Before selecting OK, cancel if the backup, power, network, free space, management approval, or target update identity is uncertain.

2. If the repair fails and Windows restores the earlier state, verify winver, user files, applications, activation, networking, and Update history. Preserve logs before retrying.

3. If the repair succeeds but the subsequently installed quality update causes a regression, open Settings > Windows Update > Update history > Uninstall updates. Remove only the exact update when it is listed and removal is supported.

4. If Windows cannot start after the quality update, use WinRE Troubleshoot > Advanced options > Uninstall Updates > Uninstall latest quality update only when the timing and update type match.

5. Restore missing personal data from the verified backup. A repair reinstall is designed to preserve files/apps/settings, but that design promise does not replace a backup.

6. Restore a full system image only using that backup product's tested recovery process. Do not overwrite the affected installation before collecting logs if escalation is possible.

1. Run winver and record the final version/build.

2. Confirm the user profile, representative files, critical applications, activation, devices, and network remain functional.

3. Open Settings > Windows Update > Update history. Require the exact formerly failing update or its superseding cumulative update to show successful installation.

4. Run:

   DISM.exe /Online /Cleanup-Image /ScanHealth
   sfc /verifyonly
   

5. Restart Windows twice, checking Update history after the second restart.

6. Run Check for updates once more. Record whether Windows reports You're up to date or offers another applicable update.

7. Compare post-repair service state and logs to the evidence folder. Historical errors are retained; judge only the new attempt timestamps.

8. Keep the backup and evidence until the system has completed two restarts and normal use without a recurrence.

Confidence is approximately 80% that Fix problems using Windows Update will resolve a persistent component/system-file-related Windows 11 Update failure when basic/code-specific checks have been completed, the repair option is natively offered, the target update remains applicable, and the target or superseding update installs afterward. Two independent source cases reported that this exact recovery feature restored normal updating; TechXplored has not independently reproduced them.

Confidence is lower when the error code was not captured, the update had only one failure, the update was preview/withdrawn/superseded, a service or policy problem remains, or the only success measure is completion of the repair itself.

Stop for an absent/blocked feature, managed-device restriction, 0x80070422 with unresolved service policy, unstable storage, inadequate backup/power/space/network, a new Setup/repair code, missing files/apps, or failure of the same update after one completed repair. Do not repeat the broad repair; preserve post-repair evidence and route to the exact code/package/phase.