Debugging UEFI Capsule updates

Latest version

If you're running into problems with fwupdate not doing UEFI capsule updates, please first try master in case it's already been fixed.

If you are running with secure boot enabled, please disable secure boot while trying master (you won't have signed binaries).

Not enabled in BIOS

Check that capsule updates are enabled in the BIOS settings. On Dell systemts, they are called "UEFI capsule firmware updates" and on Lenovo "Windows UEFI firmware update". Other vendors might use different names.

Not booting into fwup.efi

First check and make sure that the boot entry is getting created.
You can check this from efibootmgr -v output. The expected behavior is:

There is one entry for Linux-Firmware-Updater \fwupx64.efi If multiple entries exist, delete duplicates.
BootNext has been set to point to the entry that corresponds to Linux-Firmware-Updater \fwupx64.efi
BootOrder contains the entry that corresponds to Linux-Firmware-Updater \fwupx64.efi at the end of the list.

If the boot order looks correct, make sure that all the files referenced exist at the paths indicated (both shimx64.efi and fwupx64.efi)

Booting into fwupx64.efi but nothing happens

Are you applying multiple capsules simultaneously? This could mean doing a TPM update and BIOS update at the same time, or an FMP update and BIOS update at the same time.

I am doing multiple updates and it fails

Re-run the cleanup systemd unit.

You'll need to remove a state file (in /var/lib/fwupdate/done or somewhere similar - distro dependent)
This removes the payloads from EFI system partition, Boot entries and all NVRAM variables.

Re-run just one update at a time. If this fixes your problem, please report an issue with the relevant details.

Only doing one update and it fails

Enable the fwup.efi debugging facility.

Running fwupdate >= 11 (or from git)

Run this command as root:

fwupdate -d

Running fwupdate <= 10