Windows Update keeps failing: run an in-place repair install

Windows Update can repeatedly fail because the installed component/servicing state cannot be repaired by the normal update transaction, even though Windows still starts and applications and files are intact. An in-place repair install runs Windows Setup from inside the existing Windows session and reinstalls Windows while retaining personal files and applications when the media and installed system match and Keep personal files and apps is explicitly selected.

Three retained cases support this final-resort servicing path: a Windows 11 failure involving KB5018418/KB5018427, a Windows 11 24H2 cumulative-update failure displaying 0x80073712, and a Windows 10 Pro 22H2 sequence displaying 0x800F0922 with KB5062554, KB5065957, and KB5065429. In none of those records was a narrower root cause demonstrated. The successful repair action does not prove that every occurrence of either code requires reinstalling Windows.

Standard Windows 10 support ended on October 14, 2025. In 2026, whether a Windows 10 update is offered depends on the device's ESU or other supported servicing channel; an in-place repair does not create update entitlement.

Searchable Windows error codes and update identifiers

Use this procedure when all of the following are true:

• Windows 10 or Windows 11 can start to the normal desktop;
• the same applicable update or sequence has failed repeatedly across restarts;
• Windows Update troubleshooting and ordinary component checks have not produced a narrower demonstrated repair;
• storage is stable and there is no unresolved hardware error;
• official Windows media can be obtained for the installed edition, language, architecture, and compatible release;
• Setup offers Keep personal files and apps; and
• a verified backup exists even though the intended path is nondestructive.

Prefer a narrower fix first when the evidence identifies a specific security product, Windows Sandbox, an incompatible driver, insufficient system-partition space, or another isolated dependency. An in-place repair is appropriate when the installed servicing state itself remains the best-supported problem, not merely because one update attempt failed.

Do not use this procedure when Windows cannot reach a stable normal desktop, when Setup must be started by booting from media, or when Keep personal files and apps is unavailable. Booting from the media and choosing a custom installation is not an in-place repair.

It does not apply to an unsupported edition/language/architecture mismatch, an unactivated or licensing-disputed installation, an unstable disk, failing RAM, active malware response, domain-managed deployment that requires administrator control, or an update known to be blocked by a specific driver/application. It is not the first response to one transient update failure.

The exact corrupted manifest, payload, or servicing transaction may remain unknown. The in-place repair replaces a broad Windows layer and therefore establishes that the repaired operating-system state mattered, not which internal file was decisive.

The following may not remain unknown:

• installed Windows edition, release, build, display language, and architecture;
• activation state;
• exact failing KB and hexadecimal code, if displayed;
• whether the media matches the installed edition/language/architecture;
• whether Setup explicitly offers Keep personal files and apps;
• backup status; and
• whether storage and memory are sufficiently stable to complete multiple Setup restarts.

Do not use a guessed universal free-space number. Windows Setup must pass its own space/readiness checks, and enough additional working room must remain for rollback files and applications.

• Administrator account on the installed Windows system
• Verified backup of user files and application-specific data
• Preferably a recoverable system image because a same-version repair may not provide a dependable one-click rollback
• Stable AC power; disable sleep for the maintenance interval
• Official Microsoft Windows ISO or Media Creation Tool output
• Media matching installed edition, language, architecture, and a compatible same/newer repair level
• Sufficient free space as accepted by Setup
• Product keys, recovery information, and installers for critical applications in case repair exposes an existing problem
• Nonessential peripherals disconnected

Create an evidence directory on the actual online Windows system drive and record the starting state:

$evidence = Join-Path $env:SystemDrive 'UpdateEvidence\FIX-076'
New-Item -ItemType Directory -Path $evidence -Force | Out-Null

Get-ComputerInfo -Property WindowsProductName,WindowsVersion,OsBuildNumber,OsArchitecture,WindowsCurrentVersion |
  Format-List | Out-File (Join-Path $evidence 'windows-before.txt')

dism /Online /Get-Intl |
  Out-File (Join-Path $evidence 'international-settings-before.txt')

Get-WinUserLanguageList | Format-List * |
  Out-File (Join-Path $evidence 'user-language-list-before.txt')

Also run winver, open Settings > System > Activation on Windows 11 or Settings > Update & Security > Activation on Windows 10, and photograph the edition, build, and activation state.

Start from the running Windows desktop. Complete pending restarts and close applications. Disconnect nonessential USB storage, printers, docks, and external devices, but keep keyboard, mouse, display, network if Setup needs it, and stable power.

Preserve Windows Update history, the newest relevant %SystemRoot%\Logs\CBS\CBS.log, and any SetupDiag result already produced. Do not clear SoftwareDistribution, delete CBS logs, run registry cleaners, or reset component bases immediately before repair; doing so destroys evidence and can alter rollback options.

1. Open Settings > Windows Update > Update history and record the exact KB, failure count, phase, and code. Confirm the update applies to the installed release/architecture.

2. Restart Windows and retry the same update once. Stop repeated loops after the result is confirmed.

3. Check the volume without repair switches:

   chkdsk %SystemDrive%
   

   Stop on I/O errors, unreadable metadata, or evidence of an unstable disk.

4. Check component health from an elevated Command Prompt:

   dism /online /Cleanup-Image /CheckHealth
   dism /online /Cleanup-Image /ScanHealth
   sfc /verifyonly
   

   Save all output. 0x80073712 supports an inconsistent component store. A clean result does not disprove a servicing problem that appears only during update.

5. Apply only the narrower repair indicated by the two independent checks before considering Setup:

   • If DISM reports that the component store is repairable, run:

     dism /online /Cleanup-Image /RestoreHealth
     

     Require a successful result before treating the component-store repair as complete.

   • If sfc /verifyonly reports integrity violations—even when DISM reports a healthy store—run:

     sfc /scannow
     

   • If RestoreHealth repaired the component store, also run sfc /scannow afterward so protected files can be checked against the repaired source. Do not run sfc /scannow merely because the update failed when both earlier checks were clean.

   After any narrower repair actually performed, restart Windows, retry the same applicable update once, and preserve the new result. Stop here if the update succeeds. If DISM cannot repair the image, SFC still reports unrepaired files, or the same update fails again, retain those exact results as the justification for the broader in-place repair.

6. Check for narrower demonstrated causes before using a broad repair:

   • Windows Sandbox enabled in a matching 0x800F081F/0x800F0825 case: use FIX-075;
   • Malwarebytes or VIPRE isolated by a controlled result: use FIX-074;
   • update or Setup explicitly names a driver/application: correct that item first;
   • inadequate EFI/System Reserved capacity: use the partition-capacity diagnostic rather than resizing blindly;
   • storage, RAM, or thermal failures: stop for hardware repair.

7. Confirm media matching data. Use the DISM international-settings output, installed user/display language information, edition, and architecture—not Get-WinSystemLocale alone. The edition and display language offered by Setup must align with the installed Windows. If the selected media makes Keep personal files and apps unavailable, it is not a valid repair source for this procedure.

8. Continue when repeated servicing failure is demonstrated, the DISM/SFC repair-and-retest path did not resolve it, no safer narrow correction remains, storage is stable, the backup is verified, and matching official media is ready.

1. Download the official ISO or use Microsoft's Media Creation Tool for the installed Windows generation. Do not use a modified image, third-party download, or image chosen only by build number from an unknown source.

2. Verify that the downloaded media's language, architecture, and edition family match the recorded installation.

3. In the running Windows session, right-click the ISO and select Mount. If Media Creation Tool provides an Upgrade this PC now path, it may be used from the normal desktop. Do not reboot and boot from USB/DVD.

4. Open the mounted drive and run:

   setup.exe
   

5. Approve User Account Control. Let Setup perform its compatibility checks.

6. If Setup reports a blocking application, driver, language, edition, disk-space, or compatibility condition, cancel and resolve that exact block. Do not bypass it with undocumented switches.

7. At Ready to install, read both summary lines. Select Change what to keep.

8. Select Keep personal files and apps. If that choice is absent, greyed out, or changes to Nothing, cancel. Do not continue under this article.

9. Return to Ready to install and photograph the page showing the Windows edition being installed and Keep personal files and apps.

10. Select Install. Keep AC power connected. Do not close the lid, force power off, or interrupt the automatic restarts.

11. After the final sign-in, allow Windows several minutes to finish device/app provisioning. Do not immediately start another broad repair.

12. Confirm files, applications, edition, activation, network, and Device Manager before running Windows Update.

13. Open Settings > Windows Update, check for updates, and retry the original KB or its current superseding update. Complete each required restart.

For the retained KB5018418 case, the explicitly confirmed post-repair result was successful installation of KB5018427; do not require that obsolete sequence on a current machine. For the 0x80073712 case, the media repair cleared the observed cumulative-update failure but did not prove the exact corrupted component. For the Windows 10 0x800F0922 case, the repair succeeded on Pro 22H2 build 19045.5854; that build and its listed KBs are case identifiers, not universal targets.

• Expected pass: Setup completes with applications/files retained, activation remains valid, and Windows Update installs the original applicable KB or its superseding update.
• Setup cannot keep apps/files: Cancel. Resolve edition, language, architecture, media, or version mismatch. Do not downgrade the keep choice to finish faster.
• Setup rolls back: Preserve %SystemDrive%\$WINDOWS.~BT\Sources\Panther and SetupDiag output when available. Route by the exact setup phase/code rather than immediately repeating Setup.
• Repair completes but update still fails with the same code: The broad Windows layer was refreshed but the decisive cause remains. Stop and inspect CBS/Setup logs, policy, package applicability, reserved-partition capacity, driver blocks, or hardware.
• A superseding update installs instead: That is a valid servicing pass if Windows Update no longer offers the obsolete KB and the installed build is current for the device's support channel.
• Files/apps or activation are wrong after repair: Do not call the update issue solved. Begin rollback/recovery from the verified backup and captured Setup state.

• Do not boot from the installation media for this procedure.
• Do not choose Custom, delete/format partitions, or select Nothing.
• Do not proceed if Keep personal files and apps is unavailable.
• Do not use media for a different display language, architecture, edition, or an unsupported downgrade.
• Do not promise that an in-place repair is risk-free because it normally preserves files.
• Do not use an in-place repair before correcting an isolated Sandbox, security-product, driver, disk-space, or hardware cause.
• Do not force power off because a percentage appears paused; use Setup logs/support unless the machine has conclusively failed.
• Do not assume 0x800F0922 has one cause.
• Do not install the historical KB identifiers if Windows says they are superseded or not applicable.

The primary rollback boundary is the verified backup or system image made before Setup. A same-version in-place repair does not guarantee a Go back option, and the presence of Windows.old does not by itself make manual restoration safe.

If Setup detects a problem before installation begins, select Back or close Setup; no repair has been committed. If Setup automatically rolls back, leave its logs intact and verify that Windows returned to the recorded build before another attempt.

If the repair completes but creates a material regression, use System Restore only when a suitable restore point exists and understand that it may not restore all applications/drivers. For a severe regression, recover from the verified system image. Do not manually copy the old Windows directory over the new installation.

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

2. Confirm activation in Settings.

3. Open representative critical applications and verify user data paths.

4. Open Device Manager and confirm no new unknown or warning devices appeared.

5. Check component health:

   dism /online /Cleanup-Image /CheckHealth
   sfc /verifyonly
   

6. Open Windows Update history and confirm the original applicable update or its superseding update installed successfully.

7. Restart Windows at least twice and run Check for updates again.

8. Save final state:

Get-ComputerInfo -Property WindowsProductName,WindowsVersion,OsBuildNumber,OsArchitecture,WindowsCurrentVersion | Format-List | Out-File (Join-Path $env:SystemDrive 'UpdateEvidence\FIX-076\windows-after.txt')

9. Keep the repair media and backup until the machine has completed its normal workload and at least one later update scan without recurrence.

Confidence is approximately 80% when the update failure is repeatable, Windows remains normally bootable, no narrower cause survives review, storage is stable, matching official media offers Keep personal files and apps, and the post-repair update succeeds. Three reporter-confirmed outcomes support this repair class. It has not been independently lab-reproduced for the listed KB/code combinations.

Confidence is lower for 0x800F0922 because it has multiple causes, when component health is clean, or when only one update attempt failed. Stop before Setup if backup, power, media match, activation, storage stability, or the keep-apps choice is uncertain. Stop after an automatic rollback or repeated post-repair failure and analyze the exact Setup/CBS evidence instead of rerunning the same broad repair.