KB5034765 failing on a Lenovo laptop — usually with error 0x800f0922 or a hang near the end of installation — is a known painful combination. The update itself is a standard cumulative package, but on Lenovo hardware it collides with firmware-level Secure Boot handling and occasionally with Lenovo’s own preinstalled utilities. The result is an update that downloads fine, installs to 95 percent, and then rolls back.

This guide is Lenovo-specific where it matters (BIOS, Vantage, firmware) and general where the problem is general (servicing stack, cache, manual install). Work it in order.

One caution before you begin: because this failure so often involves firmware, do every step on AC power with the battery charged above 50 percent. A power loss during a BIOS flash or a cumulative install turns a fixable software problem into a machine that will not POST. Keep Lenovo Vantage closed while you work so its background updater does not race the repairs below.

Why this happens

  • Secure Boot configuration mismatch: The update validates boot components against Secure Boot policy; Lenovo firmware with outdated certificates or nonstandard settings fails the check.
  • Outdated Lenovo BIOS: Older BIOS versions mishandle the EFI variables the update touches, triggering 0x800f0922 during the final phase.
  • Corrupted servicing stack: Damage from a previous failed update leaves the component store unable to stage this cumulative package.
  • Lenovo Vantage interference: Vantage’s own update and power-management hooks occasionally lock files the cumulative installer needs to replace.
  • Damaged EFI partition: A corrupted or nearly-full EFI system partition breaks the boot-file updates bundled in the cumulative package.
  • Third-party disk encryption: Encryption filter drivers can block the low-level file operations the installer performs near completion.
  • Stale update cache: A corrupted download of this specific KB fails hash checks at install time, producing the same rollback every attempt.

How to fix it

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

Fix 1: Update the Lenovo BIOS first

  1. Open Lenovo Vantage (or go to Lenovo support ) and check for a BIOS update newer than your installed version.
  2. Install the BIOS update on AC power with a charged battery — do not interrupt it.
  3. Enter the BIOS after the flash and confirm Secure Boot is Enabled with the standard Microsoft keys (not custom or cleared keys).
  4. Retry KB5034765 via Windows Update; a large share of Lenovo-specific failures end at this step.

Fix 2: Repair the servicing stack

  1. Open an elevated Command Prompt and run DISM /Online /Cleanup-Image /RestoreHealth.
  2. Follow with sfc /scannow and restart the laptop.
  3. The 0x800f0922 error is frequently a servicing-stack problem wearing a Lenovo mask — a healthy component store lets the installer stage correctly.
  4. After the restart, check for updates before trying anything more drastic.

Fix 3: Clear the corrupted download

  1. Stop the update services: net stop wuauserv, net stop bits, net stop cryptSvc.
  2. Rename C:\Windows\SoftwareDistribution to SoftwareDistribution.old and restart the services.
  3. Check for updates again to pull a fresh copy of KB5034765.
  4. A fresh download eliminates the corrupted-payload failures that mimic firmware problems.

Fix 4: Temporarily quiet Lenovo Vantage and third-party tools

  1. Open Lenovo Vantage and pause any pending Vantage-driven updates (BIOS, drivers) so they do not race the cumulative install.
  2. Temporarily disable third-party antivirus real-time protection and disconnect any disk-encryption pre-boot tools if applicable.
  3. Retry the update with the field clear of competing installers.
  4. Re-enable everything afterward. If driver updates are also failing , handle them separately after this KB is in.

Fix 5: Check the EFI partition health

  1. In an elevated Command Prompt, run mountvol S: /s to mount the EFI partition, then S: and dir to inspect it — it should not be full.
  2. Run bcdedit /enum and confirm the boot entries look sane (Windows Boot Manager pointing at the right partition).
  3. If the EFI partition is damaged, the safest repair is bcdboot C:\Windows /s S: /f UEFI from recovery media — do not improvise here.
  4. Dismount with mountvol S: /d when done.

Fix 6: Install KB5034765 manually from the Update Catalog

  1. Go to the Microsoft Update Catalog and search for KB5034765.
  2. Download the x64 package matching your Windows build and run it — the standalone installer bypasses the Windows Update client entirely.
  3. Keep the laptop plugged in and idle during the install; do not run Vantage updates simultaneously.
  4. Verify in Settings > Windows Update > Update history that the KB shows as successfully installed.

Fix 7: Reset the update components as a last resort

  1. Run the full manual reset: stop wuauserv, cryptSvc, bits, msiserver; rename SoftwareDistribution and Catroot2; restart all four services.
  2. Run the Windows Update troubleshooter to confirm the pipeline is healthy.
  3. Retry via Windows Update one final time.
  4. If it still fails after BIOS, servicing repair, fresh cache, and manual install, collect the CBS logs (C:\Windows\Logs\CBS) — at that point the failure signature is specific enough for Lenovo support or the Microsoft forums.

Fix 8: Attempt the install from a clean boot

  1. Press Win + R, type msconfig, and on the Services tab tick Hide all Microsoft services, then Disable all; disable third-party startup items in Task Manager too.
  2. Restart into this clean state and install KB5034765 — either via Windows Update or the Catalog package from Fix 6.
  3. If it succeeds here, a third-party driver or service was the blocker; re-enable items in halves to identify it, then update or remove the offender.
  4. Return msconfig to Normal startup afterward and restart once more so the machine runs its full software load.

Closing

KB5034765 on Lenovo hardware is a firmware-first problem: update the BIOS, verify Secure Boot, repair the servicing stack, clear the cache, and install manually if the pipeline still balks. Most of these failures surrender at the BIOS step — the rest need the methodical work above. Either way, the update goes on, the error clears, and Patch Tuesday stops being an event.

Frequently asked questions

What does error 0x800f0922 mean with KB5034765?
Error 0x800f0922 means the installer could not load a required component during the update, most often tied to Secure Boot configuration or a damaged servicing stack. On Lenovo laptops it frequently traces to firmware-level Secure Boot settings conflicting with the update’s expectations. Updating the Lenovo BIOS resolves most instances, because newer firmware handles the Secure Boot variables the installer validates.
Why does this update fail specifically on Lenovo machines?
Lenovo’s firmware and preinstalled utilities interact with Secure Boot and the EFI partition in ways that occasionally clash with cumulative updates. Outdated Lenovo BIOS versions are the most common machine-specific trigger for this failure. The pattern is consistent enough that a BIOS update is always the first step on Lenovo hardware, before any generic Windows repairs.
Will the manual installer from the Update Catalog work better?
Often yes. The standalone package bypasses the Windows Update delivery cache and its integrity checks, installing directly. If the failure is in the download or staging pipeline rather than the payload itself, the manual install succeeds. Use it after the BIOS and servicing repairs, not instead of them — the manual installer still needs a healthy servicing stack underneath.
Should I disable Secure Boot to install the update?
No — do not disable Secure Boot as a workaround. The correct fix is updating the BIOS and repairing the servicing components so the update installs with Secure Boot intact. Disabling it weakens the machine’s boot security for no lasting benefit. The correct path is always to make the update work with Secure Boot enabled, not to dismantle a security boundary for convenience.