0x800f0954: Fix Windows Update Error

Error code 0x800f0954 stops Windows Update from installing certain updates, most often .NET Framework packages, and it usually appears because the system is configured to get updates from a local Windows Server Update Services (WSUS) server instead of Microsoft directly. The fix is to either temporarily bypass WSUS for that update, repair the Windows Update components, or clear the software distribution cache. Below is a practical walkthrough for the most common scenarios, plus background on why the error happens.

What Does Error 0x800f0954 Mean?

The code 0x800f0954 is a Windows Update error that translates to CBS_E_SOURCE_MISSING or a related servicing failure. In plain terms, the Windows component servicing engine (CBS) could not find the source files it needed to complete the update. This is frequently tied to .NET Framework 3.5 or 4.x updates on machines that receive updates through WSUS, because the update source is not configured to provide those payloads locally. The error can also appear after a failed manual update attempt, a corrupted update cache, or when the Windows Modules Installer service is not running properly.

Why Does 0x800f0954 Happen?

Most reports of 0x800f0954 come from Windows 10 and Windows 11 systems joined to a domain that uses WSUS. When WSUS is active, Windows Update is told to pull updates from the internal server, not from Microsoft. If the WSUS administrator has not approved or imported the .NET Framework update packages, the client computer cannot find the files and throws 0x800f0954. The error can also occur on standalone machines if a Group Policy setting forces the update source to a non-existent or unreachable server, or if the local update cache (the SoftwareDistribution folder) has become corrupted.

How to Fix Error 0x800f0954

Try these fixes in order. The first two are the most likely to resolve the issue quickly.

Install the update manually from the Microsoft Update Catalog. Go to the Microsoft Update Catalog, search for the KB number of the update that failed (you can find it in Windows Update history), download the correct version for your system (x86, x64, or ARM64), and run the installer. This bypasses WSUS entirely and often works immediately.
Clear the SoftwareDistribution folder. Stop Windows Update and the Background Intelligent Transfer Service (BITS) by running these commands in an elevated Command Prompt:
net stop wuauserv
net stop bits
Then rename the folder: ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
Restart the services: net start wuauserv and net start bits. Then try Windows Update again.
Run the Windows Update troubleshooter. Go to Settings > System > Troubleshoot > Other troubleshooters, select Windows Update, and run it. This can fix common component issues automatically.
Use DISM and SFC. In an elevated Command Prompt, run DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow. This repairs corrupted system files that might be causing the update to fail.
Temporarily switch the update source to Microsoft. If you have administrative access to Group Policy, go to Computer Configuration > Administrative Templates > Windows Components > Windows Update > Manage updates offered from Windows Update. Set “Specify intranet Microsoft update service location� to Not Configured or Disabled, then run gpupdate /force and try updating again. After the update installs, you can re-enable the policy.

Common Related Questions

Here are answers to questions people often search alongside this error.

Can I ignore error 0x800f0954?

You can ignore it if the update is not critical and you are not experiencing issues, but it is better to fix it because the failed update may be a security patch. If the update is for .NET Framework, leaving it broken can cause applications that rely on that framework to malfunction.

Will resetting Windows fix 0x800f0954?

Resetting Windows (Settings > System > Recovery > Reset PC) can fix the error because it reinstalls the operating system and clears corrupted components. However, it is a last resort because you will need to reinstall your apps and restore your files from a backup. Try the manual fixes first.

Is 0x800f0954 the same as 0x800f0950?

No, they are different codes. 0x800f0950 often indicates a missing update source or a problem with the Windows Update service, while 0x800f0954 is specifically tied to component servicing failures, often with .NET Framework. The fixes overlap, but the exact cause can differ.

Preventing 0x800f0954 in the Future

If you manage a WSUS environment, make sure the .NET Framework updates are synchronized and approved. For individual users, keeping the Windows Update service healthy and not manually deleting the SoftwareDistribution folder (unless following the steps above) helps prevent this error. Also, avoid using third-party “update cleaner� tools that may remove files Windows Update still needs.

When to Seek Professional Help

If you have tried all the steps above and the error persists, it may indicate a deeper system corruption or a network issue that requires a domain administrator or IT professional. For home users, contacting Microsoft Support or posting on the Microsoft Community forums with your Windows version and the exact update KB number can provide more specific guidance.

Frequently Asked Questions

Why does 0x800f0954 happen only for .NET Framework updates?

.NET Framework updates are often delivered as “payload� files that need to be sourced locally. When WSUS is configured but does not have those payloads, the client cannot pull them, causing the error. Other updates that are fully hosted on WSUS install fine.

Do I need to be an administrator to fix this?

Yes, most fixes require administrative privileges because you need to stop services, rename system folders, or change Group Policy. If you are on a work computer, contact your IT department.

Can I use the Microsoft Update Catalog on any Windows version?

Yes, the catalog supports Windows 10, Windows 11, and Windows Server. Just make sure you download the update that matches your system architecture and edition (Home, Pro, etc.).

What if the update is already installed but still shows as failed?

Sometimes the update actually installs but the status is not refreshed. Check the installed updates list (Settings > Windows Update > Update history) to see if the KB is listed. If it is, the error may be a reporting glitch, and you can ignore it.

Is there a way to force Windows Update to ignore WSUS temporarily?

Yes, you can change the registry value HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU and set UseWUServer to 0, then restart the Windows Update service. This is a temporary workaround; remember to set it back to 1 after the update.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →