sodcalculator

10 Tech How-To

Net Framework 3.5 Installation Error 0x800f0950

Guide 10-5792 · Updated · Step by step

If you see error 0x800f0950 while installing .NET Framework 3.5 on Windows 10 or 11, it usually means Windows Update cannot fetch the required feature files from its servers. The fix is to either repair the Windows Update component or install the feature using the Windows installation media.

What Causes Error 0x800f0950?

Error 0x800f0950 is a DISM (Deployment Imaging Service and Management) error that occurs when the system cannot find or download the source files for the .NET Framework 3.5 feature. The most common triggers are:

  • Windows Update service is disabled or corrupted.
  • Group Policy or registry settings block the download from Windows Update.
  • The local cache of Windows Update files (C:\Windows\SoftwareDistribution) is damaged.
  • You’re trying to install .NET 3.5 on a system that has never had it enabled, and the required CAB files aren’t present locally.

Windows 10 and 11 include .NET Framework 4.x by default, but many older applications (especially business software, games, and utilities) still require the 3.5 runtime. The installer tries to pull the necessary components from Windows Update; when that fails, you see the 0x800f0950 code.

Background: Why .NET 3.5 Isn’t Included

.NET Framework 3.5 is a separate feature in Windows, not a standalone download. Microsoft made it an optional feature because it’s only needed for legacy apps. The installation process uses DISM to enable the feature and then copies the required files from either Windows Update or the local installation media (install.wim or install.esd).

On Windows 10 and 11, the feature is listed under “Turn Windows features on or off” in the Control Panel. Checking the box for .NET Framework 3.5 (which includes 2.0 and 3.0) triggers the download. If that download fails, you get error 0x800f0950. The same error can appear during a clean installation or when using the DISM command line tool.

How to Fix: Step-by-Step Methods

Try these fixes in order. The first two are the most likely to work.

Method 1: Use Windows Features Dialog

  1. Press Win + R, type optionalfeatures, and press Enter.
  2. Check the box for .NET Framework 3.5 (includes .NET 2.0 and 3.0).
  3. Click OK and let Windows download the files. If it fails, move to Method 2.

Method 2: Use DISM with Windows Update

  1. Open Command Prompt as Administrator (right-click Start, choose “Command Prompt (Admin)” or “Terminal (Admin)”).
  2. Run: dism /online /enable-feature /featurename:NetFx3 /all /source:C:\Windows\WinSxS
  3. If that fails, try without the source: dism /online /enable-feature /featurename:NetFx3 /all

If DISM reports error 0x800f0950, the source files are missing. You’ll need the Windows installation media (ISO or USB).

Method 3: Install from Windows Installation Media

  1. Mount the Windows ISO or insert the USB installation drive. Note the drive letter (e.g., E:).
  2. Open Command Prompt as Administrator.
  3. Run: dism /online /enable-feature /featurename:NetFx3 /all /source:E:\sources\sxs /limitaccess

This tells DISM to use the local files instead of Windows Update. Make sure the media matches your Windows version (same build or newer).

Method 4: Reset Windows Update Components

  1. Stop the Windows Update service: net stop wuauserv
  2. Rename the SoftwareDistribution folder: ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
  3. Restart the service: net start wuauserv
  4. Try the installation again.

What If the Installer Still Fails?

If none of the above works, the problem may be deeper. Check if your Windows is fully updated (Settings > Update & Security > Windows Update). Sometimes a pending update blocks the feature installation. Also, run the System File Checker:

  1. Open Command Prompt as Administrator.
  2. Run sfc /scannow and wait for it to finish.
  3. If it finds errors, restart and try the .NET install again.

Another possibility: your Windows edition doesn’t include the .NET 3.5 feature at all (e.g., some N editions or LTSC versions). Check your edition by pressing Win + Pause or running winver. If you’re on N edition, you may need to download the feature pack manually from Microsoft’s website.

Common Misconceptions and Pitfalls

  • “Error 0x800f0950 means my hard drive is failing.” No, it’s purely a component installation error.
  • “I can just download .NET 3.5 from the web.” Microsoft doesn’t offer a standalone installer for Windows 10/11; you must use the features dialog or DISM.
  • “The error is the same as 0x800F081F.” They are similar but not identical. 0x800F081F means source files not found; 0x800f0950 often indicates a Windows Update download failure.
  • “I need to disable antivirus.” Rarely helps, but some security software can block DISM from writing to system folders. If you’ve tried everything, temporarily disable third-party antivirus and retry.

Comparison: DISM vs. Windows Features Dialog

The Windows Features dialog is the easiest for beginners, but it gives you little control. DISM is more flexible: you can specify a source path, limit access to Windows Update, and see detailed error codes. For most users, the dialog works. If it doesn’t, DISM with the installation media is the most reliable method.

There’s also the PowerShell equivalent: Install-WindowsFeature -Name Net-Framework-Core (requires admin). That’s mainly for Windows Server, but it works on client editions too.

Frequently Asked Questions

Can I install .NET 3.5 without internet?

Yes, if you have the Windows installation media. Use the DISM command with the source path pointing to the sources\sxs folder on the media. Without media and without internet, you cannot install it because the files aren’t included in the default installation.

Will this error affect my existing .NET 4.x apps?

No. .NET Framework 4.x and 3.5 are separate runtimes. The error only affects the 3.5 feature installation; your current apps will continue to work.

Is it safe to delete the SoftwareDistribution.old folder?

Yes, after you’ve successfully installed .NET 3.5 or if you don’t need Windows Update anymore. But it’s safer to keep it until you’ve confirmed everything works, then delete it to free space.

Why does the installer ask for a source path?

Because the .NET 3.5 feature files are not part of the base Windows image. They are stored in the WinSxS folder or on the installation media. The source path tells DISM where to find them.

Can I use a Windows 10 ISO to install .NET 3.5 on Windows 11?

Generally, no. The source files must match your Windows version. Using a mismatched ISO may cause other errors. Always use the ISO for your specific OS version.

What if I don’t have the installation media?

You can download an official Windows ISO from Microsoft’s website (requires a valid product key). Alternatively, use the Windows Media Creation Tool to create a USB drive. Then mount the ISO and use the source path method.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →