Install Error 0x800f081f: What CBS_E_SOURCE_MISSING Means and How to Fix It in 2026

When a Windows update fails, the Windows Update screen displays one of these messages — and you are not alone if any of these look familiar:

“Install error – 0x800f081f”

“Installation Failure: Windows failed to install the following update with error 0x800f081f”

“Error: 0x800f081f — The source files could not be found”

“Error 0x800f081f” in Windows Update history next to a failed KB number.

All four messages point to exactly the same problem. Whether Windows Update shows it as “install error – 0x800f081f,” “error 0x800f081f,” or just the bare code “0x800f081f,” the meaning is identical — and so is the fix.

Windows Update error 0x800f081f means Windows cannot find the source files required to service or repair the operating-system image. Microsoft defines it as CBS_E_SOURCE_MISSING — the Component-Based Servicing stack found corruption or an incomplete component but could not resolve a usable source for the replacement payload.

The good news: 90 percent of 0x800f081f windows update failures resolve within the first three fixes, and none of them risk your personal files.

The tricky part: this error appears in three distinct scenarios — during Windows Update, when DISM itself fails, and when enabling .NET Framework 3.5. Each scenario has a different primary fix, and applying the wrong one wastes time.

This guide explains every scenario, every root cause, and every fix in the correct order.

What Does Error 0x800f081f Mean?

Microsoft classifies the code as CBS_E_SOURCE_MISSING: the Component-Based Servicing stack found corruption or an incomplete component but could not resolve a usable source for the replacement payload.

The install error 0x800f081f is not about a download failure. The update files may have downloaded successfully — the problem is that the files CBS needs to stage and commit them exist in neither the local component store nor any accessible repair source.

The Component-Based Servicing system — CBS — manages how Windows installs updates, enables features, and repairs itself. It works by staging component files and manifests in the WinSxS folder, then committing them to their final locations. When CBS cannot find a required source file to complete this process, the entire operation fails with error: 0x800f081f.

Three Scenarios Where 0x800f081f Appears

Understanding which scenario applies to you is the most important step — because the primary fix differs for each one.

Scenario 1 — Windows Update Failing With 0x800f081f

The most common scenario. You open Windows Update, an update is downloading or installing, and it fails with 0x800f081f in the update history.

This happened repeatedly across 2026 updates including KB5083769 in April, KB5094126 in June, and other cumulative updates. Microsoft also acknowledged a specific wave of these failures in late 2025 tied to its own cleanup processes.

Microsoft’s 2025 acknowledgment: The cumulative update failure might be accompanied with error code 0x800F081F (CBS_E_SOURCE_MISSING). This issue has been identified to be caused by missing language packs and feature payloads required for cumulative updates, resulting from ACR (Automatic Component Repair) and MCR (Manual Component Repair) cleanup processes, leading to update failures.

ACR and MCR are Windows background processes that remove what they determine to be unnecessary component payloads. In a documented 2025 case, these processes incorrectly removed language packs and feature payloads that were still needed for future cumulative updates. The result was 0x800f081f for those missing payloads when the next update tried to reference them.

Scenario 2 — DISM /RestoreHealth Itself Returns 0x800f081f

The second scenario. You run DISM /Online /Cleanup-Image /RestoreHealth to repair a different problem — and DISM itself fails with the same error and the message: “The source files could not be found.”

This is DISM telling you it cannot reach a valid repair source. It tried to download replacement files from Windows Update, could not reach them or verify them, and failed.

Common causes of this specific DISM failure:

The PC has no internet connection or Windows Update access is blocked by a firewall, proxy, or Group Policy.

The PC was using WSUS and the WSUS server does not have the required repair content for the current build.

Someone added /LimitAccess to the DISM command — a common self-inflicted failure. A common mistake is adding /LimitAccess to the first command: that switch explicitly prevents DISM from checking Windows Update, removing its default repair source.

The local component store is so deeply corrupted that even the online repair source cannot reconcile it.

Scenario 3 — .NET Framework 3.5 Installation Failing With 0x800f081f

The third scenario. You try to enable .NET Framework 3.5 through Windows Features, or DISM tries to install it as a dependency, and it fails with 0x800f081f.

.NET Framework 3.5 is not fully included in Windows 11 by default — it requires downloading payload files either from Windows Update or from a Windows installation ISO. When .NET 3.5 payload cannot be sourced from Windows Update — due to a restricted environment, a WSUS limitation, or a missing feature payload — 0x800f081f appears.

This is a separate root cause from component store corruption. It needs a different fix: pointing DISM at an ISO source explicitly for the .NET 3.5 payload.

Error Code Comparison

Error Code	Name	Core Issue	Primary Fix
0x800f081f	CBS_E_SOURCE_MISSING	Repair source not found	DISM online, then ISO
0x80073712	CBS_E_COMPONENT_STORE_CORRUPT	Store itself corrupted	DISM /RestoreHealth
0x80070643	ERROR_INSTALL_FAILURE	Installation failure	WinRE partition or .NET repair
0x80070002	ERROR_FILE_NOT_FOUND	Cache file missing	Cache reset + date/time
0x800f0922	—	EFI partition full	ESP font file deletion
0x80244022	WU_E_PT_HTTP_STATUS_SERVICE_UNAVAIL	Server unavailable	Network/proxy fix

The distinction between 0x800f081f and 0x80073712 is the most important. 0x80073712 means the component store itself is corrupted — DISM is the primary fix. 0x800f081f means the store tried to repair but could not find its source files — a working repair source is the fix.

How to Diagnose — Read CBS Log First

CBS log location: C:\Windows\Logs\CBS\CBS.log

Open it in Notepad. Press Ctrl+F and search for 0x800f081f. The entries around that point tell you what specifically was missing.

Look for these patterns:

CBS_E_SOURCE_MISSING with a specific package name — identifies which component triggered the failure. Note the package name for targeted repair.

The source files could not be found in DISM.log at C:\Windows\Logs\DISM\dism.log — confirms DISM cannot reach a repair source. This is Scenario 2.

Failed to get feature payloads or language pack references — suggests the ACR/MCR cleanup issue Microsoft acknowledged. Installing the latest available cumulative update is the fix.

Every Fix — In Order

Fix 1 — Restart Twice

Start with two reboots and the Windows Update troubleshooter. Wait a couple of minutes each time for background services to fully start before checking Windows Update again.

Some 0x800f081f errors are caused by a Windows servicing operation in a stuck state — the CBS stack is mid-operation from a previous failed attempt and cannot start cleanly until that operation is cleared by a restart.

Restart once. Wait two minutes. Check Windows Update. If the error persists, restart again. If it clears, no further action is needed.

Fix 2 — Run Windows Update Troubleshooter

Go to Settings, System, Troubleshoot, Other troubleshooters. Run Windows Update. The troubleshooter checks for service failures, stuck operations, and registry issues that can interfere with the CBS stack’s source resolution. Apply any fixes suggested and restart before retrying the failed update.

Fix 3 — Run SFC First

Before running DISM, run System File Checker to repair any protected system files that might be preventing CBS from finding its sources:

cmd

sfc /scannow

Wait for the scan to reach 100 percent. Restart afterward and retry the failed update. In some cases this alone resolves 0x800f081f by repairing the system files the CBS stack uses to locate repair sources.

Fix 4 — Run DISM CheckHealth and ScanHealth

Before the full DISM repair, run the diagnostic commands to understand the component store’s state:

cmd

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

/CheckHealth reports whether DISM has already flagged the image as corrupted and whether it is considered repairable. /ScanHealth performs a more extensive scan and can take longer but gives you a definitive answer on component store corruption.

If ScanHealth reports the image as repairable, proceed to Fix 5. If it reports the image as not repairable, the in-place repair in Fix 8 is the correct path.

Fix 5 — DISM RestoreHealth Online (No LimitAccess)

Run DISM’s online repair — without /LimitAccess. This is the most important fix for both Scenario 1 and Scenario 2:

cmd

DISM.exe /Online /Cleanup-Image /RestoreHealth

Critical note: Do not add /LimitAccess to this command. The practical order matters. Start by letting DISM contact Microsoft Update with no custom source. Only point DISM at installation media after the default repair fails or when the PC is intentionally blocked from Microsoft Update.

Adding /LimitAccess on the first attempt is a common mistake that blocks DISM from downloading required repair files from Windows Update — making it fail for a self-imposed reason rather than a genuine source problem.

Wait for DISM to reach 100 percent. This can take 15 to 30 minutes. Restart afterward, run SFC again, then retry Windows Update.

Fix 6 — DISM With ISO Source (When Online DISM Fails)

If Fix 5 fails with “The source files could not be found,” the online repair source is unavailable or incompatible. Mount a Windows installation ISO that matches your exact OS version and edition, then run DISM pointing at that local source.

Step 1 — Download the correct ISO:

Download the Windows 11 ISO from Microsoft’s official software download page. Ensure it matches your exact Windows 11 version (24H2 or 25H2), edition (Home, Pro, Enterprise), language, and architecture (x64 or ARM64). Using an ISO from a different edition, language, architecture, or substantially older servicing level is a common cause of this specific DISM command also failing.

Step 2 — Mount the ISO:

Double-click the downloaded ISO to mount it. Note the drive letter assigned — for example, D:.

Step 3 — Run DISM with the mounted ISO as source:

cmd

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

Replace D: with your actual mounted ISO drive letter. The /LimitAccess flag is appropriate here — it prevents DISM from going to Windows Update and forces it to use your local ISO source exclusively.

Step 4 — Run SFC after DISM completes:

cmd

sfc /scannow

Restart and retry Windows Update.

Fix 7 — .NET Framework 3.5 From ISO (Scenario 3 Specific)

If 0x800f081f is appearing specifically when trying to install .NET Framework 3.5, use the ISO source approach specifically for .NET 3.5:

Mount the Windows 11 ISO as described in Fix 6. Then run:

cmd

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

Replace D: with your mounted ISO drive letter. The /source points specifically to the sxs subfolder which contains .NET 3.5 installation files.

After installing .NET 3.5 successfully, retry the original Windows Update that was failing.

Fix 8 — Reset Windows Update Cache

After DISM completes but before trying Windows Update again, reset the update cache to clear any corrupted downloaded files that might re-trigger the error:

cmd

net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old
net start msiserver
net start bits
net start cryptSvc
net start wuauserv

Restart and check Windows Update.

Fix 9 — In-Place Repair Upgrade

For Windows 11 cumulative and security updates that repeatedly fail with 0x800f081f — including when using the standalone .msu from the catalog — the supported next step is to repair the underlying Windows component store and servicing stack by reinstalling the current Windows build in-place.

Via Windows 11 Settings (easiest method):

Go to Settings, System, Recovery. Look for the option to Reinstall Windows or Fix problems using Windows Update. This reinstalls the current Windows version while keeping apps and data.

After the repair completes and the system restarts, go to Settings, Windows Update and run Check for updates. Let Windows download and install the previously failing update again.

Via ISO (if Settings method is not available):

Download the Windows 11 ISO for your version. Mount it and run setup.exe. Choose Upgrade this PC now with Keep personal files and apps selected. The setup reinstalls Windows over itself, completely rebuilding the component store and servicing stack.

If the error persists after an in-place repair, collect logs and contact Microsoft Support, as persistent 0x800f081f can indicate deeper component store corruption that requires advanced analysis.

Quick Fix Decision Table

Your Situation	Start With
Error appeared once, first time	Fix 1 — Restart twice
Error with Windows Update only	Fix 2, then Fix 4, then Fix 5
DISM /RestoreHealth returning 0x800f081f	Fix 6 — DISM with ISO source
.NET 3.5 failing with 0x800f081f	Fix 7 — .NET 3.5 from ISO
DISM ScanHealth shows “not repairable”	Fix 9 — In-place repair upgrade
Affected by 2025 ACR/MCR cleanup	Install latest cumulative update
All DISM and SFC fixes failed	Fix 9 — In-place repair upgrade

2026 Updates That Triggered 0x800f081f

Several specific 2026 updates generated widespread 0x800f081f reports.

KB5083769 — April 14, 2026 Patch Tuesday — generated 0x800f081f reports on Windows 11 24H2 and 25H2 devices with pre-existing component store issues. Manual .msu installation from the catalog also failed for affected users, confirming the component store rather than the download was the problem.

KB5094126 — June 9, 2026 Patch Tuesday — confirmed 0x800f081f failures on ARM64 Windows 11 25H2 devices. Microsoft Q&A threads from June 2026 confirm this specifically and the resolution involved the DISM /RestoreHealth command sequence followed by in-place repair for stubborn cases.

The August 2026 update — KB5121003 — also generated error reports with similar CBS component store error patterns, addressed by the standard DISM component cleanup sequence.

The ACR/MCR Cleanup Story — Microsoft’s Own Processes Caused It

For context on what caused the 2025 wave of 0x800f081f errors that continued affecting systems through 2026:

Automatic Component Repair and Manual Component Repair are Windows background processes that clean up what they determine to be unused component store payloads. In a specific period through late 2025, these processes incorrectly identified language pack payloads and feature payloads as removable — and removed them from the component store.

When the next cumulative update arrived and needed to reference those payloads during installation, they were gone. Result: CBS_E_SOURCE_MISSING — 0x800f081f.

Microsoft acknowledged the issue on October 15, 2025, and fixed it in the KB5067036 October 2025 optional preview update. Systems that installed KB5067036 or any subsequent update that included its fix no longer experience this specific trigger.

For systems that missed KB5067036 and are still running on builds from before October 2025, the missing payloads may still be absent. In those cases the DISM ISO repair in Fix 6 or the in-place upgrade in Fix 9 is the correct resolution.

Frequently Asked Questions