Note the exact error code. For step 3 you need a Windows ISO of the same version as your PC, from Microsoft's software download page. If Windows cannot start, see the startup guide.
Work through these checks
0 of 7 complete01Turn on .NET 3.5 in Windows Features
Microsoft's standard way to install .NET 3.5 is enabling it as a Windows feature.
- Press Win + R, type optionalfeatures and press Enter.
- Tick .NET Framework 3.5 (includes .NET 2.0 and 3.0), click OK and choose to let Windows Update download the files.
- Restart if asked.
The feature installs and the program starts.
If it does not helpIf it fails, note the error code: 0x800F0906 (step 2), 0x800F081F (step 3), 0x800F0907 (step 4).
02Check the internet connection and Windows Update
Microsoft explains 0x800F0906 as the computer being unable to download the files from Windows Update.
- Make sure the PC is online, and disconnect any VPN or proxy for the test.
- Open Settings > Windows Update and check for updates; install pending updates and restart.
- Try step 1 again.
Windows downloads the files and the feature installs.
If it does not helpIf Windows Update itself fails, the Windows Update errors overview on this site helps; or install from media in step 3.
03Install from Windows installation media with DISM
Microsoft's method installs .NET 3.5 directly from the sources\sxs folder on the installation media, without Windows Update.
- Right-click the Windows ISO and choose Mount; note its drive letter (for example D:).
- Open Terminal (Admin) and run Dism /online /enable-feature /featurename:NetFx3 /All /Source:D:\sources\sxs /LimitAccess (replace D: with the ISO's letter).
- Wait for "The operation completed successfully" and restart if asked.
.NET Framework 3.5 is installed.
If it does not helpMicrosoft notes that 0x800F081F here means the path lacks the files, you lack read access, or the files do not match your Windows version; use an ISO of the same version.
04Check the optional component group policy
Microsoft explains 0x800F0907 as a policy that never allows downloading the files from Windows Update without an alternative source.
- On Windows Pro, run gpedit.msc and open Computer Configuration > Administrative Templates > System.
- Open Specify settings for optional component installation and component repair, select Enabled, and tick the option to contact Windows Update directly instead of WSUS (or set an alternate source path).
- Click OK, run gpupdate /force in Terminal (Admin), then repeat step 1.
Do not change this policy on a PC managed by your work or school.
The feature installs.
If it does not helpOn Windows Home there is no gpedit; use step 3 instead.
05Repair the component store
A damaged component store can stop optional features from installing.
- In Terminal (Admin), run DISM /Online /Cleanup-Image /RestoreHealth and then sfc /scannow.
- Restart and try step 1 or step 3 again.
DISM completes and the feature installs.
If it does not helpIf DISM fails with 0x800f081f, see the 0x800F081F guide on this site.
06Check whether the program needs a newer .NET
Some programs show a .NET message but actually need a newer .NET version.
- Read the program's message carefully: .NET Framework 3.5 is only for older programs.
- If it asks for .NET Framework 4.8 or for .NET (6, 8 or later), download that runtime from Microsoft's .NET website instead.
- Check the program maker's system requirements.
Download .NET only from Microsoft.
You install the version the program actually needs.
If it does not helpRun the program again after installing.
07Ask IT on a managed PC
On work or school PCs, updates often come from WSUS, which may not provide the .NET 3.5 files.
- Contact your IT department and tell them the error code.
- Microsoft's guidance for administrators is to configure an alternate source or allow downloading from Windows Update in the optional component policy.
IT installs the feature or enables the source.
If it does not helpDo not try to bypass company update policies.
Possible causes
- Windows cannot download the feature files from Windows Update
- An alternative source path that lacks usable files
- A group policy that blocks downloading from Windows Update
- Updates managed by WSUS on work or school PCs
- Damaged Windows component store
Was this helpful?
Your progress is saved on this device.