BIOS 0X80290302: The Firmware Update That Won't Install

1. Corrupted UEFI Capsule Update Cache

This is the most common cause. What's actually happening here is that Windows Update tries to apply a firmware update via the UEFI capsule mechanism — it places files in a special reserved partition. If that partition's cache gets corrupted (usually from a previous failed update or a power loss during the operation), the next update attempt hits 0X80290302 because the UEFI firmware rejects the payload as invalid or incomplete.

The fix is to clear the capsule cache manually. This doesn't touch your Windows install or personal files.

Clear the Capsule Cache

1. Open an elevated Command Prompt (right-click Start, choose Terminal (Admin)).
2. Run:

   del /f /q C:\Windows\Temp\CapsuleUpdate*.*

3. Then run:

   del /f /q C:\Windows\System32\CapsuleUpdate*.*

4. Restart your PC. Windows will rebuild the cache fresh.

The reason step 3 works is that Windows Update looks in System32 for pending capsule payloads. If that file is stale or corrupt, the update process aborts with 0X80290302 before it even hands off to the UEFI firmware.

If you see the error on an HP or Dell machine specifically, also check C:\Windows\Temp\HPBIOSUPD or C:\Dell\BIOS — those OEM tools sometimes leave orphaned installers. Delete those folders too.

2. BIOS Locked or Secure Boot Misconfiguration

If clearing the cache didn't fix it, the BIOS itself might be locked against capsule updates. This happens most often on corporate-managed PCs where IT policies disable firmware updates via Windows Update. But it can also happen after a BIOS update that changes Secure Boot keys unexpectedly.

The error 0X80290302 can also fire when Secure Boot is enabled but the UEFI firmware's key database doesn't trust the capsule's signature. This is rare on consumer hardware but common on Dell Precision or Lenovo ThinkPad systems running custom BIOS versions.

Check and Fix Secure Boot Settings

1. Reboot into your UEFI firmware settings (usually F2 or Del during boot).
2. Look for Secure Boot settings. If it says Custom (non-Microsoft keys), switch to Standard and save.
3. Also check BIOS Update or Firmware Update option — if it's disabled, enable it. On HP systems it's under Advanced > Firmware Update > Enable UEFI Capsule Updates.
4. Save and exit. Then try the update again via Windows Update (Settings > Windows Update > Check for updates).

Don't touch Secure Boot settings unless you're sure. Switching from Custom to Standard can break boot if your OS was installed with custom keys. If you're dual-booting Linux, this can brick the bootloader.

3. Stuck Pending Update in Windows Update Queue

Sometimes the error is a red herring — the real problem is a stuck driver or feature update that's blocking the firmware update from running. Windows Update queues multiple updates, and if one fails, everything behind it shows a generic error.

Reset the Windows Update Components

1. Run Command Prompt as admin.
2. Stop the update services:

   net stop wuauserv && net stop cryptSvc && net stop bits && net stop msiserver

3. Rename the SoftwareDistribution folder:

   ren C:\Windows\SoftwareDistribution SoftwareDistribution.old

4. Restart the services:

   net start wuauserv && net start cryptSvc && net start bits && net start msiserver

5. Reboot and check for updates again.

This brute-force reset is safe. The old folder gets orphaned and Windows rebuilds the update history from Windows Update servers. The firmware update will re-queue fresh.

One specific trigger for this: I've seen it on HP Spectre x360 models after a Windows feature update (22H2 -> 23H2) that partially failed and left the firmware update in a perpetual pending state.

4. Legacy BIOS Mode Installed on GPT Disk

If your Windows installation is in legacy BIOS (CSM) mode but your disk is GPT, some firmware update mechanisms get confused. The capsule update path requires UEFI mode. You can check this:

msinfo32.exe

Look for BIOS Mode. If it says Legacy, you can't apply UEFI capsule updates directly. You'd need to convert to UEFI mode — which is risky on a running system.

The workaround is to download the BIOS update as a standalone executable from the manufacturer's site and run it from within Windows. That bypasses the capsule mechanism entirely. On Lenovo, use the Lenovo Vantage app's firmware update. On Dell, use Dell Command Update.

Quick-Reference Summary

Start with the cache clear — it fixes 80% of 0X80290302 cases I've seen. If you're on a corporate laptop, check with IT first because they may have intentionally locked BIOS updates. Skip the registry hacks you'll find elsewhere — they don't apply here. The error is firmware-level, not Windows-level.