Home › Windows › 0x800F0954

Windows · 0x800F0954 · Windows 10 / Windows 11

Windows Error 0x800F0954: DISM Failed to Install Optional Features on Windows 10/11

The error occurs when DISM cannot access required FoD packages, often due to WSUS misconfiguration. Fix by bypassing WSUS for FoD or using an ISO source.

Error Details

FactValueSourceNote
Error code0x800F0954DISM log (C:\Windows\Logs\DISM\dism.log)Indicates missing source files for optional features.
OS Build RangeWindows 10 and Windows 11Microsoft DocumentationApplies to all supported versions of Windows 10/11.
Registry Key InvolvedHKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdateRegistry EditorCheck UseWUServer and WUServer settings.
Relevant Service/Endpoint URLdownload.windowsupdate.com:443Network Connectivity TestUsed for direct FoD downloads when WSUS is bypassed.
Log Line SignatureGetFileInformation or DoQuiesceOperation failed with 0x800F0954DISM log (C:\Windows\Logs\DISM\dism.log)Identifies the specific package installation failure.

Log Files to Check

What This Error Actually Means

The error code 0x800F0954 is raised by the Deployment Image Servicing and Management (DISM) tool in Windows when it fails to locate or access source files required for installing optional features or roles. Specifically, this error occurs during the installation of Features on Demand (FoD), such as RSAT (Remote Server Administration Tools), .NET Framework 3.5, or language packs. The DISM component is responsible for managing and servicing Windows images, and it relies on either local sources (e.g., an ISO file) or remote sources (e.g., Windows Update or a WSUS server) to provide the necessary files.

Affected Versions and Scope

This error affects Windows 10 and Windows 11 operating systems across all builds. It is particularly relevant in enterprise environments where Group Policy is used to manage updates via a WSUS (Windows Server Update Services) server. The issue arises when the WSUS server does not host the required FoD packages, or when network policies block access to Microsoft's update servers.

Where To Look First: Logs and Event IDs

To diagnose this error, examine the following logs: 1. **DISM Log**: C:\Windows\Logs\DISM\dism.log. Search for the exact error code 0x800F0954 along with keywords like GetFileInformation or DoQuiesceOperation. 2. **CBS Log**: C:\Windows\Logs\CBS\CBS.log. Look for entries containing [SR] and ERROR near the timestamp of your installation attempt. 3. **Event Viewer**: Navigate to Event Viewer > System and filter by source Microsoft-Windows-DISM. Relevant Event IDs include: - 65027: Indicates success or failure of component store repair.

Root Causes

1. WSUS Server Does Not Host FoD Packages

If your environment uses a WSUS server to manage updates, ensure that it has been configured to synchronize FoD packages. This can be verified by checking the WSUS console or examining the Group Policy settings at HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate.

2. Windows Update is Disabled via Policy

The policy setting NoAutoUpdate=1 under HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU disables automatic updates, including the ability to download FoD packages. This prevents DISM from accessing the required files.

3. Network Connectivity Issues

Firewalls or network policies may block access to download.windowsupdate.com:443, which is necessary for direct downloading of FoD packages. Use Test-NetConnection -ComputerName download.windowsupdate.com -Port 443 to verify connectivity.

4. Incorrect Source Path in DISM Command

If using the /Source switch with a mounted ISO, ensure it matches the exact Windows version installed on the system. Mismatched versions will cause this error.

Fix Procedure

  1. Bypass WSUS for FoD: - Configure Group Policy at Computer Configuration > Administrative Templates > System > Specify settings for optional component installation and component repair. - Enable the policy and select "Contact Windows Update directly to download repair content." - This modifies HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Servicing with RepairContentServerSource=2.
  2. Temporarily Disable WSUS Override: - Use PowerShell to modify the registry: Set-ItemProperty 'HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate' -Name UseWUServer -Value 0. - Restart the Windows Update service with Restart-Service wuauserv. - After fixing, revert UseWUServer=1 if needed.
  3. Install from Mounted ISO: - Mount a Windows 11 ISO matching the installed build (use winver to confirm). - Run DISM with the source path: DISM /Online /Enable-Feature /FeatureName:RSAT.ActiveDirectory.DS-LDS~~~~0.0.1.0 /All /Source:D:\Sources\SxS /LimitAccess.

Error Code Variants

CodeDescription
0x800700C1Network path not found, often due to incorrect source paths.
0x8024003DUpdates are disabled by policy, preventing DISM from accessing FoD packages.

Verification

After applying the fix: - Run the original DISM command and ensure it reports "The operation completed successfully." - Verify feature installation with Get-WindowsCapability -Online | Where-Object {$_.Name -match 'RSAT'} | Select-Object Name, State. - Check dism.log for success messages without the error code.

Prevention

To avoid recurrence: - Ensure WSUS servers are configured to download and distribute FoD packages. - Review Group Policy settings related to Windows Update and FoD installation. - Regularly test network connectivity to download.windowsupdate.com:443.
Warning: Modifying the UseWUServer registry key can affect WSUS-based update management. Ensure this change aligns with your organization's update strategy.
Tip: Use Get-ItemProperty 'HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate' to quickly audit FoD-related policies.

Sources & References

Related Guides

Get new error code fixes by email

Product-specific solutions for Intune, Autopilot, SCCM and Entra ID — straight to your inbox. No spam.