What the error means
Microsoft names 0x800f081f CBS_E_SOURCE_MISSING: "The source for the package or file not found." CBS is Component Based Servicing, the part of Windows that installs updates and optional features. When it needs a clean copy of a component and cannot find one, either on Windows Update or in a source folder you pointed it to, it stops with this code.
You can meet the code in three places, and the fix depends on which one:
- Windows Update. Microsoft's Windows 10 update page groups it with corrupted or missing system files or an incomplete download, and its common errors list describes the cause as component store corruption.
- A DISM repair. The
Operation resultline inCBS.logreads 0x800f081f when DISM found damage but had no source to repair it from. - Installing .NET Framework 3.5. Here it usually means the alternate source you gave is missing files, unreadable, or for a different Windows version. Windows shows "The source files could not be found."
Common causes
- A damaged component store, so Windows cannot rebuild a package it needs.
- DISM running on a PC that cannot reach Windows Update, so it has nowhere to fetch clean files from.
- A WSUS-managed PC that is not allowed to fetch repair content from Windows Update.
- A source folder or ISO that is the wrong Windows version, incomplete, or not readable by the installing account.
How to fix it
1. Run System File Checker and the update troubleshooter
This is Microsoft's first fix for the Windows Update case. Open Command Prompt as administrator and run sfc /scannow. Then run the Windows Update troubleshooter: on Windows 10 it is under Settings, Update & Security, Troubleshoot, Additional troubleshooters; on Windows 11 under Settings, System, Troubleshoot, Other troubleshooters. Check for updates again.
2. Repair the component store with DISM
Microsoft's mitigation for component store corruption is DISM followed by SFC, then a restart. Run these in an elevated Command Prompt while the PC is online, because by default DISM fetches replacement files from Windows Update:
Dism.exe /Online /Cleanup-Image /Restorehealth
Sfc.exe /Scannow3. Give DISM a repair source if it cannot reach Windows Update
If DISM itself ends with 0x800f081f, it had no usable source. Microsoft documents pointing it at a working Windows installation of the same version, or at Windows files on a network share, USB drive or DVD. Replace the placeholder with the computer you are copying from:
DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:\\<servername>\c$\windows /LimitAccess/LimitAccess stops DISM from trying Windows Update again. Afterwards, check %windir%\Logs\CBS\CBS.log for any corruption still listed as not repaired.
4. For .NET Framework 3.5, fix the source or the policy
Confirm the source path is correct, for example D:\sources\sxs on mounted installation media, that the installing account has at least Read access, and that the media matches your Windows version. Then install from it:
Dism /online /enable-feature /featurename:NetFx3 /All /Source:D:\sources\sxs /LimitAccessOn WSUS-managed PCs, Microsoft documents enabling the Group Policy setting Specify settings for optional component installation and component repair (Computer Configuration, Administrative Templates, System). Set an Alternate source file path or select the option to contact Windows Update directly, then run gpupdate /force.
5. Repair Windows with an in-place upgrade
For the Windows 11 upgrade case, Microsoft's upgrade errors page suggests creating media with the Media Creation Tool and performing an in-place upgrade from a Windows ISO. This keeps your apps and files while replacing system components. Back up first.
If nothing works
Microsoft's DISM article has an advanced procedure for this exact result: read CBS.log to find the corrupted file and its build number, match the build to a KB number on the Windows update history page, download that update from the Microsoft Update Catalog, extract it to a folder, then run DISM with that folder as /Source. Verify with DISM /Online /Cleanup-Image /ScanHealth. This needs administrator skills, so stop here if you are not comfortable with it.
What we checked
On 2026-11-19 we read five Microsoft pages that mention 0x800f081f: the Windows Update troubleshooting page and the upgrade and installation errors page on support.microsoft.com, and three Microsoft Learn articles covering Windows Update corruption and DISM, common Windows Update errors, and .NET Framework 3.5 installation errors. They agree that the code means a source package or file was not found, and they document SFC, DISM with or without a source, the optional component Group Policy and an in-place upgrade. We read the vendor documentation and did not reproduce the error.
Last checked: 2026-11-19.