How to Fix Windows Update Error 0x800f0805

Understanding Error 0x800f0805: Component Store Corruption

Error code 0x800f0805 translates to "CBS_E_INVALID_PACKAGE" in Windows terminology, meaning the Component-Based Servicing system detected an invalid or corrupted package during installation. Here's what's happening internally:

• Component manifests corrupted: XML files describing component relationships are damaged
• CBS database inconsistency: The servicing stack's internal database has conflicting entries
• Pending operations stuck: Previous failed installations left the system in an inconsistent state
• .NET Framework conflicts: Multiple .NET versions interfering with each other
• System image damage: The Windows component store (WinSxS) is corrupted

Updates most commonly affected by 0x800f0805:

• .NET Framework cumulative updates (most frequent)
• Windows feature updates (e.g., version upgrades)
• Language pack installations
• Optional Windows components
• Cumulative security updates with large component changes
• Microsoft Visual C++ redistributables

Common triggers:

• Previous update installation interrupted by power loss or forced restart
• Disk errors corrupting component store files
• Third-party software modifying system files improperly
• Running system cleaners that delete critical component files
• Malware damage to CBS infrastructure

Method 1: Run Windows Update Troubleshooter

Always start with Microsoft's automated troubleshooter. It detects and repairs common CBS issues, pending update problems, and service configuration errors automatically.

Windows 11:

1. Press Windows + I to open Settings
2. Go to System → Troubleshoot → Other troubleshooters
3. Find Windows Update and click Run
4. Wait for the scan to complete (2-5 minutes)
5. If issues are detected, click Apply this fix
6. Restart your computer after troubleshooting completes
7. Check for updates again: Settings → Windows Update → Check for updates

Windows 10:

1. Open Settings → Update & Security → Troubleshoot
2. Click Additional troubleshooters
3. Select Windows Update and click Run the troubleshooter
4. Follow on-screen instructions
5. Restart and test

What this fixes: Stopped services, registry corruption, pending restarts, component registration issues, and basic CBS database problems. Success rate: ~40% for error 0x800f0805.

Method 2: Run DISM RestoreHealth with Component Cleanup

DISM (Deployment Image Servicing and Management) is specifically designed to repair Windows component store corruption—the primary cause of error 0x800f0805. This method is more effective than SFC for CBS-related issues.

1. Press Windows + X and select Terminal (Admin) or Command Prompt (Admin)
2. If prompted by UAC, click Yes
3. Step 1 - Check component store health:
4. Type: DISM /Online /Cleanup-Image /CheckHealth
5. Press Enter (completes in 10-30 seconds)
6. This performs a quick check without repairs
7. Step 2 - Scan for corruption:
8. Type: DISM /Online /Cleanup-Image /ScanHealth
9. Press Enter (takes 5-15 minutes)
10. This performs a thorough scan and reports corruption
11. Step 3 - Repair component store:
12. Type: DISM /Online /Cleanup-Image /RestoreHealth
13. Press Enter (takes 10-30 minutes)
14. Watch the progress percentage—do not close the window
15. If successful, you'll see "The restore operation completed successfully"
16. Step 4 - Clean up superseded components:
17. Type: DISM /Online /Cleanup-Image /StartComponentCleanup
18. Press Enter (takes 5-10 minutes)
19. This removes old component versions causing conflicts
20. For aggressive cleanup, use: DISM /Online /Cleanup-Image /StartComponentCleanup /ResetBase
21. Restart your computer
22. Try installing the failed update again

If DISM RestoreHealth fails: You'll see an error message like "Error: 0x800f081f - The source files could not be found." This means DISM needs access to clean Windows installation files. See Method 7 for using installation media as a repair source.

Method 3: Run System File Checker (SFC)

After DISM repairs the component store, run SFC to fix individual corrupted system files that may still be causing update failures.

1. Open Command Prompt (Admin) or Terminal (Admin)
2. Type: sfc /scannow
3. Press Enter
4. Wait for the scan to reach 100% (15-45 minutes)
5. Do not close the window or use your PC intensively during the scan
6. After completion, you'll see one of these results:
   • "Windows Resource Protection did not find any integrity violations" - No file corruption found
   • "Windows Resource Protection found corrupt files and successfully repaired them" - Issues fixed automatically
   • "Windows Resource Protection found corrupt files but was unable to fix some of them" - Need to run DISM again or use advanced methods
7. Check detailed results: findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log > "%userprofile%\Desktop\sfcdetails.txt"
8. This creates a report on your desktop showing which files were repaired
9. Restart your computer
10. Attempt the update installation again

Important sequence: Always run DISM before SFC. DISM repairs the component store (the source SFC uses for repairs), while SFC repairs individual files. Running them in reverse order reduces effectiveness.

Method 4: Clear Pending Update Operations

Error 0x800f0805 often occurs when previous update attempts left the CBS database in a "pending" state. Clearing these pending operations allows Windows to start fresh.

1. Open Command Prompt (Admin)
2. Stop Windows Update services:
3. net stop wuauserv
4. net stop cryptSvc
5. net stop bits
6. net stop msiserver
7. Navigate to the pending operations registry key:
8. reg delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\SessionsPending" /f
9. Delete pending.xml if it exists:
10. del /f /s /q C:\Windows\WinSxS\pending.xml
11. Clear the CBS temp folder:
12. del /f /s /q C:\Windows\System32\CatRoot2\*
13. Rename the component-based servicing logs:
14. ren C:\Windows\Logs\CBS\CBS.log CBS.old
15. Restart the services:
16. net start wuauserv
17. net start cryptSvc
18. net start bits
19. net start msiserver
20. Restart your computer
21. Windows will rebuild the CBS database from scratch
22. Try installing updates

Warning: This method resets pending update operations. If you had partially installed updates, you may need to download them again. This is normal and necessary to fix the corruption.

Method 5: Repair or Reinstall .NET Framework

Since error 0x800f0805 most commonly affects .NET Framework updates, repairing or reinstalling .NET can resolve the underlying conflict.

Option A: Use .NET Framework Repair Tool (Easiest)

1. Download the official .NET Framework Repair Tool from Microsoft's website
2. Search for "Microsoft .NET Framework Repair Tool" on Microsoft's support site
3. Run the downloaded NetFxRepairTool.exe
4. Accept the license agreement
5. Click Next to start detection
6. The tool will scan for .NET Framework issues (takes 5-10 minutes)
7. If problems are found, click Next to repair them
8. Wait for repairs to complete
9. Restart your computer
10. Try Windows Update again

Option B: Uninstall and Reinstall .NET Framework 3.5

1. Press Windows + R, type appwiz.cpl, press Enter
2. Click Turn Windows features on or off (left sidebar)
3. Find .NET Framework 3.5 (includes .NET 2.0 and 3.0)
4. Uncheck it and click OK
5. Wait for it to uninstall, then restart
6. After restart, return to Turn Windows features on or off
7. Check .NET Framework 3.5 and click OK
8. Windows will download and reinstall it fresh
9. If installation fails, use DISM: DISM /Online /Enable-Feature /FeatureName:NetFx3 /All
10. Restart and test Windows Update

Option C: Install Latest .NET Framework Version

1. Visit Microsoft .NET Framework download page
2. Download the latest .NET Framework Runtime (currently .NET Framework 4.8.1)
3. Run the installer
4. Follow the installation wizard
5. Restart your computer
6. This often resolves conflicts between .NET versions

Method 6: Reset Windows Update Components Completely

This comprehensive reset restores all Windows Update components, CBS services, and related registrations to their default state.

1. Download Microsoft's official Windows Update Troubleshooter (advanced version)
2. Or manually reset using these Command Prompt commands (run as administrator):

Stop all services:

• net stop bits
• net stop wuauserv
• net stop appidsvc
• net stop cryptsvc

Delete queue files:

• Del "%ALLUSERSPROFILE%\Application Data\Microsoft\Network\Downloader\*.*"

Rename distribution folders (backup):

• ren %systemroot%\SoftwareDistribution SoftwareDistribution.bak
• ren %systemroot%\system32\catroot2 catroot2.bak

Reset BITS and Windows Update services to default security descriptors:

• sc.exe sdset bits D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU)
• sc.exe sdset wuauserv D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU)

Re-register Windows Update DLLs:

• regsvr32.exe /s atl.dll
• regsvr32.exe /s urlmon.dll
• regsvr32.exe /s mshtml.dll
• regsvr32.exe /s wuapi.dll
• regsvr32.exe /s wuaueng.dll
• regsvr32.exe /s wups.dll
• regsvr32.exe /s wups2.dll
• regsvr32.exe /s wuweb.dll

Reset Winsock and proxy:

• netsh winsock reset
• netsh winhttp reset proxy

Restart services:

• net start bits
• net start wuauserv
• net start appidsvc
• net start cryptsvc

Restart your computer and test updates.

Method 7: Use Installation Media as DISM Repair Source

When DISM's RestoreHealth fails because it cannot download repair files, use a Windows installation ISO as a local repair source.

1. Download Windows 11 ISO from Microsoft's website
2. Or Windows 10 ISO if that's your version
3. Right-click the ISO file and select Mount
4. Note the drive letter (e.g., D:)
5. Open Command Prompt (Admin)
6. Run DISM with the mounted ISO as source:
7. DISM /Online /Cleanup-Image /RestoreHealth /Source:D:\Sources\install.wim:1 /LimitAccess
8. Replace "D:" with your mounted drive letter
9. Wait for completion (10-30 minutes)
10. After successful repair, run SFC again: sfc /scannow
11. Restart your computer
12. Unmount the ISO: Right-click the drive → Eject
13. Try Windows Update

Alternative for Windows 10: If using install.esd instead of install.wim, first check the index number:

• DISM /Get-WimInfo /WimFile:D:\Sources\install.esd
• Find your Windows edition index (e.g., "Index: 6" for Windows 10 Pro)
• Use that index in the repair command: /Source:D:\Sources\install.esd:6

Method 8: Manually Install the Failed Update

If Windows Update continues failing, download and install the specific update manually via the Microsoft Update Catalog.

1. Identify the exact update failing (check Windows Update history for KB number)
2. Go to Microsoft Update Catalog
3. Search for the KB number (e.g., "KB5012345")
4. Find the version matching your Windows edition and architecture (x64 or x86)
5. Click Download
6. Save the .msu or .cab file
7. Double-click the downloaded file to install
8. Or use DISM for .cab files: DISM /Online /Add-Package /PackagePath:"C:\path\to\update.cab"
9. Wait for installation to complete
10. Restart if prompted
11. Verify installation in Windows Update history

For .NET Framework updates specifically:

• Search for the exact .NET update KB number
• Download the standalone installer from Microsoft's download center
• Run it directly (often more reliable than through Windows Update for .NET)

Method 9: Perform In-Place Upgrade (Repair Install)

When all else fails, an in-place upgrade reinstalls Windows while preserving your files and applications. This completely rebuilds the component store and CBS infrastructure.

1. Download the Media Creation Tool from Microsoft
2. Run the tool and select Upgrade this PC now
3. Wait for Windows to download (2-4 GB)
4. Accept license terms
5. Choose Keep personal files and apps
6. Click Install
7. Your PC will restart multiple times (30-90 minutes total)
8. Windows will be reinstalled with fresh CBS components
9. All your files, apps, and settings remain intact
10. After completion, Windows Update will work normally

What this fixes: Every type of component store corruption, CBS database issues, system file damage, and servicing stack problems. Success rate: 99% for error 0x800f0805.

Important: While this preserves your data, it's still wise to back up important files before proceeding. Use OneDrive, external drive, or File History.

Additional Troubleshooting for Error 0x800f0805

Check CBS.log for Specific Errors

The Component-Based Servicing log contains detailed information about what's failing:

1. Open File Explorer
2. Navigate to C:\Windows\Logs\CBS\
3. Open CBS.log with Notepad
4. Press Ctrl + F and search for "0x800f0805"
5. Read the surrounding lines to identify which component is failing
6. Common culprits: "NetFx" (.NET), "Microsoft-Windows-LanguagePack", "Foundation-Package"

Disable Third-Party Antivirus Temporarily

Antivirus software can interfere with CBS operations. Temporarily disable it during update installation:

• Right-click antivirus icon in system tray
• Select Disable protection or Pause
• Try the update again
• Re-enable protection after installation completes

Ensure Sufficient Disk Space

CBS operations require substantial temporary space:

• Check C: drive has at least 20 GB free
• Go to Settings → System → Storage
• Use Storage Sense or Disk Cleanup to free space
• Delete temporary files, downloads, and old Windows installations

Check for Malware

Malware can corrupt CBS components. Run a full scan:

• Open Windows Security: Windows + I → Privacy & security → Windows Security
• Go to Virus & threat protection
• Click Scan options
• Select Full scan and click Scan now
• Remove any detected threats
• Restart and run DISM again to repair any damage

Prevention: Maintain Component Store Health

• Install updates regularly (monthly) to prevent large backlogs
• Never force shutdown during "Getting Windows ready" or "Configuring updates"
• Run DISM /Online /Cleanup-Image /StartComponentCleanup quarterly
• Keep at least 20 GB free space on C: drive at all times
• Run SFC and DISM scans every 3-6 months as preventive maintenance
• Avoid using aggressive system cleaners that delete WinSxS files
• Create system restore points before major updates
• Keep backups of important data for disaster recovery

Frequently Asked Questions

Q: Why does error 0x800f0805 keep appearing after I fix it?

A: This usually indicates underlying disk corruption or malware damage continually re-corrupting the component store. Run CHKDSK (chkdsk C: /f /r /x), perform a full malware scan, and check your hard drive health using SMART monitoring tools. If the drive is failing, you may need to replace it and perform a clean Windows installation.

Q: Can I skip the failed update and install later ones?

A: Not recommended for cumulative updates or prerequisites. .NET Framework and servicing stack updates must install in order. However, you can hide optional updates using the "Show or hide updates" troubleshooter from Microsoft. Download it, run it, and hide the problematic update. Later updates may install successfully and supersede the failed one.

Q: What's the difference between DISM RestoreHealth and StartComponentCleanup?

A: RestoreHealth repairs corrupted components by downloading replacements from Windows Update. StartComponentCleanup removes old component versions after updates install, freeing disk space. Use RestoreHealth to fix corruption, then use StartComponentCleanup to prevent future conflicts from accumulated old files.

Q: Will an in-place upgrade delete my programs?

A: No, if you choose "Keep personal files and apps." The in-place upgrade preserves installed programs, personal files, and most settings. However, some drivers or Windows Store apps may need reinstalling. Windows.old folder is created as a backup. Note: Desktop programs stay, but you should still back up important data as a precaution.

Q: How do I know if the error is specifically .NET Framework related?

A: Check Windows Update history. If the failing update has "NET Framework" or "NetFx" in its name (e.g., "Cumulative Update for .NET Framework"), it's .NET-specific. Also check CBS.log for references to "NetFx" or "dotnet". In these cases, go directly to Method 5 (.NET repair) before trying other solutions.