Fix Windows Update Error 0x80073712 Without Losing Files

Windows Update error 0x80073712 usually means that Windows is missing or cannot read a component in its component store, or that update files are corrupted. Restart first, then repair the component store with DISM and run System File Checker; reset the Windows Update cache only if those repairs fail. These steps are designed to preserve personal files, but back up important documents before making system-level changes.

What error 0x80073712 means and whether these fixes fit your PC

0x80073712

The error commonly appears when Windows 10 or Windows 11 is downloading, installing, or completing a cumulative update, feature update, language pack, or optional component. It usually points to a missing or corrupted file in the Windows component store, also called the WinSxS store, or to damaged files in the local Windows Update cache.

These steps apply to a normally working Windows 10 or Windows 11 installation where you can sign in and open an elevated Command Prompt. You need an account with Administrator permission for the troubleshooter and repair commands. If Windows cannot boot normally, use Windows Recovery Environment or an in-place repair approach instead of repeatedly retrying Windows Update.

Repeated low-disk-space warnings, disk errors, unexplained crashes, disabled security software, browser redirects, or new unknown programs suggest a separate problem. Address that problem first; these steps are less likely to solve a failing drive, severely insufficient storage, malware, or an installation modified heavily with third-party system tools.

Do these safe checks before repairing Windows

These checks are reversible and do not alter Windows system files. Save open work, back up important files, and plan for at least one restart.

1. Restart the PC from Start > Power > Restart. A pending restart can prevent an update from completing.
2. Check free space on the Windows drive, usually C:. Open Settings and review the storage summary. Remove only files you recognize, or use Storage Sense. Leave extra room beyond the update's stated requirement because Windows needs working space while it stages and rolls back an update.
3. Disconnect nonessential USB storage, printers, docks, cameras, and other peripherals. Keep the keyboard, mouse, display, network connection, and any device required to use the computer.
4. Check the clock and time zone. Open Settings and go to the date and time settings, then enable automatic time and automatic time-zone options if they are appropriate for your location.
5. Run the built-in Windows Update troubleshooter. The layout differs by release, but the path is generally:

Settings > System > Troubleshoot > Other troubleshooters > Windows Update > Run

On some Windows 10 installations, use:

Settings > Update & Security > Troubleshoot > Additional troubleshooters > Windows Update

Apply any suggested fix and restart if Windows requests it. If the troubleshooter reports that it repaired a problem, try Windows Update before moving on. If it finds nothing, continue with DISM and SFC.

Repair Windows in this order with DISM and SFC

DISM repairs the component store that Windows uses as a source for protected system files. SFC then checks and replaces damaged protected files using that repaired store. Run every command in an Administrator Command Prompt, not a normal Command Prompt.

1. Open Start, type Command Prompt, right-click it, choose Run as administrator, and approve the User Account Control prompt.
2. Check whether DISM detects a marked problem.

DISM /Online /Cleanup-Image /CheckHealth

A message saying that no component store corruption was detected does not rule out a repairable problem. Continue with the deeper scan.

3. Perform a deeper scan.

DISM /Online /Cleanup-Image /ScanHealth

This can take time and may appear to pause at a percentage. Let it finish. If it reports corruption that can be repaired, run the repair command.

4. Repair the component store.

DISM /Online /Cleanup-Image /RestoreHealth

DISM normally obtains replacement files through Windows Update. A successful result typically says that the restore operation completed successfully and that the operation completed successfully. Restart Windows even if the command reports that no corruption was found.

5. Run System File Checker after DISM finishes.

sfc /scannow

Wait until verification reaches 100 percent. These results have different meanings:

• Windows Resource Protection did not find any integrity violations: SFC found no damaged protected files.
• Windows Resource Protection found corrupt files and successfully repaired them: restart and test Windows Update.
• Windows Resource Protection found corrupt files but was unable to fix some of them: run DISM again, restart, and run SFC once more.

If RestoreHealth reports that source files could not be found, use installation media that matches the installed Windows edition and is as close as possible to the installed version and build. Mount a current Windows ISO, note its drive letter, and check whether it contains install.wim or install.esd in the sources folder. The image index depends on the edition, so identify the correct one before using the command.

DISM /Get-WimInfo /WimFile:D:\sources\install.wim

Replace D: with the mounted media's drive letter. Then use the matching index. For a WIM source, the pattern is:

DISM /Online /Cleanup-Image /RestoreHealth /Source:wim:D:\sources\install.wim:INDEX /LimitAccess

Replace INDEX with the number for your edition. If the media contains install.esd, use this form instead:

DISM /Online /Cleanup-Image /RestoreHealth /Source:esd:D:\sources\install.esd:INDEX /LimitAccess

An incorrect edition, index, drive letter, or build can produce another source error. Do not guess the index or use media from a different Windows release if you can avoid it. After DISM succeeds, run sfc /scannow again, restart, and try Windows Update. If DISM still cannot find valid source files, continue to the verification and next-step guidance rather than repeatedly running the same command.

Try the Windows Update reset only if the repairs did not work

A damaged update cache can keep producing 0x80073712 after DISM and SFC have completed. Resetting it stops update-related services and renames two working folders so Windows can create fresh ones. You need Administrator permission, and every command must be entered accurately.

Back up important files before changing system services. This procedure does not delete your personal documents, but interrupting a servicing operation or changing an unrelated command can create additional problems. Do not use it while an update is actively installing.

1. Open Command Prompt with Run as administrator.
2. Stop the services used by Windows Update and its cryptographic checks.

net stop bits
net stop wuauserv
net stop appidsvc
net stop cryptsvc

If a service says it was not started, continue. If Windows says access is denied, close the window and reopen Command Prompt as Administrator.

3. Rename the update data folders. Renaming is safer than deleting because the old folders remain available if you need to inspect them.

ren %systemroot%\SoftwareDistribution SoftwareDistribution.old
ren %systemroot%\System32\catroot2 catroot2.old

If a folder is in use, confirm that all four stop commands completed. A folder with an existing .old name may also require a different temporary name, such as SoftwareDistribution.previous; type the new name consistently.

4. Start the services again.

net start bits
net start wuauserv
net start appidsvc
net start cryptsvc

5. Restart the PC. Windows will create new SoftwareDistribution and catroot2 folders as needed. Do not manually delete the old folders immediately; keep them until Windows Update works, then remove them only if you need the disk space and the renamed folders are no longer needed.

How to confirm the error is gone and what to do next

After the restart, run Windows Update again from Settings. Let the scan finish and allow Windows to restart if it requests one.

Windows 11: Settings > Windows Update > Check for updates
Windows 10: Settings > Update & Security > Windows Update > Check for updates

The repair worked if the update downloads and installs without 0x80073712 and the update history shows it as successfully installed. If the update fails again, record the update's knowledge-base number, the exact error, and whether DISM or SFC reported unrepaired corruption.

If only one update continues to fail, you can search the Microsoft Update Catalog for that update's knowledge-base number and install the package that matches your Windows version and system architecture. Avoid installing a package merely because its number looks similar.

If several updates fail, DISM still cannot find valid source files, or Windows has other corruption symptoms, use an in-place repair install. Start compatible Windows installation media from within the running Windows desktop, choose the option to keep personal files and apps, and follow the setup prompts. Confirm the selected keep option before proceeding; booting from the media and choosing a clean installation is a different process and can remove data.

Contact Microsoft Support when the error persists after a correctly matched repair source and an in-place repair, when the PC is managed by an organization, or when storage, malware, or hardware faults may be involved. Provide the error code and the steps already completed so support can avoid repeating them.

Conclusion

Run the safe checks first, then DISM followed by SFC. Reset the Windows Update folders only after those repairs fail. If the same update still returns 0x80073712, use an in-place repair install with personal files and apps selected, or contact Microsoft Support when the problem persists or points to hardware, malware, or organizational management.

Frequently Asked Questions

Will fixing error 0x80073712 delete my personal files?

The checks, DISM, SFC, and Windows Update cache reset are intended to leave personal files alone. Back up important files first. For an in-place repair install, verify that setup is set to keep personal files and apps; do not choose a clean installation unless you have deliberately backed up and accepted data removal.

Should I run SFC before DISM?

No. Run DISM first, then `sfc /scannow`. DISM repairs the component store that SFC may need when replacing damaged protected system files.

What if DISM says the source files could not be found?

Use matching Windows installation media and specify the correct `install.wim` or `install.esd` source with the correct image index. An incorrect edition, build, drive letter, or index can cause the same message. After DISM succeeds, run SFC again, restart, and try Windows Update.