The Following Feature Couldn't Be Installed: Net Framework 3.5 Fix for Stubborn Systems

Troubleshooting

The following feature couldn't be installed: .NET Framework 3.5 is a nightmare that’s haunted Windows admins for years—especially when Windows Update fails silently. ⚡ I’ve spent hours chasing this error across Windows 10 and 11 machines, and the root causes always boil down to three things: missing updates, corrupted system files, or a stubborn Windows Features service.

The good news? Most fixes take under 15 minutes once you know where to look.

Windows Update often throws error codes like 0x800F0954 when it can’t download or verify the framework files. Meanwhile, manual installation via "Turn Windows features on/off" fails if the Windows Modules Installer service is stuck or system files are corrupted.

I’ve seen this block legacy apps, development tools, and even Windows itself from completing updates—so fixing it isn’t just about .NET; it’s about restoring system health.

You’ll walk away with a foolproof three-step repair process: first, force-enable the Windows Modules Installer service; second, run DISM and SFC scans to patch corrupted files; and third, manually trigger the installation with the exact command-line flags Microsoft’s docs omit.

No more guessing whether your system is "just broken"—this method works even when Windows Update refuses to cooperate.

Works for Windows 10 (1809+) and Windows 11, whether you’re dealing with a fresh install or a system that’s been through years of updates. Here’s the exact sequence I use to get .NET 3.5 installed every time—no regedit hacks or third-party tools required.

Why it happens

When you encounter the error "The following feature couldn’t be installed: .NET Framework 3.5", it’s rarely a single issue—it’s usually a chain reaction of underlying problems. Understanding these root causes helps you pinpoint the exact fix for your system.

Let’s break down the most common reasons why this happens, explained in plain terms with actionable insights.

🔧 Corrupted Windows Components or System Files

The .NET Framework 3.5 relies on core Windows components, such as the Windows Installer service, DISM (Deployment Image Servicing and Management), and SFC (System File Checker). If these are damaged—due to incomplete updates, malware, or hardware issues—the installation will fail before it even begins.

How it happens: Windows updates can sometimes fail mid-install, leaving critical files in a broken state. Malware or disk errors can also corrupt system files required for the .NET Framework to function.
Science behind it: The .NET Framework 3.5 is a layered technology that depends on the .NET Framework 2.0/3.0 stack. If those layers are missing or corrupted, the installer throws an error because it can’t build upon a faulty foundation.
Actionable fix: Run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth in Command Prompt (Admin) to repair system files. If these tools don’t resolve the issue, the corruption may be deeper—consider a Windows repair install.

📦 Missing or Disabled Windows Features

The .NET Framework 3.5 is technically a Windows feature, meaning it’s managed through Turn Windows features on or off in Control Panel. If this feature is disabled, grayed out, or partially installed, the installer will reject it with an error.

How it happens: Some Windows versions (especially Windows 10/11) hide or disable the .NET Framework 3.5 feature by default. Previous installations may have been interrupted, leaving it in a "half-installed" state.
Science behind it: Windows uses a transactional model for feature installations. If the transaction fails (e.g., due to insufficient permissions or disk space), the feature remains in a limbo state, triggering the error when you try to reinstall it.
Actionable fix:
- Open Control Panel > Programs > Turn Windows features on or off and manually enable .NET Framework 3.5. If it’s grayed out, proceed to the next steps.
- Use DISM /Online /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess in Command Prompt (Admin) to force-enable it.

🔒 Permission or Admin Rights Issues

Installing .NET Framework 3.5 requires administrative privileges. If you’re logged in as a standard user or the installer lacks sufficient permissions, it will fail silently—or with an error like this.

How it happens: Many users try to install .NET Framework 3.5 without admin rights, especially on shared or corporate machines. Even if you’re an admin, User Account Control (UAC) restrictions can block the process.
Science behind it: Windows enforces mandatory integrity control (MIC) levels for system components. The .NET Framework installer runs at a high integrity level, and if your session doesn’t match, the operation is denied.
Actionable fix:
- Run Command Prompt or PowerShell as Administrator and retry the installation.
- If UAC is interfering, temporarily disable it (not recommended for security) or adjust the installer’s compatibility settings to run as admin.

🖥️ Hardware or Disk Space Limitations

While less common, hardware issues—such as insufficient disk space, failing storage drives, or corrupted system partitions—can prevent the installation from completing.

How it happens: The .NET Framework 3.5 requires at least 200MB of free space on the system drive (C:). If your disk is full or fragmented, the installer may fail. Additionally, bad sectors on your hard drive can corrupt installation files mid-process.
Science behind it: Windows installers use temporary files stored in %TEMP% and %WINDIR%\Temp. If these folders are full or inaccessible, the installer cannot extract or write necessary files, leading to a failure.
Actionable fix:
- Free up at least 500MB of disk space on your system drive.
- Run chkdsk /f to scan for and repair disk errors.
- If using an HDD, consider defragmenting the disk for better performance.

🛡️ Antivirus or Firewall Blocking the Installer

Overzealous security software can mistakenly flag the .NET Framework installer as a threat and block its execution, causing the installation to fail.

How it happens: Some antivirus programs (e.g., Windows Defender, McAfee, Norton) scan installers in real-time and may quarantine or delete files if they trigger false positives.
Science behind it: The .NET Framework installer (dotnetfx35.exe) is digitally signed by Microsoft, but if your antivirus database is outdated, it may not recognize the signature, leading to a block.
Actionable fix:
- Temporarily disable your antivirus and retry the installation.
- Add an exception for %WINDIR%\Servicing\Packages\ and %TEMP% folders in your antivirus settings.
- Update your antivirus definitions to the latest version.

🔄 Conflicting Software or Previous Installations

Other installed software—especially older .NET Framework versions, Visual Studio, or development tools—can interfere with the installation process.

How it happens: If you have multiple .NET Framework versions installed (e.g., 2.0, 3.0, 4.8), conflicts can arise during the 3.5 installation. Some programs also lock system files needed by the installer.
Science behind it: The .NET Framework uses side-by-side (SxS) assemblies, meaning different versions can coexist—but only if they’re properly registered. If a previous installation was incomplete or corrupted, the new installer may detect conflicts and fail.
Actionable fix:
- Uninstall any conflicting .NET Framework versions via Control Panel > Programs > Uninstall a program.
- Use appwiz.cpl to remove Visual Studio or other development tools that might be interfering.
- Boot into Safe Mode and attempt the installation to rule out software conflicts.

How to solve it

Encountering the error "The following feature couldn't be installed" for .NET Framework 3.5 can be frustrating, but the good news is that most fixes are straightforward. Below, we’ve mapped common causes to their solutions—plus tips to prevent future issues. Let’s get your system up and running!

🔥 Cause 1: Missing Windows Update Components

If Windows Update services or required components are missing, the installer will fail. Here’s how to fix it:

🔧 Enable Windows Update Service:
1. Press Win + R, type services.msc, and hit Enter.
2. Find Windows Update in the list, right-click, and select Properties.
3. Set Startup type to Automatic and click Start.
4. Repeat for Background Intelligent Transfer Service (BITS).
🌐 Manually Install Windows 6.1-KB949106-v6001-x64.msu:
Download the standalone installer from Microsoft’s official site and run it as Administrator.

💡 Pro Tip: If the download link is broken, try searching for Windows6.1-KB949106-x64.msu on a trusted source like Microsoft Update Catalog.

🍳 Cause 2: Corrupted .NET Framework Installation

If files are corrupted or partially installed, the system will block the process. Clean up and reinstall:

🧹 Repair .NET Framework:
1. Open Control Panel > Programs > Turn Windows features on or off.
2. Uncheck .NET Framework 3.5, click OK, and wait for the process to complete.
3. Recheck .NET Framework 3.5 and restart your PC.
🔄 Reinstall via Command Prompt (Admin):
Open an elevated Command Prompt and run:
```
DISM /Online /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:"C:\path\to\sources\SXS"
```
Replace C:\path\to\sources\SXS with your Windows installation media’s Sources\SXS folder.

💡 Pro Tip: If the SXS folder is missing, mount your Windows ISO and copy the files to a local drive.

👨‍🍳 Cause 3: Antivirus or Firewall Blocking Installation

Security software can mistakenly flag .NET Framework installers as threats. Temporarily disable them:

🛡️ Disable Antivirus Temporarily:
Right-click your antivirus icon in the system tray and select Disable or Pause Protection for 15–30 minutes.
🔥 Add Exception for .NET Framework:
1. Open your antivirus settings and navigate to Exclusions or Whitelisted Files.
2. Add the following paths:
  - C:\Windows\Microsoft.NET\Framework\v3.5
  - C:\Windows\WinSxS
🔥 Temporarily Disable Windows Firewall:
Go to Control Panel > Windows Defender Firewall > Turn Windows Defender Firewall on or off and disable it for both private and public networks.

⚠️ Warning: Only disable protections temporarily—re-enable them immediately after installation.

🥘 Cause 4: Outdated or Incompatible Windows Version

Older Windows versions (e.g., Windows 7/8) may lack critical updates. Ensure your system is ready:

📊 Run Windows Update:
1. Go to Settings > Update & Security > Windows Update.
2. Click Check for updates and install all pending updates.
3. Restart your PC and retry the installation.
🔄 Install Latest .NET Framework 3.5 Offline Package:
Download the standalone installer for your Windows version and run it as Administrator.

💡 Pro Tip: For Windows 10/11, ensure you’re on Version 1507 or later—earlier builds may not support .NET 3.5.

⏰ Cause 5: Pending Restarts or System Conflicts

Sometimes, pending updates or background processes can interfere. Force a clean state:

🔄 Restart in Safe Mode:
1. Press Win + R, type msconfig, and go to the Boot tab.
2. Check Safe boot and restart.
3. Attempt the .NET Framework installation again.
🧹 Clear Temp Files:
Open File Explorer > This PC > Right-click C: > Properties > Disk Cleanup. Check Temporary files and Windows Update Cleanup, then run the tool.