These two codes account for a large share of the update failures we see. They mean different things, and knowing which you have saves a lot of wasted effort.
What the Codes Mean
- 0x800f0983 — component store corruption. Windows cannot reconcile its own servicing files.
- 0xc1900101 — a driver problem during the upgrade phase. Almost always a specific driver failing at the migration step.
The Order We Work Through It
- Free up space. 20GB minimum on C:. Insufficient space causes failures that masquerade as corruption.
- Run the built-in troubleshooter. Settings → System → Troubleshoot → Other troubleshooters → Windows Update. It genuinely fixes a fair share.
- Repair the component store. In an admin Command Prompt, run
DISM /Online /Cleanup-Image /RestoreHealth, thensfc /scannow. In that order — SFC alone cannot repair a broken store. - Reset the update components. Stop wuauserv and bits, rename C:\Windows\SoftwareDistribution to SoftwareDistribution.old, restart the services.
- For 0xc1900101, hunt the driver. Disconnect every non-essential USB device. Update or temporarily uninstall graphics, storage controller and security software drivers. Third-party antivirus is a repeat offender — remove it, update, reinstall it.
- Try the Installation Assistant or a mounted ISO for an in-place upgrade that keeps files and apps.
Before You Start Any of This
Back up, and locate your BitLocker recovery key. Steps four and five touch the servicing stack, and a machine that reboots into a recovery prompt without its key is a data loss event.
MediaVision Technical Analysis
If DISM itself fails, you usually need a repair install from an ISO rather than more command-line attempts — that is the point where continuing to try commands wastes time. An in-place upgrade repair keeps your files and programs and fixes the underlying corruption in most cases.
If you would rather not do this yourself, bring it in. We image the drive before touching anything, so there is no scenario where troubleshooting costs you your data.
