KB5058411 not installing on your Lenovo is the kind of problem that rewards method and punishes impatience. Every blind retry re-downloads the package, re-runs the same failing install, and teaches you nothing. The method is simple: bring Lenovo’s firmware current, repair Windows’ pipeline, and install manually if the automatic path keeps looping.

This is the same fix order that resolves nearly every Lenovo cumulative-update failure, applied specifically to KB5058411. An hour of ordered work beats a week of hopeful retrying.

The single most skipped step — and the single most effective one — is updating Lenovo’s own firmware before touching Windows. People assume their drivers are current because Windows never complained, but Windows does not check your BIOS age until an update’s validation fails against it. Vantage takes ten minutes and eliminates the entire Lenovo-specific variable set, which is why it comes before every Windows-side repair in this guide.

Why this happens

  • Outdated Lenovo BIOS: Install-phase validation failing against old firmware.
  • Stale chipset/storage drivers: Factory driver versions the installer no longer accepts.
  • Lenovo background utilities: File locks from Vantage components or legacy tools.
  • Corrupted update cache: Damaged package data failing verification repeatedly.
  • Trial security software: Filter drivers blocking the install phase.
  • Low disk space: Staging failures on nearly full drives without clear errors.
  • Interrupted prior update: Half-applied states the new KB cannot reconcile.
  • Component store damage: WinSxS corruption failing pre-install checks — the shared root with the KB5050009 Lenovo failure .

How to fix it

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

Fix 1: Capture the error code

  1. Settings → Windows Update → Update history: click the failed KB5058411 for the exact code.
  2. Event Viewer → Windows Logs → Setup: note failure-time errors and any named driver.
  3. Screenshot both — the code is your map for everything below.
  4. Also record your BIOS version via msinfo32 for the firmware comparison in Fix 2.
  5. Two minutes of evidence-gathering prevents an hour of wrong-direction work. Future you, troubleshooting the next failed KB, will be grateful for the habit.

Fix 2: Update Lenovo’s stack through Vantage

  1. Open Lenovo Vantage (Microsoft Store if missing) and run Check for updates.
  2. Install all: prioritize BIOS, chipset, Intel RST/storage, power management.
  3. BIOS rules: charger plugged in, battery charged, everything closed, hands off until self-reboot.
  4. Allow a full settle after reboot — firmware changes can trigger a second restart.
  5. Retry the KB immediately; most Lenovo cases end here.
  6. If Vantage reports everything current but the support site shows a newer BIOS, trust the website — Vantage’s catalog occasionally lags a release behind.

Fix 3: Cross-check on the Lenovo support site

  1. Enter your serial at the Lenovo support site .
  2. Compare BIOS/chipset versions against installed; manually install anything newer.
  3. Grab the latest storage driver — the most common silent blocker on Lenovos.
  4. Reboot after firmware; batch driver-only installs.
  5. Retry once more and compare the error code to the original.

Fix 4: Clear third-party antivirus

  1. Uninstall (not disable) trial antivirus via Settings → Apps.
  2. Reboot with Windows Security active.
  3. Retry KB5058411.
  4. Reinstall preferred protection afterward if desired.
  5. Disabled suites still load filter drivers — only uninstalling truly removes them.
  6. If you rely on a third-party suite, reinstall the latest version from the vendor afterward; old installers reintroduce the same outdated filters.

Fix 5: Reset the update components

  1. Elevated prompt: net stop wuauserv, net stop cryptSvc, net stop bits, net stop msiserver.
  2. Rename: ren C:\Windows\SoftwareDistribution SoftwareDistribution.old, ren C:\Windows\System32\catroot2 catroot2.old.
  3. Restart services; check for updates.
  4. Retry on the clean pipeline.
  5. Firmware-current plus cache-clean ends the great majority of stubborn cases.

Fix 6: Repair the system image

  1. DISM /Online /Cleanup-Image /RestoreHealth to completion, elevated.
  2. sfc /scannow; reboot.
  3. Retry the update; compare codes.
  4. Microsoft documents these on the Windows support hub .
  5. Note unrepairable corruption — Fix 8’s in-place upgrade becomes the plan.
  6. If DISM completes but SFC still finds unfixable files, run DISM once more after the SFC pass; the two tools repair different layers and sometimes need to alternate.

Fix 7: Manual install from the catalog

  1. Download KB5058411 x64 from the Microsoft Update Catalog .
  2. Close apps, disconnect VPN, run the .msu.
  3. Reboot; verify in Update history.
  4. The standalone installer skips the pipeline entirely.
  5. Manual plus current firmware succeeds where automatic looping failed.
  6. Keep the downloaded .msu file for a week; if a future update exhibits the same behavior, you will already know the manual path works on your machine.

Fix 8: Clean boot and in-place upgrade

  1. msconfig: hide Microsoft services, disable rest and startup apps, reboot, retry.
  2. Still failing? Mount a Windows 11 ISO, run setup, Keep personal files and apps.
  3. The in-place upgrade rebuilds the OS around your data.
  4. Re-run Vantage afterward to re-register Lenovo drivers.
  5. If your machine also fails updates immediately after reinstalls, the Lenovo clean-install guide covers that scenario.

Closing

KB5058411 on a Lenovo fails for stack reasons, not update reasons: stale firmware, a corrupted pipeline, or a third-party filter. Update through Vantage and the support site, strip trial antivirus, reset the components, repair the image, and install manually when the automatic path loops. Then stay current — monthly Vantage checks and 20 GB of free space — and cumulative updates will install the way they should: silently, in the background, while you do literally anything else. The laptops that fight updates are almost always the ones whose firmware has not been touched since unboxing; ten minutes a month in Vantage is the cheapest insurance in computing.

Frequently asked questions

How do I know whether the failure is Lenovo-specific or general?
Update Lenovo’s BIOS and drivers through Vantage first, then retry. If the KB installs, it was Lenovo-specific. If it fails with the identical code on fully current firmware, the problem is in Windows’ pipeline — cache, component store, or a third-party filter — and the Windows-side fixes apply regardless of brand.
My Lenovo is out of warranty — can I still get driver updates?
Yes. Lenovo publishes drivers and BIOS updates on its support site for years after warranty expiry; warranty covers repairs, not downloads. Enter your serial number on the support site and install what’s offered. Age alone is never a reason to run ancient firmware.
Should I install optional driver updates from Windows Update too?
For the core fix, prioritize Lenovo’s own drivers over Windows Update’s optional ones — Lenovo’s packages are validated for your exact model. Windows Update’s optional drivers are fine as a supplement afterward, but they should not be your first source on Lenovo hardware.
What is the fastest way to retry after each fix?
Settings, Windows Update, Check for updates — then watch Update history for the result and the code. Do not batch three fixes and retry once; retry after each change so you know which step actually fixed it. That discipline saves enormous time across a laptop’s lifetime.