Optional Features Not Installing in Windows 11? Fixes

If optional features in Windows 11 (like .NET Framework 3.5, Hyper-V, or Windows Subsystem for Linux) are stuck on “Downloading” or fail with an error, the fix usually involves repairing the component store, checking Windows Update, or using the DISM command-line tool. Below are the most effective methods to get those features installed, plus background on why they fail in the first place.

Why Optional Features Fail to Install

Optional features in Windows 11 are not stored as full installers on your PC. Instead, they are “feature on demand” packages that Windows downloads from Windows Update or from local sources like the Windows image file (install.wim). When you enable a feature, Windows calls the Component-Based Servicing (CBS) system, which locates the required payload, verifies its integrity, and then installs it. Failures happen when:

• Windows Update is blocked, paused, or misconfigured.
• The Component Store (WinSxS) is corrupted or has missing manifests.
• Group Policy or registry settings redirect the feature source to a server that is unreachable.
• There is not enough disk space for the feature payload.
• Third-party antivirus or security software interferes with the servicing process.

Understanding this helps because most fixes target either the source of the payload or the health of the component store.

Prerequisites and Quick Checks

Before diving into advanced repairs, verify these basics:

1. Check Windows Update status: Go to Settings > Windows Update and ensure no updates are pending. Pause updates temporarily if a download is stuck.
2. Ensure enough disk space: Features like Windows Subsystem for Linux can require several gigabytes. Check Settings > System > Storage.
3. Run Windows Update troubleshooter: Settings > System > Troubleshoot > Other troubleshooters > Windows Update. This can fix common download issues.
4. Temporarily disable third-party antivirus: Some security suites block the CBS process. If disabling fixes the issue, add an exclusion for C:\Windows\WinSxS.

If these don’t help, proceed to the command-line methods below, which are more reliable for persistent failures.

Method 1: Use DISM to Repair the Component Store

DISM (Deployment Image Servicing and Management) can fix corruption in the Windows image that prevents features from installing. Run this in an elevated Command Prompt (search for “cmd”, right-click, “Run as administrator”):

1. Run: DISM /Online /Cleanup-Image /RestoreHealth — this scans and repairs the system image. It may take 15-30 minutes.
2. If it fails with “source files not found”, you need a valid Windows 11 installation media. Insert a USB or mount an ISO, then run: DISM /Online /Cleanup-Image /RestoreHealth /Source:D:\sources\install.wim /LimitAccess (replace D: with your drive letter).
3. After DISM completes, run sfc /scannow to verify system file integrity.
4. Reboot and try enabling the optional feature again.

DISM is often the first fix because it addresses the root cause: a broken component store.

Method 2: Install the Feature from a Local Source

If Windows Update is not an option (e.g., offline PC), you can point the installer to the Windows installation media. This is especially useful for .NET Framework 3.5, which is not included by default in Windows 11.

1. Mount the Windows 11 ISO or insert installation media. Note the drive letter (e.g., E:).
2. Open Command Prompt as administrator.
3. Run: DISM /Online /Enable-Feature /FeatureName:NetFx3 /All /Source:E:\sources\sxs /LimitAccess
4. For other features, replace NetFx3 with the feature name (e.g., Microsoft-Hyper-V-All). You can get the exact name with DISM /Online /Get-Features.

This method bypasses Windows Update entirely and is the standard workaround for “Windows couldn’t complete the requested changes” errors.

Method 3: Reset Windows Update Components

If the feature is stuck on “Downloading” and never progresses, the Windows Update service may be in a bad state. Resetting it can clear stuck queues:

1. Stop the relevant services by running these commands in an elevated Command Prompt:
   net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
2. Rename the SoftwareDistribution and Catroot2 folders:
   ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 Catroot2.old
3. Restart the services:
   net start wuauserv
net start cryptSvc
net start bits
net start msiserver
4. Reboot and try enabling the feature again.

This is a safe, well-known procedure that does not affect personal files.

Common Error Codes and Their Meanings

Windows often shows a numeric error code when a feature fails. Here are the most common ones and what they indicate:

• 0x800F081F – Source files not found. The payload is missing from the local source or Windows Update. Use DISM with a local source.
• 0x800F0906 – Windows Update could not download the files. Often due to network or WSUS (Windows Server Update Services) policy. Check Group Policy for “Specify settings for optional component installation”.
• 0x800F0954 – The feature cannot be installed because of Group Policy settings. This is common on corporate PCs where the administrator has disabled downloads from Windows Update.
• 0x800F0922 – The feature installation failed during the reboot phase. Often related to language pack or disk space issues.

If you see 0x800F0954, you must contact your IT administrator because the policy blocks the installation.

When to Use Windows Settings vs. DISM

For most users, the Settings app (Settings > Apps > Optional features) is the simplest way to add features. However, it relies on Windows Update and often fails silently. DISM gives you more control and detailed error messages. Use Settings first; if it fails or hangs, switch to DISM. For .NET Framework 3.5 specifically, DISM with a local source is almost always the most reliable method because the feature is not distributed via Windows Update on many systems.

Frequently Asked Questions

Why does my optional feature keep saying “Downloading” but never finish?

This usually means Windows Update is stuck or the component store is corrupted. Try resetting Windows Update components (Method 3) or running DISM with a local source. If you are on a corporate network, Group Policy may be blocking the download.

Can I install .NET Framework 3.5 without internet?

Yes. Use the DISM command with the /Source parameter pointing to the Windows 11 installation media (the sxs folder). This is the standard offline method and does not require Windows Update.

Is it safe to use DISM commands?

Yes, when run correctly. DISM is a built-in Windows tool designed for servicing. The commands listed above are safe and do not delete personal files. However, always run as administrator and avoid using it if you are not comfortable with command-line tools.

What if DISM fails with “source files not found”?

Your local Windows image is corrupted and you need a valid source. Download the Windows 11 ISO from Microsoft’s website, mount it, and use the /Source parameter with the mount’s drive letter. If the ISO is the same version as your installed Windows, it will work.

Will installing optional features slow down my PC?

Most optional features are inactive until you use them. For example, Hyper-V only runs when you start a virtual machine. However, some features like Windows Subsystem for Linux run background services. You can disable them later via the same Optional Features page.

Do I need to reboot after installing a feature?

Some features require a reboot, others do not. Windows will prompt you if a reboot is necessary. It is always safest to reboot after any feature installation to ensure all services start correctly.

Related

• Install Jenkins on Windows: Step-by-Step Guide
• Fix Error 0x803f9008: Windows Store & Xbox Guide
• How to Change Google Drive Folder Location