Troubleshooting Guide · 2026

How to Fix Error 0x800F0950
When Installing .NET Framework in Windows

A practical guide for Windows 10 and Windows 11 users who cannot enable .NET Framework 3.5 or install required .NET components because Windows shows error code 0x800F0950.

⏱ ~11 min read Windows 10 Windows 11 .NET Framework 3.5 / 4.x / .NET Desktop Runtime

Error 0x800F0950 usually appears when Windows cannot install or enable a required .NET Framework component. You may see it while enabling .NET Framework 3.5 in Windows Features, running an older program that asks for .NET 2.0 or 3.5, installing a game launcher, or adding a modern .NET Desktop Runtime.

The error is often caused by missing installation source files, damaged system components, Windows Update problems, or corporate update policies that prevent Windows from downloading optional features. The methods below are ordered from the simplest fixes to the more advanced recovery steps.

💡
Important distinction .NET Framework 3.5 is a Windows optional feature, while newer .NET Desktop Runtime packages are usually installed with a separate installer. The same error code can appear in both cases, but the best fix depends on which package you are trying to install.
Section 01

What Does Error 0x800F0950 Mean During .NET Framework Installation?

Error code 0x800F0950 means that Windows could not complete the installation of a requested optional component or runtime. In most home-user cases, it is related to .NET Framework 3.5, which includes older .NET 2.0 and .NET 3.0 components used by legacy software.

✦ Common Symptoms

  • Windows Features fails while enabling .NET Framework 3.5.
  • An app says that .NET Framework is required, but installation fails.
  • The standalone .NET installer stops with error 0x800F0950.
  • DISM reports that source files could not be found or the feature cannot be enabled.

✦ Typical Causes

  • Windows Update cannot download optional feature files.
  • The component store is corrupted or incomplete.
  • A WSUS or Group Policy setting blocks downloading repair content.
  • The installed package does not match your Windows version or architecture.
Section 02

Before You Fix 0x800F0950: Quick Checks That Prevent Wasted Time

Before changing system settings, verify these basics. Many .NET Framework installation errors are caused by a wrong installer, a blocked internet connection, or a pending Windows restart.

  1. Restart the computer. If a previous update or runtime installation is pending, Windows may block new component changes until the restart completes.
  2. Check your Windows version. Press Win + R, type winver, and confirm whether you are using Windows 10 or Windows 11.
  3. Use an administrator account. Enabling Windows features and running DISM requires elevated permissions.
  4. Disconnect unreliable VPN or proxy connections. Optional feature downloads may fail if Microsoft update servers are blocked.
⚠️
Do not download random DLL or .NET packages Avoid third-party websites that offer individual .NET files. Use Windows Features, Windows Update, DISM, or official Microsoft installers only.
Method 01

Enable .NET Framework 3.5 from Windows Features

If the problem started when an older program requested .NET Framework 3.5, first try the normal Windows Features method. It is the safest option because Windows downloads and enables the correct files for your system automatically.

  1. Press Win + R, type optionalfeatures, and press Enter.
  2. Check .NET Framework 3.5 (includes .NET 2.0 and 3.0).
  3. Click OK.
  4. Choose Let Windows Update download the files for you.
  5. Wait for the installation to finish and restart Windows.
Run Dialogoptionalfeatures

If this method again ends with 0x800F0950, continue with the Windows Update and DISM-based methods below.

Method 02

Install Pending Windows Updates to Fix .NET Framework Error 0x800F0950

.NET Framework installation depends on the Windows servicing stack. If Windows Update is outdated, partially installed, or waiting for a restart, optional components may fail to install.

  1. Open Settings.
  2. Go to Windows Update.
  3. Click Check for updates.
  4. Install all available cumulative updates, servicing stack updates, and .NET updates.
  5. Restart the computer even if Windows does not explicitly require it.
Windows Version Path What to Install
Windows 11 Settings → Windows Update Cumulative updates, optional .NET updates, driver updates if relevant
Windows 10 Settings → Update & Security → Windows Update Latest cumulative update and any available .NET Framework update
Method 03

Use the Official Offline Installer for Newer .NET Runtime Packages

Some users see 0x800F0950 while installing a modern .NET runtime required by an app. In that case, do not try to enable .NET Framework 3.5 unless the app specifically asks for it. Install the required runtime package instead.

  1. Identify the package requested by the app: .NET Framework 4.8, .NET Desktop Runtime, or ASP.NET Core Runtime.
  2. Download the correct offline installer from Microsoft.
  3. Right-click the installer and choose Run as administrator.
  4. Restart Windows after the installation completes.
ℹ️
Which package do you need? Desktop applications usually need .NET Desktop Runtime or .NET Framework. Server applications may require ASP.NET Core Runtime. Installing the wrong runtime may finish successfully but still not fix the app.
Method 04

Install .NET Framework 3.5 with DISM and a Windows ISO Source

If Windows cannot download .NET Framework 3.5 files from Windows Update, use a Windows ISO as the local source. This method is especially effective on systems that show 0x800F0950 because optional feature files are missing.

  1. Download a Windows ISO that matches your installed Windows version and language.
  2. Right-click the ISO file and choose Mount.
  3. Note the new drive letter, for example D:.
  4. Open Terminal (Admin) or Command Prompt (Admin).
  5. Run the command below, replacing D: with your mounted ISO drive letter.
Command Prompt / Terminal (Admin)DISM /Online /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:D:\sources\sxs

The key part is \sources\sxs, which contains the .NET Framework 3.5 component files. If your ISO is mounted as E:, the source path becomes E:\sources\sxs.

⚠️
Use a matching ISO A Windows 10 ISO should be used for Windows 10, and a Windows 11 ISO should be used for Windows 11. Using the wrong source version can cause DISM to fail again.
Method 05

Repair Windows System Files and Component Store

If the component store is corrupted, Windows may be unable to enable features even when the source files are available. Run DISM and SFC to repair the servicing stack and protected system files.

  1. Right-click Start and choose Terminal (Admin).
  2. Run the following commands one by one.
  3. Wait for each command to finish before running the next one.
  4. Restart Windows and try installing .NET Framework again.
Terminal (Admin)DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

If DISM /RestoreHealth cannot download repair files, repeat the DISM source method from the previous section using a mounted Windows ISO.

Method 06

Check WSUS and Group Policy Settings Blocking Optional Feature Downloads

On work, school, or previously managed PCs, Windows may be configured to use WSUS instead of Microsoft Update. If the WSUS server does not provide optional component files, .NET Framework 3.5 installation can fail with 0x800F0950 or a similar servicing error.

Option A: Change the policy in Group Policy Editor

  1. Press Win + R, type gpedit.msc, and press Enter.
  2. Go to Computer Configuration → Administrative Templates → System.
  3. Open Specify settings for optional component installation and component repair.
  4. Set it to Enabled.
  5. Check Download repair content and optional features directly from Windows Update instead of Windows Server Update Services (WSUS).
  6. Click OK, restart Windows, and try again.

Option B: Temporarily bypass WSUS in the Registry

If Group Policy Editor is not available, you can check the Windows Update policy registry key. Create a restore point first, because incorrect registry changes may affect update behavior. 

Registry pathHKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU

Look for UseWUServer. On personal PCs, setting it to 0 and restarting the Windows Update service may allow Windows to download optional feature files directly. On organization-managed computers, contact the administrator instead of overriding policy.

Method 07

Install .NET Framework in Clean Boot Mode

Security software, system optimizers, update blockers, and background services can interfere with installers. A clean boot starts Windows with Microsoft services and minimal startup items, making it easier to complete the installation.

  1. Press Win + R, type msconfig, and press Enter.
  2. Open the Services tab.
  3. Check Hide all Microsoft services.
  4. Click Disable all.
  5. Open Task Manager → Startup apps and disable nonessential startup items.
  6. Restart Windows and try installing .NET Framework again.
  7. After the installation, return to msconfig and re-enable normal startup.
✅
Best use case Clean boot is most useful when the installer starts normally but fails near the end, or when error 0x800F0950 appears only on one particular PC.
Summary

Best Fixes for Error 0x800F0950: Quick Reference Table

Situation Recommended Fix Difficulty
Older app asks for .NET 2.0 / 3.0 / 3.5 Enable .NET Framework 3.5 in Windows Features Easy
Windows cannot download required feature files Install .NET Framework 3.5 with DISM and Windows ISO Medium
Windows Update is broken or pending Install all Windows updates and restart Easy
System files or component store are damaged Run DISM and SFC repair commands Medium
Work or school PC uses WSUS Adjust optional component installation policy Advanced
Third-party software blocks installation Use clean boot mode Medium
FAQ

FAQ: Error 0x800F0950 and .NET Framework Installation

Q Is error 0x800F0950 the same as a missing DLL error? ▼
No. A missing DLL error usually means an application cannot find a specific runtime file. Error 0x800F0950 means Windows failed to install or enable the required .NET component. Fix the .NET installation first instead of downloading individual DLL files.
Q Do I need .NET Framework 3.5 on Windows 11? ▼
Only if a program specifically requires it. Windows 11 can run many modern apps without .NET Framework 3.5, but older utilities, business apps, game launchers, and legacy games may still require it.
Q Can I install .NET Framework 3.5 without internet? ▼
Yes. Mount a matching Windows ISO and use the DISM command with the \sources\sxs folder as the source. This is the most reliable offline method.
Q Why does Windows say .NET Framework 4.x is already installed? ▼
Windows 10 and Windows 11 include modern .NET Framework 4.x components by default, but that does not replace .NET Framework 3.5. Some older applications still require the 3.5 feature, even if .NET Framework 4.x is already present.
Q What should I do if DISM also fails? ▼
Confirm that the ISO matches your installed Windows version, check the drive letter, and verify that the path sources\sxs exists. Then run DISM and SFC repair commands. If the PC is managed by an organization, WSUS policy may be blocking optional components.
Conclusion

Final Recommendations for Fixing .NET Framework Error 0x800F0950

For most users, error 0x800F0950 is fixed by enabling .NET Framework 3.5 through Windows Features, installing pending Windows updates, or using DISM with a mounted Windows ISO. If those methods fail, repair the component store and check whether WSUS or Group Policy is preventing Windows from downloading optional feature files.

Recommended Fix Order

Start with Windows Features, then update Windows, try the official offline installer if you need a modern runtime, use DISM with an ISO source for .NET Framework 3.5, repair Windows with DISM /RestoreHealth and SFC, and finally check WSUS or clean boot if the error persists.