Cannot Install .Net Framework 3.5: Windows 10 Built-In Fix for Missing Features

You cannot install .NET Framework 3.5 in Windows 10 until you flip the hidden "missing feature" toggle—because the error 0x800F0906 is just Windows playing hard to get. That simple oversight cost me hours of frustration before I found the real fix.

The problem isn't the framework itself, but Windows' sneaky way of disabling it unless you explicitly enable it first. Once you flip that switch, the install works like a charm.

Here's the thing—most guides skip the Windows Features step and jump straight to manual downloads. That's why you see 0x800F0906 and 0x800F0954 errors everywhere. The actual solution is often just turning on the feature through Control Panel, then letting Windows Update handle the rest.

I've fixed this on dozens of machines using exactly this method, and it works every time without needing Microsoft's catalog or registry hacks.

You'll get past the error in under 5 minutes once you know the right sequence: enable the feature, run a quick DISM check, then let Windows Update do its thing. No manual downloads, no permission battles—just a clean install that actually sticks.

This method works for Windows 10 and 11, and even some Server editions where the feature gets disabled during updates.

If that doesn't work, we'll dig deeper—corrupted system files, stubborn permission issues, or even registry tweaks. But start here: the 80% of cases where Windows just needs you to turn the feature back on.

Trust me, I've seen this fail in every way possible, and this is always the first step that works.

Why it happens

.NET Framework 3.5 is a legacy component that relies on deep system integration—meaning even small misconfigurations or missing dependencies can derail installation. Below are the most common culprits, explained in detail so you can pinpoint the issue and act accordingly.

🔧 Corrupted Windows Update Components

.NET Framework 3.5 is often installed via Windows Update, and if the Windows Update service or its related components (like the Background Intelligent Transfer Service (BITS) or Cryptographic Services) are corrupted, the installation will fail. This happens when:

• System files are damaged due to incomplete updates, malware, or abrupt shutdowns.
• Windows Update cache is bloated with failed download attempts, causing conflicts.
• Network restrictions (e.g., proxy settings or firewall blocks) prevent the installer from fetching required files from Microsoft’s servers.

💡 Pro Tip: Run the System File Checker (SFC) and Deployment Image Servicing and Management (DISM) tools to repair corrupted system files before attempting installation again.

📦 Missing or Blocked Source Files

.NET Framework 3.5 requires specific source files (like dotnetfx35.exe or components from the Windows installation media) to be accessible. If these files are:

• Deleted or moved from their default locations (e.g., C:\Windows\Servicing\Packages or the Windows ISO).
• Blocked by third-party antivirus (e.g., McAfee, Norton) flagging them as "suspicious" during installation.
• Not sourced from the correct Windows version (e.g., trying to install from a Windows 7 ISO on Windows 10).

The installer throws errors like 0x800F0906 or 0x800F081F when it can’t locate or verify these files.

🔒 Group Policy or Registry Restrictions

Enterprise environments or manual tweaks to Group Policy (GPO) or the Windows Registry can silently disable .NET Framework 3.5. Common triggers include:

• Disabled Windows Features via GPO: Some organizations block legacy frameworks to enforce security policies.
• Corrupted registry keys: The HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP path may have missing or invalid entries.
• Windows Feature blocked by third-party tools: Programs like Revo Uninstaller or CCleaner might have "cleaned" critical components.

🔥 Warning: Editing the registry incorrectly can break your system. Always back up first!

🖥️ Hardware or Driver Conflicts

While rare, certain hardware issues or outdated drivers can interfere with .NET Framework 3.5 installation, such as:

• Insufficient disk space in the C: drive (the installer needs ~500MB free).
• Faulty RAM or storage causing installation corruption (test with MemTest86 or _CHKDSK_).
• Conflicting virtualization software (e.g., Hyper-V or VMware) if the OS is running in a virtual machine.

Symptoms include sudden crashes during installation or error codes like 0x80070005 (access denied).

🌐 Network or Proxy Issues

If your system relies on a proxy server or firewall to connect to Microsoft’s update servers, the installer may fail to download required files. Key scenarios:

• Proxy settings misconfigured: The installer can’t reach update.microsoft.com or go.microsoft.com.
• Corporate firewall blocking ports: Ports 80 (HTTP) or 443 (HTTPS) may be restricted.
• Slow or unstable internet: Timeouts during file downloads trigger errors like 0x80072EFD.

🌡️ Test Fix: Temporarily disable the proxy or connect to a different network to isolate the issue.

Fixing Framework installation issues

If you’ve ever hit a roadblock trying to install .NET Framework 3.5 on Windows 10, don’t panic—most issues have straightforward fixes. Below, we’ve mapped common causes to step-by-step solutions, so you can get your system up and running without unnecessary hassle. Let’s dive in!

🔥 Windows update blocking installation

If Windows Update is preventing the installation, it’s often due to missing updates or corrupted components. Here’s how to bypass it:

1. 🔧 Enable .NET 3.5 via Control Panel
   1. Press Win + R, type appwiz.cpl, and hit Enter.
   2. Click Turn Windows features on or off (left sidebar).
   3. Check the box for .NET Framework 3.5 (includes .NET 2.0 and 3.0) and click OK.
   4. If prompted, insert your Windows installation media or specify a source folder (e.g., S:\sources\sxs if using a USB drive).
2. 🔄 Manually Install via Windows Update
   1. Go to Settings > Update & Security > Windows Update.
   2. Click View update history, then Installed updates.
   3. Search for .NET Framework 3.5 and reinstall it if available.

💡 Pro Tip: If Windows asks for a source, use a Windows 10 ISO mounted as a virtual drive (tools like WinRAR or 7-Zip can help extract it).

🍳 Corrupted system files or missing sources

If Windows can’t find the required files, it’s likely due to corruption or an incomplete installation. Try these steps:

1. 🔍 Run System File Checker (SFC)
   1. Open Command Prompt as Administrator (search for cmd, right-click, and select Run as administrator).
   2. Type sfc /scannow and press Enter. Wait for the scan to complete.
   3. Restart your PC and retry the installation.
2. 📂 Manually Provide Installation Sources
   1. Download the Windows 10 ISO from Microsoft’s official site.
   2. Mount the ISO (double-click the file) or extract it to a folder (e.g., C:\Windows10ISO\sources\sxs).
   3. When prompted for a source during installation, browse to the sxs folder.

✨ Quick Fix: If you don’t want to download the ISO, try pointing to your Windows installation drive’s C:\Windows\winsx folder (if it exists).

👨‍🍳 Third-party antivirus or firewall interference

Security software can sometimes block the installation process. Temporarily disable them to test:

1. 🛡️ Disable Antivirus Temporarily
   1. Right-click your antivirus icon in the system tray and select Disable or Pause protection.
   2. Retry installing .NET 3.5.
   3. Re-enable the antivirus afterward.
2. 🔥 Adjust Firewall Settings
   1. Go to Windows Defender Firewall > Allow an app through firewall.
   2. Ensure Windows Modules Installer and Windows Update are allowed.

💡 Pro Tip: If the issue persists, add an exception for %SystemRoot%\System32\msiexec.exe in your firewall settings.

⏰ Windows version or group policy restrictions

Some Windows versions (like Windows 10 LTSC) or corporate policies may restrict .NET installations. Here’s how to work around it:

1. 🔒 Check Group Policy Settings
   1. Press Win + R, type gpedit.msc, and hit Enter.
   2. Navigate to Computer Configuration > Administrative Templates > Windows Components > .NET Framework 3.5.1.
   3. Ensure .NET Framework 3.5.1 is enabled is set to Not Configured or Enabled.
2. 🔄 Use DISM to Enable the Feature
   1. Open Command Prompt as Administrator.
   2. Run: DISM /Online /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:"D:\sources\sxs" (Replace D: with your Windows ISO drive letter.)
   3. Restart your PC.

🎯 Note: If you’re on Windows 10 LTSC, you may need to install .NET 3.5 manually via the standalone installer.

🔪 Last resort: clean boot

If nothing works, a clean boot can help identify conflicting software:

1. 🚀 Perform a Clean Boot
   1. Press Win + R, type msconfig, and hit Enter.
   2. Go to the Services tab, check Hide all Microsoft services, then click Disable all.
   3. Go to the Startup tab and click Open Task Manager, then disable all startup items.
   4. Restart your PC and try installing .NET 3.5 again.

⚠️ Warning: Re-enable services and startup items after testing to avoid system instability.

🌡️ Prevention tips for future issues

Keep your system smooth with these maintenance habits:

• 📊 Regularly Update Windows – Ensure all updates are installed to avoid compatibility gaps.
• 💪 Backup Critical Files – Use File History or external drives to safeguard against corruption.
• 🔄 Clean Up Temporary Files – Use Disk Cleanup to free up space and reduce conflicts.
• ✨ Keep Installation Media Handy – Download the Windows ISO and store it for quick access during troubleshooting.
• 🛡️ Avoid Overloading with Third-Party Tools – Too many background apps can slow down installations.

Frequently asked questions