How to Fix .NET Framework 3.5 Error 0x800F0922 on Windows 11

When trying to install .NET Framework 3.5 on Windows 11, many users encounter a frustrating error message that stops the installation midway: “The changes couldn’t be completed. Error code: 0x800F0922”

This error usually occurs when Windows cannot access the necessary files or system components needed to install .NET Framework 3.5 properly. The good news is that you can fix it quickly by following a few straightforward troubleshooting steps.

In this guide, we’ll explain what causes this error, and show you how to resolve Error 0x800F0922 step by step — whether you’re installing online, offline, or through Windows features.

What Causes Error 0x800F0922 in Windows 11?

Before fixing the issue, it’s helpful to understand what’s going wrong behind the scenes. The 0x800F0922 error generally appears when:

Windows Update is unable to connect to Microsoft’s servers.
Your PC is connected to a corporate network or WSUS (Windows Server Update Service).
The installation source (SxS folder) is missing or damaged.
System files or Windows image components are corrupted.
Windows features are disabled or blocked by a Group Policy setting.

Essentially, Windows can’t locate or download the .NET 3.5 files it needs — but you can manually fix that.

Fix 1: Enable .NET Framework 3.5 Using Windows Features

The simplest way to install .NET 3.5 is through Windows Features, which is built into Windows 11.

Press Windows + R to open the Run dialog.
Type: optionalfeatures and hit Enter.
In the Windows Features window, find and check the box next to:
✅ .NET Framework 3.5 (includes .NET 2.0 and 3.0)
Click OK and allow Windows to download and install the required files.

If you receive the 0x800F0922 error, proceed with the next fix — your system might be blocked from reaching Microsoft’s servers.

Fix 2: Bypass WSUS via Group Policy Editor

If you’re using a computer connected to a company network, Windows might be configured to fetch updates from a local WSUS server instead of Microsoft. This often causes the 0x800F0922 error.

You can fix this by telling Windows to download optional features directly from Microsoft’s servers.

Press Windows + R, type gpedit.msc, and hit Enter.
Navigate to the following path: Computer Configuration → Administrative Templates → System
On the right panel, find and double-click Specify settings for optional component installation and component repair.
Select Enabled.
Check both options:
- ☑ Contact Windows Update directly to download repair content instead of WSUS
- ☑ Repair content and optional features directly from Windows Update
Click Apply → OK.
Restart your PC and try installing .NET Framework 3.5 again.

Fix 3: Use DISM Command to Install .NET 3.5

If you’re still getting the 0x800F0922 error, you can manually install the framework using the DISM tool (Deployment Image Servicing and Management).

Insert your Windows 11 installation USB or mount the ISO file.
Note the drive letter (for example, D:).
Open Command Prompt as Administrator and run: DISM /Online /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:D:\sources\sxs
Replace D: with the actual drive letter of your installation media.
Wait for the installation to finish — it may take a few minutes.

Once it’s complete, restart your PC and the .NET 3.5 feature should now be successfully installed.

Fix 4: Run Windows Update Troubleshooter

Sometimes, .NET installation fails because of a temporary Windows Update issue. Running the built-in troubleshooter can automatically detect and fix such problems.

Open Settings (Windows + I).
Go to System → Troubleshoot → Other troubleshooters.
Find Windows Update and click Run.
Let the troubleshooter detect and fix any issues automatically.

After it’s done, restart your PC and retry the .NET installation.

Fix 5: Clear Windows Update Cache

A corrupted Windows Update cache can also block .NET Framework installation. Clearing it can often resolve the 0x800F0922 error.

Open Command Prompt as Administrator.
Stop Windows Update services by running: net stop wuauserv net stop bits
Navigate to the update cache folder: C:\Windows\SoftwareDistribution
Delete all files inside this folder (don’t delete the folder itself).
Restart the services: net start wuauserv net start bits
Now try enabling .NET Framework 3.5 again.

Fix 6: Repair Windows Image Using DISM

If system files related to optional components are corrupted, repairing your Windows image can help.

Open Command Prompt (Admin).
Run the following command: DISM /Online /Cleanup-Image /RestoreHealth
Wait for the process to complete — this may take 10–15 minutes.
Once finished, run: sfc /scannow
Restart your computer and try installing .NET Framework 3.5 again.

This ensures that the component store used for installing Windows features is fully healthy.

Fix 7: Use Microsoft’s Offline Installer

If your system is having trouble connecting to Windows Update, use the official offline installer to manually install .NET 3.5. Download .NET Framework 3.5 SP1 Offline Installer

After downloading:

Run the installer.
Follow the on-screen instructions.
Restart your PC once installation completes.

Fix 8: Disable VPN or Proxy

If you’re connected through a VPN or proxy server, it might prevent your PC from accessing Microsoft’s update servers, triggering the 0x800F0922 error.

Temporarily disconnect your VPN or disable the proxy connection.
Then retry installing .NET Framework 3.5.

Once installed, you can safely reconnect your VPN.

Bonus Tip: Reinstall .NET Framework (If Already Corrupted)

If .NET Framework 3.5 was previously installed but now fails to work properly:

Open Windows Features again (optionalfeatures).
Uncheck .NET Framework 3.5 → click OK → restart your PC.
Go back and check it again to reinstall.

This can resolve incomplete or corrupted installations.

Wrapping Up

The .NET Framework 3.5 Error 0x800F0922 usually means Windows couldn’t download the required files from Microsoft’s update servers or that a system policy blocked the process.

By enabling optional components through Group Policy, using DISM commands, or installing offline via ISO, you can easily fix the issue and get your apps running again.

Once .NET 3.5 is successfully installed, you’ll be able to launch older Windows applications and tools without any interruptions.