Fix Error 0x800f0954 on Windows Server (Complete Guide)

Error 0x800f0954 stops you from installing .NET Framework 3.5 or other Windows features on Windows Server 2019, 2022, or 2016. If you have hit this wall, you are not alone — it is one of the most common feature-installation failures in enterprise environments, and it almost always has the same root cause: your server is configured to use WSUS (Windows Server Update Services) and cannot reach the files it needs from Microsoft's servers directly.

This guide covers six proven methods to resolve error 0x800f0954 on Windows Server, from the fastest one-liner fixes to offline installation for air-gapped environments.

What Is Error 0x800f0954?

Despite what some older articles say, 0x800f0954 is not a Windows activation error. It is a Windows feature installation error — specifically, the error code returned by the Deployment Image Servicing and Management tool (DISM) or the Add Roles and Features wizard when the server cannot obtain the required source files.

The full error message typically reads:

Error: 0x800f0954
The source files could not be found.

Or, from DISM:

DISM failed. No operation was performed.
For more information, review the log file.
Error code: 0x800f0954

Common Causes

• WSUS is configured via Group Policy — the most frequent cause. When WSUS is active, Windows redirects all update and feature requests through the internal WSUS server. If that server does not have the required feature payloads, installation fails.
• Missing installation media or source files — the server cannot locate the SxS (side-by-side) folder needed for offline feature installation.
• Group Policy blocking Windows Update access — even without WSUS, a GPO may prevent direct contact with Microsoft's update servers.
• Corrupted Windows component store — the CBS (Component Based Servicing) store has integrity issues that prevent feature installation.
• Incorrect DISM source path — the /Source flag points to the wrong location.

Method 1: DISM with Explicit Source Path

Before anything else, try forcing DISM to fetch the files directly from Windows Update, bypassing any configured local source:

DISM /Online /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:"%SystemRoot%\WinSxS"

If that returns 0x800f0954, remove the /LimitAccess flag to allow internet access:

DISM /Online /Enable-Feature /FeatureName:NetFx3 /All

If the error persists, move on to Method 2.

Method 2: Bypass WSUS Temporarily (Most Effective Fix)

This is the fix that works for the vast majority of servers. It temporarily redirects Windows Update traffic away from WSUS so that the feature installation can pull source files directly from Microsoft.

Open an elevated PowerShell or Command Prompt and run:

# PowerShell — disable WSUS for this session
$env:WINDOWS_TRACING_LOGFILE = $null
Set-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU" `
  -Name "UseWUServer" -Value 0
Stop-Service wuauserv
Start-Service wuauserv

Then immediately install the feature:

Install-WindowsFeature -Name NET-Framework-Core -Source windows

Or using DISM:

DISM /Online /Enable-Feature /FeatureName:NetFx3 /All

After installation completes, re-enable WSUS:

Set-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU" `
  -Name "UseWUServer" -Value 1
Stop-Service wuauserv
Start-Service wuauserv

Method 3: Fix via Group Policy (Permanent WSUS Bypass)

If you manage multiple servers or want a cleaner solution through Group Policy, you can configure Windows to use Windows Update directly for feature installation while still routing regular updates through WSUS.

1. Open Group Policy Management (gpmc.msc) on your domain controller.
2. Edit the GPO applied to the affected server(s).
3. Navigate to: Computer Configuration > Administrative Templates > System
4. Open the policy: "Specify settings for optional component installation and component repair"
5. Set it to Enabled.
6. Check the box: "Download repair content and optional features directly from Windows Update instead of Windows Server Update Services (WSUS)"
7. Click OK and run gpupdate /force on the target server.

Then retry the feature installation. This setting persists across reboots and applies to all future feature installations on those servers.

Method 4: Offline Installation from ISO (No Internet Required)

If your servers have no internet access or you cannot touch Group Policy, install .NET Framework 3.5 directly from the Windows Server installation media.

Step 1 — Mount the ISO or insert the media

If you have an ISO, mount it in Windows (right-click → Mount) or attach it to your VM. Note the drive letter — for this example, we will use D:.

Step 2 — Run DISM with the SxS source path

DISM /Online /Enable-Feature /FeatureName:NetFx3 /All `
  /LimitAccess /Source:D:\sources\sxs

Replace D:\sources\sxs with the actual path to your mounted media. The /LimitAccess flag ensures DISM does not attempt to contact Windows Update — useful for air-gapped environments.

Alternative — PowerShell

Install-WindowsFeature -Name NET-Framework-Core -Source D:\sources\sxs

Method 5: Repair the Windows Component Store

If the above methods have not resolved the issue, the Windows component store (CBS) may be corrupted. Run the following sequence to check and repair it:

Step 1 — Check the component store health

DISM /Online /Cleanup-Image /CheckHealth

Step 2 — Scan for corruption

DISM /Online /Cleanup-Image /ScanHealth

Step 3 — Restore health from Windows Update

DISM /Online /Cleanup-Image /RestoreHealth

This command connects to Windows Update to download and replace corrupted files. It can take 10–30 minutes. If your server is behind WSUS and internet access is blocked, add the source flag:

DISM /Online /Cleanup-Image /RestoreHealth /Source:D:\sources\sxs /LimitAccess

Step 4 — Run System File Checker

sfc /scannow

Once the component store is healthy, retry the feature installation.

Method 6: Enable via Server Manager (GUI)

For administrators who prefer a GUI approach, Server Manager can sometimes succeed where the command line fails — particularly after applying the Group Policy fix in Method 3.

1. Open Server Manager.
2. Click Add Roles and Features.
3. Step through the wizard until you reach Features.
4. Expand .NET Framework 3.5 Features and tick the checkbox.
5. On the confirmation screen, click "Specify an alternate source path" if you want to use installation media.
6. Enter the path: D:\sources\sxs
7. Click Install.

How to Check DISM Logs for More Detail

If none of the above methods work immediately, the DISM log will tell you exactly what went wrong. Check it with:

Get-Content C:\Windows\Logs\DISM\dism.log -Tail 50

Or open it in Notepad:

notepad C:\Windows\Logs\DISM\dism.log

Look for lines containing CBS, NetFx3, or 0x800f0954 to identify the exact failure point. Common entries to look for:

• Error: 14098 — component store corrupted (run RestoreHealth)
• WU client failed Searching for update — WSUS blocking (use Method 2)
• Source not found — wrong source path (verify your ISO path)

Which Fix Should You Use?

Need a Genuine Windows Server Licence?

If you are setting up a new server environment or renewing an existing one, make sure you are running on a genuine, fully activated licence. A properly licensed and activated server will never block feature installation due to licence-related issues.

Licendi offers genuine, EU-compliant Windows Server licences at competitive prices:

• Windows Server 2019 Standard — stable, proven, ideal for most workloads
• Windows Server 2022 Standard — latest features, enhanced security, improved hybrid capabilities
• Windows Server 2022 Datacenter — unlimited virtualisation rights for large environments
• Windows Server CALs — user and device access licences for your server environment

All licences are instantly delivered by email with activation keys. Browse Windows Server licences →

Frequently Asked Questions

What causes error 0x800f0954 on Windows Server?

Error 0x800f0954 is caused by Windows being unable to locate the source files needed to install a feature such as .NET Framework 3.5. The most common cause is a WSUS configuration that blocks direct access to Windows Update. Other causes include missing installation media, a corrupted component store, or a Group Policy restricting Windows Update access.

Is 0x800f0954 a Windows activation error?

No. Despite how some older articles describe it, 0x800f0954 is not a Windows activation error. It is a feature installation error returned by DISM or the Add Roles and Features wizard. It has nothing to do with your Windows licence or product key.

How do I fix 0x800f0954 without internet access?

Use offline installation from the Windows Server ISO. Mount the ISO, then run:

DISM /Online /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:D:\sources\sxs

Replace D: with your actual drive letter. This installs .NET Framework 3.5 directly from installation media without any internet connection.

Can I fix 0x800f0954 across multiple servers at once?

Yes. Use the Group Policy method (Method 3). Configure the "Specify settings for optional component installation and component repair" policy, enable the option to download repair content directly from Windows Update instead of WSUS, apply it to the relevant OU, and run gpupdate /force. This resolves the issue for all affected servers simultaneously.

Will bypassing WSUS affect my server's update management?

Temporarily, if you use Method 2 — which is why you must re-enable WSUS immediately after installation completes. The Group Policy fix in Method 3 is more surgical: it only allows direct Windows Update access for feature installation, while regular updates continue to flow through WSUS as normal.

Sources: Microsoft Learn — Troubleshoot .NET Framework 3.5 installation error 0x800f0954 | Microsoft DISM Troubleshooting Guide