Fix error 0x800f081f
0x800f081f is CBS_E_SOURCE_MISSING: the source for a package or file was not found. It shows up when a Windows update meets a damaged component store, or when DISM or Windows Features cannot find files for .NET Framework 3.5. Run DISM with RestoreHealth while online, then sfc /scannow, and if DISM fails again give it a source from matching Windows media.
Checked November 10, 2026 against the manufacturer's own pages.
The short version
What to install and where it comes from. Every link goes to the manufacturer or Microsoft, never to a copy.
Official files only, nothing bundled
Step by step
Note what you were doing when it failed
If the code came from Settings, Windows Update, the component store is the suspect. If it came from Turn Windows features on or off while adding .NET Framework 3.5, the feature files are the suspect. The fixes differ, so start with the matching step.
Repair the store from Windows Update
Open Terminal (Admin) from the Start button's right-click menu and run DISM.exe /Online /Cleanup-image /Restorehealth. With a working internet connection DISM downloads replacement files itself. Then run sfc /scannow and restart.
Check that DISM really finished
Open C:\Windows\Logs\CBS\CBS.log and read the Summary block near the end. Operation result 0x800f081f with Total Repaired lower than Total Detected means DISM found damage it could not replace from its source.
Point DISM at a matching repair source
Microsoft's syntax is DISM /Online /Cleanup-Image /RestoreHealth /Source: followed by the path to a Windows folder from the same build, then /LimitAccess so DISM uses only that source. The build must match yours exactly.
For .NET Framework 3.5, install from the ISO
Create an ISO with Microsoft's Media Creation Tool, double-click it to mount it, and run Dism /online /enable-feature /featurename:NetFx3 /All /Source:D:\sources\sxs /LimitAccess, changing D: to the mounted drive letter.
Install the update again
Go back to Settings, Windows Update and choose Check for updates. If the same update still fails, its KB number in Update history lets you fetch it from the Microsoft Update Catalog.
Faster option: let a PC tool do the clean-up
The steps above fix this error. Errors like this often come back on a PC full of junk files, broken registry entries and leftovers from removed programs. A maintenance tool clears those in one scan.
Scan and clean up Windows
Finds junk files, invalid registry entries, startup slowdowns and privacy traces, then fixes them in one click.
Auslogics BoostSpeed 14 · Free version · Windows 11, 10, 8, 7 · 30-day refund on Pro
Two different jobs, one error code
Windows keeps every system component in the component store, the WinSxS folder. Updates and optional features are both installed by the servicing stack (CBS), and both need source files. When CBS asks for a file and cannot find a usable copy anywhere it is allowed to look, it stops with CBS_E_SOURCE_MISSING. That is why the same code appears in two places that look unrelated: a cumulative update in Windows Update, and the .NET Framework 3.5 checkbox in Windows Features.
How the .NET Framework 3.5 case differs
In Windows 10 and 11, .NET Framework 3.5 is a Feature on Demand. Windows ships its metadata but not its binaries, so turning it on means downloading them. Microsoft lists three reasons for 0x800f081f in this case: the source path does not hold the needed files, the account lacks read access to them, or the file set is damaged or for another Windows version. A fresh ISO of your exact version with the sources\sxs folder solves all three.
Less common: a missing package that DISM cannot rebuild
Sometimes CBS.log shows “CBS MUM Missing” for a package from an older update. Microsoft’s advanced guide maps the build number in that line to a KB number in the Windows release history, downloads that KB from the Update Catalog, extracts it, and runs RestoreHealth with /Source pointing at the extracted files. It is slower, but it works when online repair keeps failing.
Questions
Why does DISM itself return 0x800f081f?
DISM reports this code when it cannot find good copies of the damaged files. Its default source is Windows Update, so a blocked connection, a WSUS-managed PC or a damaged package that Windows Update no longer offers all lead here.
Can I use any Windows 11 ISO as the source?
No. Microsoft says the repair source must be the same operating system version. An ISO for a different build or language often produces the same error again.
My work PC gets 0x800f081f adding .NET 3.5. Why?
Managed PCs often get updates from WSUS, which may not carry feature files. Microsoft's fix is the Group Policy setting Specify settings for optional component installation and component repair, set by your IT team.