Windows Update Error 0x800f081f? The Proven DISM Fix

By Ahmet Tolga KAYA 8 min read
Windows Update Error 0x800f081f? The Proven DISM Fix

Windows Update error 0x800f081f is one of those failures that looks scary and usually is not. The update stops, the progress bar disappears, and Windows Update history shows a failed install with that code. Underneath, the message is simple: Windows tried to repair or add something and could not find the source files it needed. This guide walks through how I approach it, from reading the logs to repairing the component store with DISM, and what to check when the machine is managed by Group Policy or WSUS.

What Windows Update Error 0x800f081f Actually Means

The code 0x800f081f maps to CBS_E_SOURCE_MISSING. The servicing stack found a component that needed repair, then looked for the payload and came back empty. When you run DISM yourself, the same problem shows up as the message 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.

That wording is the whole story. By default, DISM uses Windows Update as the repair source. If Windows Update is blocked, redirected by policy, or simply cannot supply the exact files for your build, DISM has nowhere to get them. So the Windows Update error 0x800f081f you see in the update history and the DISM source error are two views of the same root cause: a damaged component store with no reachable repair source.

Windows Update error 0x800f081f: DISM reports the source files could not be found (illustration)

The screenshot above is an illustration of the typical output, not a capture from a specific machine. The line to remember is the last one: DISM writes its details to C:\Windows\Logs\DISM\dism.log.

Step 1: Confirm the Damage and Read the Logs

Before changing anything, find out whether the component store is flagged as damaged. Open an elevated Command Prompt or PowerShell window and run the two checks Microsoft documents for an online image:

DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth

/CheckHealth only reports whether the image was already flagged as corrupted, so it returns quickly. /ScanHealth scans the component store for corruption and takes several minutes. If both come back clean and the update still fails, the problem may sit elsewhere, such as a stuck servicing operation or a pending restart, so reboot once and retry before going further.

If corruption is reported, open the logs. DISM logs to C:\Windows\Logs\DISM\dism.log, and the servicing stack logs to C:\Windows\Logs\CBS\CBS.log. The System File Checker marks its own entries with an [SR] tag, so you can pull just those lines out with a filter instead of scrolling through a huge file:

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log > "%userprofile%\Desktop\sfcdetails.txt"Code language: JavaScript (javascript)

Run that from an elevated prompt, otherwise it often returns nothing. Microsoft explains how to read these entries in its article on CBS.log records that were not repaired by sfc.

Step 2: Run DISM RestoreHealth With a Local Source

This is the fix for the DISM RestoreHealth source files could not be found error, and it solves most cases of Windows Update error 0x800f081f. Instead of letting DISM go to Windows Update, you give it a known-good Windows image on disk. Microsoft describes the pattern as /RestoreHealth /Source: combined with /LimitAccess, where /LimitAccess stops DISM from using Windows Update as a repair source or as a backup source.

The source has to match the installed system. Same Windows version, same build family, and the edition you are repairing. A mismatched ISO is the most common reason this step fails, and I check it before I do anything else. Mount an ISO that matches your build, note the drive letter, and list the indexes inside the image:

Get-WindowsImage -ImagePath D:\sources\install.wimCode language: CSS (css)

Find the index that matches your edition, for example Windows 11 Pro, and use it in the repair. Microsoft documents the WIM form of a repair source with a Wim: prefix followed by the path and the index:

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

Replace the drive letter and the index with your own values. Some ISOs ship an install.esd instead of an install.wim. If that is what you have, point DISM at the file that actually exists in the sources folder, and confirm the syntax in the Microsoft documentation linked in the references before you script it.

Windows Update error 0x800f081f fix steps: check, repair with DISM, review policy, retry

The command takes several minutes, and the progress bar sometimes sits at 20 percent for a while. That is normal. Let it finish rather than cancelling it halfway through.

Step 3: Check the Windows Update Repair Source Group Policy

On a domain-joined PC the repair source is often decided by policy, not by DISM. Microsoft documents the setting under Computer Configuration, Administrative Templates, System as Specify settings for optional component installation and component repair. It controls where Windows looks when it has to restore a feature or repair the operating system.

Windows Update is the default repair source, but the policy can point machines at one or more network locations instead. That is useful in locked-down networks, and it is also a classic way to trigger Windows Update error 0x800f081f. If the configured location no longer exists, does not contain files for the build you run, or Windows Update is not allowed as a fallback, the repair has nothing to use. In my own checklist, this is the second thing I open on any managed machine that fails with this code. The Windows Update repair source Group Policy and the related options are described in Microsoft’s Configure a Windows repair source article.

  • Run gpresult /h C:\Temp\gp.html and check whether the repair source setting is applied to the machine.
  • If a network path is configured, confirm the share still exists and the computer account can read it.
  • If Windows Update is used as a backup source, make sure the firewall and proxy allow access to it.
  • Test the repair with a local source first, so you know whether the policy or the image is the problem.

Step 4: Repair System Files and Retry the Update

Once DISM reports success, run the System File Checker so that damaged system files are replaced from the freshly repaired store, restart the machine, and retry the update:

sfc /scannow
shutdown /r /t 0
Windows Update error 0x800f081f fixed: DISM RestoreHealth and sfc /scannow completed (illustration)

If you want to see how large the component store has become, you can generate a report with DISM /Online /Cleanup-Image /AnalyzeComponentStore. Cleaning up superseded components with /StartComponentCleanup is optional here. Be careful with the /ResetBase switch: Microsoft states that installed Windows updates cannot be uninstalled after you run it, so I do not use it on a machine that is still failing updates.

After the restart, open Windows Update, check for updates and install again. If the error is gone, you are done. If it returns, read the new entries in dism.log and CBS.log, because the failing component may be a different one this time.

Windows Update Error 0x800f081f When Installing .NET Framework 3.5

The same code shows up when you enable an optional feature, with .NET Framework 3.5 being the usual case. The cause is the same: Windows cannot download the feature payload, so you provide it from installation media. Mount an ISO that matches your Windows version, then point DISM at its sources\sxs folder and use /LimitAccess so it does not try to contact Windows Update:

DISM /Online /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:D:\sources\sxs

The syntax follows Microsoft’s documented /Enable-Feature options with /Source and /LimitAccess. A small detail that wastes time: the drive letter needs a colon, so /Source:D:\sources\sxs works and /Source:D\sources\sxs does not.

Troubleshooting: When Windows Update Error 0x800f081f Keeps Coming Back

  • The source image does not match: use an ISO of the same Windows version and build family as the installed system.
  • The wrong index: list the image with Get-WindowsImage and pick the index for your edition.
  • The command still reaches for Windows Update: add /LimitAccess so DISM only uses the source you gave it.
  • Policy keeps overriding the fix: review the repair source Group Policy and any WSUS settings applied to the device.
  • Nothing helps: read the last errors in dism.log, then consider an in-place repair upgrade with matching media, which keeps apps and data.

Read more: SCCM Scan Failed 0x80244022? Fix the WSUS 503 Error Fast

Read more: Install-Module Not Working? Fix NuGet and TLS 1.2 Errors Fast

Read more: Windows 11 26H2 Released: How to Install KB5121794

FAQ

What does Windows Update error 0x800f081f mean?

It maps to CBS_E_SOURCE_MISSING. Windows needed to repair or add a component and could not find the source files, so the update or feature install failed.

How do I fix the DISM error saying the source files could not be found?

Run DISM /Online /Cleanup-Image /RestoreHealth with /Source pointing to a matching install.wim and add /LimitAccess so DISM does not try Windows Update.

Which Windows ISO should I use as the repair source?

Use an ISO with the same Windows version and build family as the installed system, and select the index for the edition you are repairing.

Can Group Policy cause error 0x800f081f?

Yes. The policy Specify settings for optional component installation and component repair controls the repair source. A wrong network path or blocked Windows Update fallback can leave DISM with nothing to use.

Is it safe to run DISM RestoreHealth and sfc /scannow?

Yes. Both are standard repair tools. Avoid the /ResetBase option unless you are sure, because installed updates cannot be uninstalled afterwards.

References

Microsoft Learn: Repair a Windows image

Microsoft Learn: Configure a Windows repair source

Microsoft Learn: DISM operating system package servicing command-line options

Microsoft Learn: CBS.log records that were not repaired by sfc

Ahmet Tolga KAYA

Systems Engineer and Technical Writer focused on Windows, Microsoft technologies, infrastructure, cybersecurity, automation, and platform reliability.