How to Fix Windows Error 0x800F0954 When Installing .NET Framework

Encountering “Error 0x800F0954” when attempting to enable .NET Framework on Windows? You’re not alone—and the solution might be simpler than you think. This guide will walk you through beginner-friendly steps to bypass common WSUS/Web Update Service restrictions, optimize system configurations, and finally enable .NET Framework seamlessly. Let’s get your system running smoothly!

🔍 What does 0x800F0954 mean?

This error typically appears when Windows cannot download the required files to enable optional components, such as .NET Framework 3.5. It often occurs because Windows is configured to receive updates from a WSUS (Windows Server Update Services) server that lacks the necessary files.

1. Bypass WSUS (Temporarily Force Windows to Use Microsoft Update)

If your PC is part of an organization or using a custom WSUS server, it may block .NET components. Here’s how to temporarily bypass it:

• Open the Run dialog (Win + R), type regedit, and run as Administrator.
• Navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU
• Locate the UseWUServer DWORD value and set its data to 0. If this value is missing, you’ll need to create it.
• Close Registry Editor and restart the Windows Update service: net stop wuauserv && net start wuauserv

Once done, try enabling .NET Framework again .

2. Install .NET Framework via DISM or PowerShell

If the normal method fails, use these command-line tools to enable the feature:

• DISM (run in Admin Command Prompt): DISM /Online /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:X:\sources\sxs Replace X: with your Windows installation ISO or USB drive.
• PowerShell alternative: Add-WindowsCapability -Online -Name NetFx3~~~~0.0.1.0 -Source X:\sources\sxs

Either command installs .NET without relying on the Windows Features dialog .

3. Clean Up CBS Logs

Corrupted CBS (Component-Based Servicing) logs can block feature installation:

1. Go to C:\Windows\Logs\CBS and delete all files in the folder.
2. Run DISM installation again (as shown above).

This often clears underlying system errors and allows successful installation.

4. Change a Group Policy for Optional Features Repair

Windows may require local policy settings that allow component repair:

• Open Run dialog, type gpedit.msc, and open Group Policy Editor.
• Navigate to: Computer Configuration → Administrative Templates → System
• Double-click “Specify settings for optional component installation and component repair”, set it to Enabled, and ensure the box for “Download repair content and optional features directly from Windows Update” is checked.
• Click Apply, close the window, and restart your PC.

After this, retry installing .NET Framework.

💡 Why this works

WSUS-based environments don’t always include .NET Framework 3.5 files by default. These steps—registry edit, DISM fixes, and policy updates—ensure Windows can fetch or install necessary components from Microsoft’s official servers.

🧪 Hidden Fixes and Expert Workarounds

If the main steps didn’t work, don’t worry—there are additional fixes that have helped many users in enterprise environments or systems using WSUS. These advanced techniques may resolve the error 0x800F0954 when standard methods fail.

1. Use PowerShell Immediately Without Restarting

After changing the registry key UseWUServer to 0, you might read that a system restart is required. However, in many cases, you can skip the reboot and proceed immediately with PowerShell:

Steps:

• Press Windows + X and select Windows PowerShell (Admin).
• Type or paste the following command and press Enter:

If successful, this command installs .NET Framework 3.5 directly from Microsoft’s update servers without needing a restart.

2. Install .NET from a Local ISO or Network Share

If your PC is restricted to using WSUS (which may not provide .NET 3.5 files), you can use a local Windows ISO or a shared folder containing the sources\sxs directory:

Steps:

• Mount your Windows ISO file by double-clicking it.
• Note the drive letter assigned (e.g., D:).
• Open Command Prompt as Administrator.
• Run the following command, replacing D: with your actual drive letter:

Run the following command in the Command Prompt, replacing D: with your actual drive letter:

This forces Windows to use your local files instead of downloading from WSUS or Microsoft Update.

3. Force Group Policy Changes to Apply

After modifying Group Policy settings related to optional component repair, they may not take effect right away. You can apply them instantly using a built-in command.

Steps:

• Press Windows + R, type cmd, and press Ctrl + Shift + Enter to open as Admin.
• Type the following and press Enter:

Type the following command and press Enter:

This will apply Group Policy settings immediately without requiring a restart.

4. Check Event Viewer for Hidden Errors

If .NET Framework installation keeps failing and you’re not sure why, Event Viewer may reveal detailed error messages.

Steps:

• Press Windows + S and search for Event Viewer.
• In the left sidebar, go to Windows Logs → Setup.
• Look for recent events related to .NET Framework or CBS (Component-Based Servicing).

The logs may show specific reasons for failure, such as permission issues, corrupted files, or missing source locations.

5. Try DISM Without /LimitAccess

If your system is not part of a domain or WSUS-controlled environment, you can try installing .NET directly from Microsoft’s servers using this simpler command:

This tells Windows to fetch the required files over the internet, which often works well on home or personal PCs not connected to a domain.

This tells Windows to fetch the required files over the internet, which often works on home or personal PCs.

🛠️ Community tip from r/sysadmin

＞ “Basically disable WSUS via registry, proceed with your task, then re-enable the setting… and don’t forget to restart the Windows Update service.”

✅ Conclusion

To fix error 0x800F0954 when enabling .NET Framework:

1. Temporarily bypass WSUS via Registry
2. Use DISM or PowerShell to install the feature
3. Clean CBS logs if needed
4. Enable repair policy in Group Policy Editor

Most users resolve this issue by following these steps in order. If you’re still stuck, feel free to reach out for further assistance!

➡︎For more troubleshooting guides,check out:

▶︎🐢 [FIXED] File Explorer Running Slow After Windows 11 24H2 Update? Here’s How to Speed It Up!

▶︎Fix Windows 11 24H2 Search Bar Not Working – Causes and Solutions

▶︎💤 Why Does My Laptop Battery Drain So Much in Sleep Mode? Real Fixes You Can Try Today

タグ: 0x800f0954, Windows Update Error, .NET Framework install failed, WSUS bypass, DISM NetFx3, Windows 11 error, registry fix, Windows optional features