Windows command guide
Fix Windows Update error 0x800f0900
Windows Update error 0x800f0900 usually points to damaged servicing metadata or corrupted update components. This page focuses on a fast repair path built around DISM and SFC instead of random cleanup steps.
This guide is written around the specific symptom-command match for fix windows update error 0x800f0900, not as a generic dump of terminal lines. That makes the page more useful for real troubleshooting and reduces the chance of running the wrong repair step.
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow
Best place to run it
Elevated Command Prompt is the right execution context for this page. Because this repair touches protected Windows state, a normal unelevated shell can return misleading access errors or partial results.
Fast repair workflow
- Start from the exact symptom on this page: Windows Update downloads updates but fails during install with 0x800f0900
- Run the primary repair line exactly as shown: DISM /Online /Cleanup-Image /ScanHealth DISM /Online /Cleanup-Image /RestoreHealth sfc /scannow.
- This workflow is tuned for this repair, so avoid mixing it with unrelated repair commands too early.
- Reboot if the servicing stack or protected files were changed, then retry the original Windows action.
- Escalate only after reading the output, usually toward CBS.log, DISM source repair, or Windows Update-specific repair.
Copyable wrapper script
Use this wrapper when you want the page command inside a clearer script block with start and finish prompts.
@echo off
echo Run this CMD sequence in an elevated Command Prompt.
echo Starting targeted repair sequence...
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow
echo.
echo Review the output before closing this window.
pause
Verification commands after the repair
These follow-up commands help you check whether the repair actually changed the Windows state that matters, instead of assuming success from a single line.
findstr /c:"[SR]" %windir%LogsCBSCBS.log
sfc /verifyonly
What problem this command is trying to solve
This page targets update failures where Windows can still boot, but the servicing stack cannot complete an update because the repair source or component state is inconsistent.
- Windows Update downloads updates but fails during install with 0x800f0900.
- Repeated retry attempts end with the same code.
- DISM or SFC is often needed before update installation succeeds again.
How the command works
The command sequence checks the component store, attempts to repair it, and then verifies protected system files. That usually restores the servicing pieces Windows Update depends on.
When it makes sense to run it
Use it when the machine is otherwise usable but update installation keeps failing with the same code.
Before you run this command
- Open an elevated Command Prompt or PowerShell window before running DISM /Online /Cleanup-Image /ScanHealth DISM /Online /Cleanup-Image /RestoreHealth sfc /scannow.
- Confirm that the symptom really matches this guide, especially if you are seeing signs such as: windows update downloads updates but fails during install with 0x800f0900.
- Keep any exact DISM, SFC, CBS, or Windows Update error output because those details matter in the next step.
What result to expect
After running DISM /Online /Cleanup-Image /ScanHealth DISM /Online /Cleanup-Image /RestoreHealth sfc /scannow, compare the result against the symptom that brought you here. The most useful checkpoint is whether windows update downloads updates but fails during install with 0x800f0900 becomes less frequent, changes form, or produces a clearer error message. A command page is stronger when it helps you verify a real change instead of just assuming the line must have worked.
How to verify that it worked
The best verification step after DISM /Online /Cleanup-Image /ScanHealth DISM /Online /Cleanup-Image /RestoreHealth sfc /scannow is to repeat the action that previously triggered the problem. If repeated retry attempts end with the same code still appears in exactly the same way, the command probably was not the whole answer and you should move to the next targeted check instead of assuming the page is finished.
Why administrator rights matter here
This command changes system integrity and component corruption. Run it in an elevated shell so Windows can apply the repair instead of only returning an access or privilege error.
Before you run it
Run the commands in an elevated terminal and allow DISM to finish fully even if progress pauses for a while.
When this is probably the wrong fix
This is not the right first fix for a single third-party app bug, a browser-only issue, or obvious hardware failure. Use it when the symptom points to Windows image health, recurring update corruption, or protected system files.
What to do if it does not help
If DISM /Online /Cleanup-Image /ScanHealth DISM /Online /Cleanup-Image /RestoreHealth sfc /scannow does not improve windows update downloads updates but fails during install with 0x800f0900, move to the next repair step that matches the same symptom family instead of piling on random commands. The best follow-up depends on whether the failure is mainly about system integrity and component corruption.
Frequently asked questions
Should I use DISM /Online /Cleanup-Image /ScanHealth DISM /Online /Cleanup-Image /RestoreHealth sfc /scannow for this exact Windows symptom?
Use it when the behavior on your PC lines up with the repair target on this page: This page targets update failures where Windows can still boot, but the servicing stack cannot complete an update because the repair source or component state is inconsistent.
What should I check right after DISM /Online /Cleanup-Image /ScanHealth DISM /Online /Cleanup-Image /RestoreHealth sfc /scannow?
Check whether the original trigger still reproduces the same failure. For this page, a useful checkpoint is whether windows update downloads updates but fails during install with 0x800f0900 becomes less frequent, changes form, or points you toward a more specific next step.
When should I not rely on DISM /Online /Cleanup-Image /ScanHealth DISM /Online /Cleanup-Image /RestoreHealth sfc /scannow alone?
This is not the right first fix for a single third-party app bug, a browser-only issue, or obvious hardware failure. Use it when the symptom points to Windows image health, recurring update corruption, or protected system files.