Error 0x800F0900 means the update installer could not read the manifest files — the XML documents that describe what an update contains and how to install it. Your Lenovo laptop downloaded the instructions but cannot decipher them, so the installation never meaningfully begins.

This is a data-delivery problem far more often than a system-damage problem: the instructions arrived garbled. If the manifests parse fine but the components do not match, the 0xC1900101 driver-block guide covers that later-stage failure.

The remedy is refreshingly direct: throw away the unreadable manifests and fetch clean ones. Cache resets resolve the overwhelming majority of these cases.

Why this happens

  • A corrupted download: Manifests damaged in transit fail XML parsing on arrival — large updates over flaky connections are the usual source.
  • A poisoned update cache: The SoftwareDistribution store can hold damaged manifests from earlier attempts, and every retry reuses them.
  • Disk write errors: Bad sectors or a struggling drive can corrupt manifests as they are written to the cache.
  • Antivirus mangling downloads: Scanners that modify or quarantine parts of a download can leave manifests structurally invalid.
  • Botched download resumption: A resumed download that stitches chunks together incorrectly produces a manifest that is complete but internally inconsistent.
  • Failing RAM: Memory errors can corrupt data passing through during download or extraction, damaging manifests before they reach the disk.
  • Genuine metadata mismatch: Rarely, the published metadata and the payload truly disagree — in which case waiting for Microsoft to republish is the only fix.

How to fix it

Work through these in order — diagnose first, then act.

Fix 1: Renew the update components

Start with the cache, because the cache is almost always the culprit. Stopping the update services and renaming the SoftwareDistribution and catroot2 folders forces Windows to rebuild them cleanly — fresh permissions, no stale pending operations, and above all no damaged manifests being recycled into every retry. Renaming the SoftwareDistribution folder is Microsoft’s standard cache reset — documented in the official Windows support hub .

  1. Fire up an elevated Command Prompt by right-clicking Start and hitting Terminal (Admin).
  2. Bring the four services to a stop — net stop wuauserv, net stop cryptSvc, net stop bits, net stop msiserver.
  3. Rename SoftwareDistribution and catroot2 out of the way: ren C:\Windows\SoftwareDistribution SoftwareDistribution.old and ren C:\Windows\System32\catroot2 catroot2.old.
  4. Bring all four services online via net start, then re-check for updates.

Fix 2: Flush DNS and reset the network stack

If the manifests keep arriving damaged, the delivery path is suspect. Stale DNS entries, corrupted socket configurations, and leftover proxy settings can all degrade the connection to Microsoft’s update servers. Resetting the stack returns networking to a known-good default without touching files or apps.

  1. Bring up an elevated Command Prompt window.
  2. Enter ipconfig /flushdns, then netsh winsock reset, then netsh int ip reset.
  3. Reboot the laptop to apply the reset.
  4. Get back online and attempt the update on the reset network.

Fix 3: Check the disk for bad sectors

A drive that corrupts data on write will keep producing unreadable manifests no matter how clean the downloads are. A disk check scans for physical defects and relocates data away from damaged areas, stopping the corruption at its source.

  1. Launch an elevated Command Prompt.
  2. Execute chkdsk C: /f /r and confirm it for the next reboot.
  3. Restart the machine and allow the complete scan; it can take an hour on big drives.
  4. Retry the update after a clean disk check.

Fix 4: Temporarily disable third-party antivirus

Security suites that intercept downloads sometimes alter or quarantine pieces of the package, leaving manifests structurally invalid — and the resulting errors never name the antivirus. Pausing real-time protection for one install is a legitimate diagnostic, with Windows Defender covering you in the meantime.

  1. Launch your security suite and pause its real-time protection.
  2. Attempt the Windows Update install while protection is off.
  3. Switch protection back on right after the installation finishes.
  4. If this resolves it, add the updater to your suite’s exclusion list so next month’s update goes smoothly.

Fix 5: Install the update manually from the Update Catalog

Bypass the whole automatic pipeline. Downloading the package yourself skips the broken download path and hands you pristine manifests straight from the source. Every cumulative update is available on the Microsoft Update Catalog as a standalone installer. A clean copy from the Microsoft Update Catalog replaces every damaged manifest with a readable one.

  1. Open Windows Update in Settings, check Update history, and write down the failing KB number.
  2. Search the Microsoft Update Catalog for the KB number and open its page.
  3. Get the x64 download built for your Windows 11 release.
  4. Open the .msu file you downloaded, complete the installer, and restart when prompted.

Fix 6: Fix corrupted files with the System File Checker

The parser itself depends on healthy system files. Corrupted Windows files can break the update installer in subtle ways, and the System File Checker exists to find and replace them — scanning every protected file against a known-good copy and repairing damage, which removes a whole class of update failures.

  1. Start an elevated Command Prompt or Terminal (Admin).
  2. Key in sfc /scannow, hit Enter, and wait for the scan.
  3. If repairs were made, restart the laptop.
  4. Try installing the update again post-restart.

Fix 7: Repair the component store with DISM

When the index the installer draws from is damaged, updates fail even though every visible file looks fine. DISM checks the component store (WinSxS) against healthy online sources and repairs the damage SFC cannot reach on its own.

  1. Open an elevated Command Prompt.
  2. Run DISM /Online /Cleanup-Image /RestoreHealth and let it finish — this can take 15 to 30 minutes.
  3. When it completes, run sfc /scannow once more for good measure.
  4. Restart and try the update again.

Closing

Manifest parsing failures are shallow problems wearing a scary code: the instructions arrived garbled, so get new instructions. A cache reset plus a clean download ends nearly every case without touching system files. Lenovo owners can run Lenovo Vantage afterward to confirm drivers and firmware are current, since healthy servicing pairs well with healthy drivers. If corruption keeps recurring across fresh downloads, investigate the disk and memory — and if downloads themselves are the issue, the 0x8024500C redirector guide covers the connection-level causes.

Frequently asked questions

What does error 0x800F0900 mean?
It means CBS_E_XML_PARSER_FAILURE: the servicing stack could not parse the update’s manifest files. Manifests are XML documents describing the update’s contents and installation steps, and when they arrive damaged — bad downloads, poisoned cache, disk errors — the parser rejects them and the install aborts before doing anything. The answer is obtaining clean manifests through a cache reset and fresh download.
Why does the same update keep failing to parse?
Because Windows Update keeps reusing its cache. The damaged manifest from the first attempt stays in SoftwareDistribution, and every retry reads the same broken file. Renaming that folder forces a completely fresh download of manifests and payloads, which is why the component reset is the definitive fix. Without it, you can retry a hundred times with identical results.
Could my SSD be causing this?
Possibly, if corruption keeps recurring. Manifests are small, so repeated corruption across many different updates suggests the storage or memory is damaging data rather than the network. Run chkdsk with /r and test memory with mdsched if fresh downloads keep arriving corrupted. A healthy drive delivers clean manifests consistently, while a failing one corrupts them at random.
How is this different from 0x800F0988?
This one fails earlier. With 0x800F0900 the installer cannot even read the update’s description; with 0x800F0988 it reads the description fine but finds the system does not match it. Think of it as the difference between receiving a garbled letter and receiving a clear letter describing parts you do not own. The first needs fresh data, the second needs system cleanup.