About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
Microsoft documents 0x800F081F as CBS_E_SOURCE_MISSING, with 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." The feature's files are not stored on the server and Windows could not get them from where it looked. Give it a source: the \sources\sxs folder from installation media that matches the server, supplied to DISM or Install-WindowsFeature, or set in Group Policy for the whole estate.
Microsoft describes the feature's files as absent from the server by design, so the error points at where Windows looked for them, not at damage to the server.
What the error means
Microsoft's page explains the design: ".NET Framework 3.5 is a Feature on Demand. The metadata for Features on Demand is included. However, the binaries and other files associated with the feature are not included. When you enable a feature, Windows tries to contact Windows Update to download the missing information." The page names Windows 10 and Windows Server 2012 R2 in that sentence. It does not list later Server releases, so confirm behaviour on yours; the DISM and cmdlet pages below describe the same source mechanism.
Three related codes belong to the same family. 0x800F0906 (CBS_E_DOWNLOAD_FAILURE) is "The source files could not be downloaded": the server cannot reach Windows Update. 0x800F0907 (CBS_E_GROUPPOLICY_DISALLOWED) means "Because of network policy settings, Windows couldn't connect to the Internet to download files". For 0x800F081F, Microsoft ties the error to a source that was specified and did not hold usable files.
Microsoft states when 0x800F081F occurs "when an alternative installation source is specified and one of the following conditions is true": the location "does not contain the files that are required to install the feature"; the user "does not have at least READ access to the location and to the files"; or "the set of installation files is corrupted, incomplete, or invalid for the version of Windows that you are running."
The search order for feature files is documented for Install-WindowsFeature -Source: first the target computer, then the path given as -Source, then the repository path set by the Group Policy "Specify settings for optional component installation and component repair", then Windows Update. That policy "controls the following Windows Registry setting: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\Servicing\LocalSourcePath."
Likely causes
| Cause | What you see | How to confirm |
|---|---|---|
| No source given and Windows Update is unreachable | 0x800F0906, "The source files could not be downloaded" | The DISM log shows the failure; the server has no route to Windows Update |
| Media given, but it is not the right folder | 0x800F081F when /Source is wrong |
\sources\sxs exists at the path you used |
| Media does not match the server | 0x800F081F with a correct path | Compare media edition and version with the server; Microsoft says to use RTM media, not refresh media |
| Server patched higher than the media | Failure with correct media | Microsoft: if the target is patched higher than the source, the feature "may fail" |
| No READ access to a network source | 0x800F081F on a UNC path | Test access to the share as the account, and for the computer account |
| Group Policy forbids downloads | 0x800F0907 | The policy "Specify settings for optional component installation and component repair" is set to never attempt to download |
| WSUS is the only update source | 0x800F0906 | WSUS in use; the "Contact Windows Update directly" option is off |
Prove the cause before changing anything
All of these read only.
Check the feature's state. Microsoft's DISM page documents /Get-FeatureInfo for one feature; the feature name for .NET 3.5 is NetFx3:
Dism /online /Get-FeatureInfo /FeatureName:NetFx3
On Windows Server, the same feature has the name NET-Framework-Core, which Microsoft's .NET Framework 3.5 installation-errors page uses in its Install-WindowsFeature command. The Get-WindowsFeature page documents -Name, so Get-WindowsFeature -Name NET-Framework-Core shows that feature.
Read the DISM log. Microsoft gives its location as C:\Windows\Logs\DISM\dism.log (and %WINDIR%\logs\DISM\dism.log on the deployment page). Read the lines around the failure for the source that was used.
Check the media. Mount or insert the installation media and confirm that \sources\sxs exists on it. Compare its version with the server. If you only have an image file, Microsoft documents Dism /Get-ImageInfo /ImageFile:C:\test\images\install.wim to list indexes.
Check policy. In the Group Policy editor go to Computer Configuration, Administrative Templates, System, and read "Specify settings for optional component installation and component repair". Note whether an "Alternate source file path" is set, whether "Contact Windows Update directly to download repair content instead of Windows Server Update Services (WSUS)" is ticked, and whether "Never attempt to download payload from Windows Update" is ticked.
Fix
Work from one server to many.
One server, with media. Insert or mount the matching installation media. Microsoft's command, with <drive> as the media drive:
Disruptive step: this installs a Windows feature and, if DISM reports Enable Pending, the server must restart before the feature is fully enabled (the DISM page says "you must boot the image in order to enable the feature entirely"). Schedule it. To back out, run Dism /online /Disable-Feature /FeatureName:NetFx3; applications that need .NET 3.5 will stop working.
Dism /online /enable-feature /featurename:NetFx3 /All /Source:<drive>:\sources\sxs /LimitAccess
Microsoft explains the options: /All enables parent features, and /LimitAccess stops DISM contacting Windows Update. Several /Source values can be given; "the files are gathered from the first location where they are found and the rest of the locations are ignored."
One server, with PowerShell. The cmdlet reference documents -Name and -Source. The feature name comes from Microsoft's KB:
Disruptive step: this cmdlet also installs a Windows feature, and a restart can be needed before the feature is fully enabled. Impact: applications on the server see a new feature after the restart, and the restart ends every user's session. Back-out: run the DISM disable command above; applications that need .NET 3.5 will stop working.
Install-WindowsFeature -Name NET-Framework-Core -Source <drive>:\sources\sxs
Microsoft's KB prints this command without the hyphens before name and source; use the parameter names as in the cmdlet reference. For a share, "the computer account of the local computer must have Read permissions on the specified share".
Many servers, through Group Policy. Copy the sources\sxs folder to a share, then set the policy.
Risk: a policy applies to every computer in its scope, and changes how all of them find optional component and repair files. Link it to a test OU first. To back out, set the policy to Not Configured and run gpupdate /force.
Enable "Specify settings for optional component installation and component repair" and enter the share path in "Alternate source file path". Microsoft's example is \\server_name\share\Win8sxs; for a WIM it is WIM:\\server_name\share\install.wim:3, where 3 is the image index. Then run gpupdate /force at an elevated prompt. Microsoft adds that the source should be the right edition and patched: "Only use RTM media" and keep the source current, because a target patched higher than its source can fail.
WSUS-managed servers. Tick "Contact Windows Update directly to download repair content instead of Windows Server Update Services (WSUS)" if your change process allows servers to reach Windows Update for this purpose, or use the alternate source path above.
Risk: the first option lets servers fetch content from the internet outside WSUS approval. To back out, untick it.
0x800F0907. Decide whether "Never attempt to download payload from Windows Update" is intended. If it is, supply the alternate source path.
Risk: changing this policy changes where every server in its scope may fetch optional component and repair files. Impact: a wrong setting leaves servers unable to install features at all. Back-out: record the current setting first and restore it, then run gpupdate /force.
Confirm the fix
Run Dism /online /Get-FeatureInfo /FeatureName:NetFx3 again; the state should be Enabled, or Enable Pending until the restart. After the restart, Get-WindowsFeature -Name NET-Framework-Core should show it installed. Start the application that needed .NET 3.5 and test it.
Example (illustrative): six servers app01 to app06 in CONTOSO on 10.0.20.0/24 have no internet route and fail with 0x800F0906 from Server Manager. The administrator copies sources\sxs from matching media to \\fs01\media\sxs, sets the Group Policy alternate source path to that share, runs gpupdate /force on each server and installs the feature. Each server takes about 5 minutes (2 minutes to install and 3 minutes to restart and check). Six servers at 5 minutes is 30 minutes in one window, with the two busiest servers last.
What to watch afterwards
- After the install, apply your normal patching. Microsoft notes a source older than the server's patch level can be a problem, and the new feature has its own updates.
- Keep the source share in step with the Windows Server version you run, and keep the matching media available.
- If a later cumulative update fails, component store repair with DISM and SFC is a separate fault with its own steps.
- Track which applications depend on .NET 3.5, so that a decision to remove it is informed.
Read next
Related articles you may want next.
- TroubleshootingWindows Cumulative Update Fails: DISM and SFC DiagnosisCumulative update failing with 0x800f0831 or 0x80073712? Read CBS.log, run DISM and SFC scans that do not repair, then choose a repair source that matches.Read article
- Hosting.NET on Windows Server: what Windows Update patches and what it leaves to youWhy a fully patched Windows server can still run an out-of-support .NET runtime: the difference between .NET Framework and modern .NET, how each is updated on Windows Server, what self-contained applications mean for patching, and why .NET 8 and 9 support ended on 10 November 2026.Read article
- HostingReading a patch compliance report: what installed, needed, pending restart, failed and not applicable really meanWhat WSUS patch report statuses mean: installed, not applicable, needed, pending restart, failed and no status, and how to spot a false 'compliant'.Read article
Risks and limits
These commands have not been run or lab-tested.
The Microsoft pages cited do not list error 0x800F0954, so this guidance does not cover it. They also do not give a page-by-page statement for every Windows Server release; the installation errors page names Windows Server 2012 R2, and later releases are covered here only through the DISM, cmdlet and repair-source pages. Do not install a source from media of a different edition or version just to make the error go away. Changing Group Policy or enabling direct Windows Update access affects every server in scope.
Sources
- .NET Framework 3.5 installation errors — Microsoft Learn, page dated 2026-02-12, accessed 18 November 2026
- .NET Framework 3.5 deployment errors and resolution steps — Microsoft Learn, page dated 2024-11-14, accessed 18 November 2026
- Enable or Disable Windows Features Using DISM — Microsoft Learn, page dated 2024-11-25, accessed 18 November 2026
- Configure a Windows Repair Source — Microsoft Learn, page dated 2021-12-15, accessed 18 November 2026
- Install-WindowsFeature — Microsoft Learn, date not shown, accessed 18 November 2026
- Get-WindowsFeature — Microsoft Learn, date not shown, accessed 18 November 2026
This article was originally published on .