Fix Windows Update Error 0x800f081f — DISM Source Files Could Not Be Found

Windows Update or the Deployment Image Servicing and Management (DISM) tool may fail with error 0x800f081f. This can happen while installing updates, enabling optional features or repairing Windows system components.

A typical DISM failure looks like:

Error: 0x800f081f

The source files could not be found.

Use the "Source" option to specify the location of
 the files that are required to restore the feature.

This guide explains how to investigate the cause and repair Windows without immediately resorting to a clean installation.

What does 0x800f081f mean?#

The error corresponds to:

CBS_E_SOURCE_MISSING

CBS stands for Component-Based Servicing. Windows stores components required for servicing and repair in its component store, mainly under C:\Windows\WinSxS.

When Windows needs replacement files for a damaged or missing component, DISM attempts to find a suitable repair source. Error 0x800f081f indicates that the required source files could not be located.

Possible reasons include:

• Missing or corrupted component-store files.
• An unavailable or unsuitable repair source.
• Windows Update access being blocked or unavailable.
• Group Policy controlling optional component installation and repair.
• Repair media missing the required component versions.
• Windows edition, version, language or servicing-level differences between the installation and the source.

An update failing with 0x800f081f and DISM itself returning 0x800f081f are related but not identical situations. Check the actual failing operation and its logs before assuming which component is missing.

Step 1 — Identify your Windows version and build#

Press Windows + R, type:

winver

Record the Windows edition, version (for example 24H2 or 25H2), language and OS build.

Alternatively, run PowerShell:

Get-ComputerInfo |
  Select-Object WindowsProductName, WindowsVersion, OsBuildNumber

These details matter if you later use a Windows ISO as a repair source. An ISO for another Windows release may lack the required component files.

Step 2 — Check the component store#

Open Command Prompt as Administrator.

First, check the component store's existing health state:

DISM /Online /Cleanup-Image /CheckHealth

Then perform a more detailed scan:

DISM /Online /Cleanup-Image /ScanHealth

The scan may take several minutes. Possible results include:

• No component store corruption detected: Investigate update-specific errors and other causes if Windows Update still fails.
• The component store is repairable: Continue with DISM repair.
• The component store cannot be repaired: Consider a supported Windows repair or recovery method after backing up important data.

Step 3 — Attempt a normal DISM repair#

In the elevated Command Prompt, run:

DISM /Online /Cleanup-Image /RestoreHealth

When system policy permits, DISM can use Windows Update as a source of repair components.

If the operation succeeds, you should see a message similar to:

The restore operation completed successfully.

Then proceed to System File Checker below.

What if DISM returns 0x800f081f?#

If DISM says The source files could not be found, Windows could not obtain all required files from its configured sources.

Check network connectivity, Windows Update access and repair-source policy before concluding that Windows needs reinstalling.

Step 4 — Run System File Checker#

Run:

sfc /scannow

SFC checks protected Windows system files and attempts to repair them. Example outcomes:

• Windows Resource Protection did not find any integrity violations: No protected system-file corruption was detected.
• Windows Resource Protection found corrupt files and successfully repaired them: Corrupted files were replaced.
• Windows Resource Protection found corrupt files but was unable to fix some of them: Some problems remain. A successful DISM repair may allow SFC to complete on a subsequent run.

Restart Windows when appropriate and retry the Windows Update or feature installation that originally failed.

Step 5 — Check whether Windows Update is an available repair source#

Windows repair behaviour can be controlled by local or domain Group Policy.

Open the Group Policy Editor where available (gpedit.msc) and navigate to:

Computer Configuration → Administrative Templates → System

Review Specify settings for optional component installation and component repair.

A configured policy can direct servicing to a network repair share or prevent Windows Update from providing certain files.

On a business-managed PC, don't change these settings without consulting the administrator managing Windows Update, WSUS or your device's servicing policy.

On a personal PC, check that Windows Update is available, then try the built-in troubleshooter:

Settings → System → Troubleshoot → Other troubleshooters → Windows Update

Some Windows 11 versions launch the troubleshooter through the Get Help app.

When you've corrected any source configuration or update connectivity issue, retry:

DISM /Online /Cleanup-Image /RestoreHealth

Step 6 — Use compatible Windows installation media as a repair source#

When Windows Update cannot supply the files, DISM can use compatible Windows installation media.

Download an official Windows 11 ISO:

https://www.microsoft.com/software-download/windows11

Choose media that matches the installed Windows version, architecture, edition and language and includes the required component versions.

Important: The same Windows edition is not enough by itself. If the installed system has newer servicing updates than the ISO, the source may still lack the required files. A properly serviced repair source may be necessary.

Mount the ISO#

Right-click the ISO file in File Explorer and select Mount.

Note the drive letter (for example D:). Open:

D:\sources

Look for either install.wim or install.esd.

Identify the correct Windows image index#

If the ISO contains a WIM file:

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

If it contains an ESD file:

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

Find the image index corresponding to your installed Windows edition. The example index 6 below is only illustrative; do not assume that Windows 11 Pro is always index 6.

Repair from install.wim#

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

Replace D: and 6 with your actual ISO drive letter and correct image index.

Repair from install.esd#

If your DISM version supports an ESD source, you can specify:

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

If the ESD syntax isn't accepted by your DISM version, export the matching edition to a WIM using the supported DISM /Export-Image operation, then reference that WIM.

/LimitAccess prevents DISM from contacting Windows Update while repairing. If the local source is incomplete, leaving it out may allow an additional Windows Update source, if policy allows.

If the ISO repair still fails#

Check:

1. The correct drive letter, image path and edition index.
2. The installed Windows version, architecture and language.
3. Whether the source has the servicing level and optional components required.
4. Whether Group Policy blocks or redirects sources.
5. The DISM and CBS logs for the exact missing component.

Don't repeatedly try random ISOs. If no suitable source is available, a supported repair reinstall may be more reliable.

Step 7 — Repair Windows 11 without removing apps and files#

Windows 11 includes a repair option designed to reinstall the current Windows version while retaining installed applications, personal files and settings.

Navigate to:

Settings → System → Recovery → Fix problems using Windows Update → Reinstall now

Follow the instructions. The system typically downloads the required repair installation using Windows Update.

Microsoft describes this procedure as preserving files, applications and settings. Back up important data before any major recovery operation nonetheless.

If the option is missing, it may be unavailable for your Windows version or disabled by organisational device-management and Windows Update policies. Speak to your IT administrator on a managed PC.

Step 8 — Investigate the Windows servicing logs#

Useful log locations:

C:\Windows\Logs\DISM\dism.log
C:\Windows\Logs\CBS\CBS.log

To search recent DISM entries from PowerShell:

Select-String -Path "$env:windir\Logs\DISM\dism.log" `
  -Pattern "0x800f081f", "error" |
  Select-Object -Last 30

To search the CBS log:

Select-String -Path "$env:windir\Logs\CBS\CBS.log" `
  -Pattern "0x800f081f", "CBS_E_SOURCE_MISSING" |
  Select-Object -Last 30

Look for package identities, failed component operations and missing repair-source messages close to the time of the failure.

Log entries need context. An isolated line containing error does not necessarily identify the root cause.

Step 9 — Confirm the original issue is fixed#

After repairing Windows, restart and run:

DISM /Online /Cleanup-Image /CheckHealth
sfc /scannow

Then:

1. Open Settings → Windows Update.
2. Click Check for updates.
3. Retry the update or Windows feature installation that originally failed.
4. Check Update history and verify that installation succeeds.

A successful DISM command alone does not guarantee that the original update error has been resolved.

Common questions#

Is Windows permanently corrupted?#

Usually not. 0x800f081f often indicates a missing repair source rather than an irreparable Windows installation.

Should I delete WinSxS?#

No. The WinSxS component store is essential to Windows servicing. Manually removing its files can cause further corruption.

Will DISM remove my personal files?#

The standard /RestoreHealth operation repairs Windows components; it is not intended to remove personal files. Keep a backup before system recovery work.

Can I use any Windows 11 ISO?#

No. A repair source must contain the required component versions for the installed system. Version, language, edition and servicing-level mismatches can prevent a repair.

Should I immediately delete SoftwareDistribution?#

No. Windows Update cache resets are useful for some update failures, but 0x800f081f specifically relates to missing servicing source files in many cases. Use the error context and logs to decide which repair is appropriate.

Summary#

If Windows Update or DISM returns 0x800f081f:

1. Check Windows version and build.
2. Inspect component-store health with DISM.
3. Try /RestoreHealth, then sfc /scannow.
4. Confirm Windows Update and repair-source policies permit repair downloads.
5. If necessary, provide compatible Windows installation media.
6. Consider Windows 11's repair reinstall option when servicing remains broken.
7. Re-test the original failing update or feature installation.

The key is to identify which repair files Windows needs and provide a valid source for them.

References#

• Microsoft — Repair a Windows Image
• Microsoft — Configure a Windows Repair Source
• Microsoft — Repair-WindowsImage PowerShell documentation
• Microsoft — Fix issues by reinstalling the current version of Windows
• Microsoft — Download Windows 11