Error 0x800f0955 0x20003 usually appears when a Windows update or feature installation fails, often during .NET Framework or language pack installation. The fix is to clear the Windows Update cache, run the DISM and SFC tools, and then retry the update; if that fails, reset Windows Update components manually.
What This Error Means
Windows error codes are hexadecimal values that point to a specific component. 0x800f0955 is a CBS (Component Based Servicing) error, meaning the Windows Update engine could not complete a servicing operation. The secondary code 0x20003 often relates to a corrupted or missing manifest file in the servicing store. In plain terms, Windows tried to add or modify a system component but found the source files or the store itself in an inconsistent state.
This error is most commonly reported when:
- Installing the .NET Framework 3.5 (which includes 2.0 and 3.0) via Windows Features
- Installing a language pack or optional feature
- Running a Windows feature update that needs to modify system files
It is not a hardware error and does not indicate a failing drive or RAM. It is purely a software servicing problem.
Why It Happens
Windows keeps a local component store (usually at C:\Windows\WinSxS) that holds all the files needed for updates and features. When you install a feature, Windows copies files from this store to the active system. If the store is corrupted, or if the update cache (C:\Windows\SoftwareDistribution) has stale or damaged downloads, the operation fails with 0x800f0955.
Common triggers include:
- An interrupted previous update that left the store in a bad state
- Disk cleanup tools that removed files the store still needs
- Third-party antivirus software interfering with file operations
- Insufficient disk space (though this usually gives a different code, it can contribute)
Before You Start: Basic Checks
Do these quick checks first; they solve a surprising number of cases:
- Restart your PC. A simple reboot clears temporary locks.
- Ensure you have at least 20 GB of free space on the C: drive. Windows needs room to expand the component store.
- Temporarily disable third-party antivirus (not Windows Defender) and try again.
- Run Windows Update again after a fresh boot.
If the error persists, move to the systematic fixes below.
Fix 1: Run DISM and SFC
These two built-in tools repair corrupted system files. Run them in order, from an elevated Command Prompt (search for “cmd”, right-click, “Run as administrator”).
- Type
DISM /Online /Cleanup-Image /RestoreHealthand press Enter. This repairs the component store. It can take 10-20 minutes. - After DISM finishes, type
sfc /scannowand press Enter. This checks and repairs protected system files. - Restart your PC and try the update again.
If DISM fails because it cannot find the source files, you may need to specify a Windows installation media. Insert a Windows USB or DVD, note the drive letter (e.g., D:), and run:
DISM /Online /Cleanup-Image /RestoreHealth /Source:D:\sources\install.wim /LimitAccess
Fix 2: Clear the SoftwareDistribution Folder
This folder stores downloaded updates. A corrupted download can cause the error. Clearing it forces Windows to re-download.
- Open an elevated Command Prompt.
- Type
net stop wuauservand press Enter. - Type
net stop bitsand press Enter. - Open File Explorer, go to C:\Windows, and rename the SoftwareDistribution folder to
SoftwareDistribution.old. - Go back to the Command Prompt and type
net start wuauservandnet start bits. - Restart and try Windows Update again.
Renaming (not deleting) is safer, as it lets you revert if something goes wrong.
Fix 3: Reset Windows Update Components Manually
If the above fails, a full reset of Windows Update components often works. This re-registers DLLs and clears policies. Do this in an elevated Command Prompt:
- Stop the services:
net stop wuauserv,net stop cryptSvc,net stop bits,net stop msiserver. - Rename the SoftwareDistribution and CatRoot2 folders (as in Fix 2, but also
ren C:\Windows\System32\catroot2 catroot2.old). - Reset the network and update policies:
netsh winsock resetandnetsh winhttp reset proxy. - Re-register the update DLLs. Type each of these lines separately, pressing Enter after each:
regsvr32.exe /s atl.dll
regsvr32.exe /s urlmon.dll
regsvr32.exe /s mshtml.dll
regsvr32.exe /s shdocvw.dll
regsvr32.exe /s browseui.dll
regsvr32.exe /s jscript.dll
regsvr32.exe /s vbscript.dll
regsvr32.exe /s scrrun.dll
regsvr32.exe /s msxml.dll
regsvr32.exe /s msxml3.dll
regsvr32.exe /s msxml6.dll
regsvr32.exe /s actxprxy.dll
regsvr32.exe /s softpub.dll
regsvr32.exe /s wintrust.dll
regsvr32.exe /s dssenh.dll
regsvr32.exe /s rsaenh.dll
regsvr32.exe /s gpkcsp.dll
regsvr32.exe /s sccbase.dll
regsvr32.exe /s slbcsp.dll
regsvr32.exe /s cryptdlg.dll
regsvr32.exe /s oleaut32.dll
regsvr32.exe /s ole32.dll
regsvr32.exe /s shell32.dll
regsvr32.exe /s initpki.dll
regsvr32.exe /s wuapi.dll
regsvr32.exe /s wuaueng.dll
regsvr32.exe /s wuaueng1.dll
regsvr32.exe /s wucltui.dll
regsvr32.exe /s wups.dll
regsvr32.exe /s wups2.dll
regsvr32.exe /s wuweb.dll
regsvr32.exe /s qmgr.dll
regsvr32.exe /s qmgrprxy.dll
regsvr32.exe /s wucltux.dll
regsvr32.exe /s muweb.dll
regsvr32.exe /s wuwebv.dll
5. Restart the services: net start wuauserv, net start cryptSvc, net start bits, net start msiserver.
6. Restart your PC and try the update again.
Fix 4: Use the Windows Update Troubleshooter
Windows includes an automated troubleshooter that can diagnose and fix common update problems. Go to Settings > Update & Security > Troubleshoot > Additional troubleshooters > Windows Update. Run it and follow the prompts. It may take a few minutes and will often reset the update components automatically.
When All Else Fails: Repair Install or Reset
If none of the above works, the component store may be too damaged for online repair. In that case, you can do an in-place upgrade (repair install) using the Windows Media Creation Tool. This reinstalls Windows while keeping your files and apps. Download the tool from Microsoft’s official site, run it, and choose “Upgrade this PC now”. It takes about an hour and usually fixes even stubborn servicing errors.
As a last resort, you can reset Windows via Settings > Update & Security > Recovery > Reset this PC. Choose “Keep my files” to remove apps but keep personal files, or “Remove everything” for a clean slate. This is drastic, so back up important data first.
Frequently Asked Questions
Will this error damage my computer?
No. It only prevents a specific update or feature from installing. Your system continues to work normally, though you may be missing that update or feature.
Can I ignore this error?
You can, but you may miss security updates or be unable to install needed features like .NET Framework. It’s best to fix it to keep your system fully updated.
Does this error affect Windows 10 and Windows 11 the same way?
Yes, the error code and fixes are essentially the same on both versions. The steps above work for Windows 10 and Windows 11.
Why does DISM fail with “source files not found”?
That means the component store is too damaged to repair itself. You need to specify a Windows installation media as the source, as shown in Fix 1.
How long do these fixes take?
DISM and SFC can take 15-30 minutes. The manual reset takes about 10 minutes. The repair install takes about an hour. Plan accordingly.
Is it safe to delete the SoftwareDistribution.old folder?
After you confirm the update works, you can delete it to free space. It only contains old update files. But wait a few days to be safe.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- Fix Apps Not Downloading From Play Store
- Secure a Samsung Galaxy After a Zero-Day Disclosure
- What to Check Before Installing Linux Alongside Windows
- Fix OEM Activation Error 0xc004c060 in Windows 10
- Why Does My App Run One Query for the List and One per Item?
- Fix Google Chrome Has Stopped Working