Windows Update Error 0x800F0805 — What It Means & How to Fix It

What Does This Error Mean?

Windows Update error 0x800F0805 means Windows cannot stage or prepare a component update package. This typically happens when the Windows component store (WinSxS) has corrupted or inconsistent entries that prevent a new package from being correctly installed. It is most commonly triggered during feature updates or large cumulative updates.

Affected Models

Windows 10
Windows 11
Windows 8.1

Common Causes

The Windows component store (WinSxS folder) has corrupted entries that conflict with the incoming update package
A previous update installed incompletely, leaving the component store in a partially updated state
Disk space is critically low, preventing the update from staging its files
The CBS (Component-Based Servicing) log shows failed transactions from a prior update attempt
File system corruption on the Windows drive prevents the update staging process from completing

How to Fix It

Check that you have enough free disk space. Open File Explorer and right-click your C: drive > Properties. Windows needs at least 10 to 20 GB of free space to stage a major update. If you are low on space, use the Disk Cleanup tool (search for it in Start) and clear Temporary files and Windows Update Cleanup.

Staging an update requires extracting and temporarily storing all update files alongside the current ones. If there is not enough room, the staging process fails with this error.
Run DISM to repair the component store. Open Command Prompt as Administrator and type: DISM /Online /Cleanup-Image /RestoreHealth — then press Enter. This downloads clean component data from Microsoft and repairs corrupted entries.

This directly fixes the most common cause of 0x800F0805. Allow up to 30 minutes. Your PC needs an active internet connection for DISM to download repair files.
Run System File Checker after DISM. In the same Administrator Command Prompt, type: sfc /scannow — then press Enter. SFC uses the now-repaired component store to fix corrupted system files that may be causing staging failures.

Run SFC after DISM, not before. DISM repairs the source that SFC draws from, making SFC more effective.
Clear the Windows Update cache completely. Stop the Windows Update service: net stop wuauserv — then delete the cache folder: rd /s /q C:\Windows\SoftwareDistribution — then restart the service: net start wuauserv. Try the update again.

Corrupted partially downloaded update packages in the cache can cause staging failures. A fresh download starts the process cleanly.
Run the CBS log cleanup with DISM. Open Command Prompt as Administrator and type: DISM /Online /Cleanup-Image /StartComponentCleanup — then press Enter. This cleans up outdated and superseded component store entries that can block new packages from staging correctly.

This command removes old component versions that are no longer needed. It can free up GB of space in WinSxS and resolve staging conflicts caused by leftover outdated entries.

When to Call a Professional

If DISM and SFC repairs do not fix the component store and you cannot perform an in-place upgrade, a technician can attempt a manual component store repair or a clean Windows installation while preserving your data.

Frequently Asked Questions

What is 'staging' an update?

Before Windows installs an update, it first 'stages' it — meaning it copies all the new files to a temporary location, checks them for integrity, and prepares the swap. Only after successful staging does Windows replace the current files with the new ones. This two-step process ensures that if anything goes wrong during staging, your current Windows files are untouched. When staging fails with 0x800F0805, no changes have been made to your system yet.

Why does DISM need an internet connection?

DISM's RestoreHealth command downloads fresh, uncorrupted component data directly from Microsoft's Windows Update servers. This ensures the repair source itself is not corrupted. If your internet connection is unavailable, you can alternatively use a Windows ISO file as the repair source: DISM /Online /Cleanup-Image /RestoreHealth /Source:D:\Sources\install.wim — where D: is your mounted Windows ISO.

How do I know if DISM actually fixed anything?

After DISM completes, look at the last few lines of output. If it says 'The restore operation completed successfully,' it found and fixed corrupted entries. If it says 'No component store corruption was detected,' the component store is clean — the problem is elsewhere. The full DISM log is saved at C:\Windows\Logs\DISM\dism.log for detailed review.