Skip to content

fwupd

Introduction

fwupd is an open-source project, that is widely used to make firmware updates almost as seamless and simple as updating system packages. Most hardware vendors and Linux distributions support it.

The fwupd daemon relies on the Linux Vendor Firmware Service (LVFS) for distributing and managing the firmware binaries to the users.

Note

The use of fwupd for firmware updates depends on Capsule Updates support. Check that your device and its firmware are listed in the "Supported devices" section there.

Firmware Update Prerequisites

Intel ME

This only applies to devices with the Intel Management Engine that are not fused using the Dasharo Trust Root technology and don't yet use Capsules V2.

Intel Management Engine needs to be disabled manually to successfully perform an fwupd update. Failing to do so won't do any harm to the system, but the update will be rejected.

Intel ME needs to be switched to the Disabled (HAP) state in the Setup Menu to perform the update. This step cannot be done automatically by fwupd. Afterwards, Intel ME needs to be manually turned back on if desired.

Check Intel Management Engine Options documentation for details on how to set ME mode to Disabled (HAP). See this Intel ME/CSME FAQ page for information about disabling the ME, or Issue #1302 for more context.

Charger connected

On battery-powered devices (laptops), the AC charger must be connected before running fwupdmgr to start the update. It must be connected for the whole duration of the update, until the device boots back up normally.

Usage

Desktop Environments

The most popular Desktop Environments, like Gnome and KDE, automatically look for firmware updates on LVFS and suggest performing them with a simple button press.

Firmware update available in Gnome Software
Firmware update available in Gnome Software

Before starting the update, check whether the prerequisites are met.

CLI

For more advanced users or in a more lightweight DEs/WMs fwupdmgr command can be used in the terminal.

Installation

Most Operating Systems come with fwupd preinstalled and use it to perform firmware updates.

Dasharo Capsule Updates using fwupdmgr are not currently supported on Windows. If that is the only Operating System you wish to use, other update methods need to be considered.

Check if fwupdmgr is installed. Executing the command should print the versions of all fwupdmgr components:

$ fwupdmgr --version

Example output 
$ fwupdmgr --version
compile   org.freedesktop.fwupd         1.9.31
compile   com.hughsie.libxmlb           0.3.18
compile   com.hughsie.libjcat           0.2.0
runtime   org.freedesktop.fwupd-efi     1.4
compile   org.freedesktop.gusb          0.4.8
runtime   com.hughsie.libxmlb           0.3.x
runtime   com.hughsie.libjcat           0.2.0
runtime   org.freedesktop.gusb          0.4.8
runtime   org.freedesktop.fwupd         1.9.31
runtime   org.kernel                    6.17.0-14-generic

If not, install it using:

$ sudo apt update
$ sudo apt install fwupdmgr

Check if fwupdmgr is installed. Executing the command should print the versions of all fwupdmgr components:

$ fwupdmgr --version

Example output 
$ fwupdmgr --version
compile   org.freedesktop.fwupd         1.9.31
compile   com.hughsie.libxmlb           0.3.18
compile   com.hughsie.libjcat           0.2.0
runtime   org.freedesktop.fwupd-efi     1.4
compile   org.freedesktop.gusb          0.4.8
runtime   com.hughsie.libxmlb           0.3.x
runtime   com.hughsie.libjcat           0.2.0
runtime   org.freedesktop.gusb          0.4.8
runtime   org.freedesktop.fwupd         1.9.31
runtime   org.kernel                    6.17.0-14-generic

If not, install it using:

$ sudo dnf install fwupdmgr

To use fwupdmgr on QubesOS, the program needs to be run on the dom0 qube, and it requires an internet connection. For that reason, a fwupdmgr wrapper for QubesOS exists, that sets up the network tunnels for the firmware update downloads to be possible from dom0. The qubes-fwupdmgr package should be installed out of the box. Executing the command should print the help screen:

$ sudo qubes-fwupdmgr

Example output 
$ sudo qubes-fwupdmgr
======================================================================
Usage:
======================================================================
    Command:            qubes-fwupdmgr [OPTION…][FLAG..]
    Example:            qubes-fwupdmgr refresh --whonix --url=<url>

Options:
======================================================================
    get-devices:            Get all devices that support firmware updates
    get-updates:            Get the list of updates for connected hardware
    refresh:            Refresh metadata from remote server
    update:             Update chosen device to latest firmware version
    update-heads:           Updates heads firmware to the latest version (EXPERIMENTAL, not fully supported yet)
    downgrade:          Downgrade chosen device to chosen firmware version
    clean:              Delete all cached update files

Flags:
======================================================================
    --whonix:           Download firmware updates via Tor
    --device:           Specify device for heads update (default - x230)
    --url:              Address of the custom metadata remote server

Help:
======================================================================
    -h --help:          Show help options

Warning

fwupd on FreeBSD is very much work in progress as of March 2026. The basic elements are there, but user experience may be far from perfect. In particular, not all functionality is available (e.g., fwupd won't reboot for you, update may be reported as "in progress" after it has been applied) or works reliably (may complain about missing ESP, although this error may be gone on second try or after restarting fwupd). In addition to that, FreeBSD loader and/or kernel has issues with ESRT which may prevent uefi_capsule plugin of fwupd from working.

fwupd is available in ports, but the version there lacks UEFI capsules. The necessary changes are being upstreamed, until then a relatively complicated setup in necessary to have a chance of firmware updates working. The following instructions assume the system isn't configured much, make adjustments to not overwrite existing configuration if that's not the case.

Start by switching from "quaterly" to "latest" packages to have an already updated bsdisks (necessary to find ESP):

# mkdir -p /usr/local/etc/pkg/repos
# sed 's!/quarterly!/latest!' /etc/pkg/FreeBSD.conf > /usr/local/etc/pkg/repos/FreeBSD.conf

Then install fwupd, bsdisks and various build dependencies. A few ports will be reinstalled later, this step is just to reuse binary packages and not build everything from sources. Run the following command:

# pkg install fwupd bsdisks meson help2man noto-sans py311-Jinja2 py311-pygobject py311-pangocffi gettext-tools pkgconf vala dbus cmake ninja git

Now get the version of ports with necessary fixes and reinstall the packages (cloning will take time, building can too; there will also be a few dialogs about port options, just agreeing should do but can choose to not build documentation):

# git clone --branch=fwupd-2026 --depth=1 --filter=blob:none https://github.com/3mdeb/freebsd-ports /usr/ports
# make -C /usr/ports/devel/efivar/ deinstall
# make -C /usr/ports/devel/gnu-efi/ reinstall
# make -C /usr/ports/sysutils/fwupd-efi/ reinstall
# make -C /usr/ports/sysutils/fwupd/ reinstall

fwupd communicates with bsdisks over D-Bus, so it must be running (fwupdmgr also depends on D-Bus, otherwise using fwupdtool as root is the only option). It can be enabled permanently and then launched like this:

# echo 'dbus_enable="YES"' >> /etc/rc.conf
# service dbus start

This is how to start D-Bus temporarily:

# service dbus onestart

Checking the current firmware version

To check the currently used firmware version, run the following command

$ fwupdmgr get-devices

Look for System Firmware or UEFI Device Firmware in the output.

Example of a firmware version entry: 
├─UEFI Device Firmware:
│     Device ID:          204ce525ed4dbc468e789eb029f3627dd13d6cf4
│     Summary:            UEFI System Resource Table device (updated via NVRAM)
│     Current version:    1.0.1
│     Minimum Version:    1.0.1
│     Vendor:             NovaCustom (DMI:3mdeb)
│     GUID:               f4deb4f3-f673-48fe-a481-627357b00b6a
│     Device Flags:       • Internal device
│                         • System requires external power source
│                         • Supported on remote server
│                         • Needs a reboot after installation
│                         • Device is usable for the duration of the update
│                         • Updatable
│     Device Requests:    • Message

To check the currently used firmware version, run the following command

$ sudo qubes-fwupdmgr get-devices

Look for System Firmware or UEFI Device Firmware in the output.

Example of get-devices output 
======================================================================
System Firmware
======================================================================
    DeviceId:           204ce525ed4dbc468e789eb029f3627dd13d6cf4
    Guid:               ·f4deb4f3-f673-48fe-a481-627357b00b6a
    Summary:            UEFI System Resource Table device (updated via NVRAM)
    Plugin:             uefi_capsule
    Protocols:          ·org.uefi.capsule
    Flags:              ·internal
                        ·updatable
                        ·require-ac
                        ·needs-reboot
                        ·can-verify
                        ·usable-during-update
    RequestFlags:       ·allow-generic-message
    Checksums:          ·914872cd28744aacad621b8a95e02171b7854b79cf61c59eec939868a33de07d
    Vendor:             Notebook
    VendorIds:          ·DMI:3mdeb
    Version:            16777344
    VersionRaw:         16777344
    Created:            1771420572
    UpdateState         2
As of QubesOS R4.2.3, the firmware version is not interpreted correctly by fwupdmgr. As a fallback on Dasharo firmware, use dmidecode to verify the firmware version. Run: 
$ sudo dmidecode -t bios | grep Version:
Example output: 
Version: Dasharo (coreboot+UEFI) v1.0.0

Checking for updates

To check for available updates for your device, run the following commands

$ fwupdmgr refresh
$ fwupdmgr get-updates

Example of a possible update from v1.0.0 to v1.0.1: 
$ fwupdmgr get-updates
Devices with no available firmware updates:
• UEFI dbx
• SSDPR-PX600-250-80
Notebook V54x_6x_TU
│
└─System Firmware:
│   Device ID:          204ce525ed4dbc468e789eb029f3627dd13d6cf4
│   Summary:            UEFI System Resource Table device (updated via NVRAM)
│   Current version:    1.0.0
│   Minimum Version:    1.0.0
│   Vendor:             NovaCustom (DMI:3mdeb)
│   Update State:       Success
│   GUID:               f4deb4f3-f673-48fe-a481-627357b00b6a
│   Device Flags:       • Internal device
│                       • Updatable
│                       • System requires external power source
│                       • Supported on remote server
│                       • Needs a reboot after installation
│                       • Cryptographic hash verification is available
│                       • Device is usable for the duration of the update
│   Device Requests:    • Message
│
└─V54x_6x_TU System Update:
        New version:      1.0.1
        Remote ID:        lvfs
        Release ID:       135872
        Summary:          V54x_6x_TU V540TU system firmware
        License:          Proprietary
        Size:             34.0 MB
        Created:          2026-01-29
        Urgency:          High
        Tested by NovaCustom:
        Tested:         2026-01-29
        Distribution:   ubuntu 24.04
        Old version:    1.0.1
        Version[fwupd]: 1.9.31
        Vendor:           NovaCustom
        Release Flags:    • Trusted metadata
                        • Is upgrade
                        • Tested by trusted vendor
        Description:
        New Dasharo firmware release for the NovaCustom Meteor Lake laptops

        with integrated graphics, featuring numerous bug fixes, performance

        improvements and stability fixes.
        Checksum:         178be21614286811e95484118e06b4b39c91fe401b234639d4aa73cd7d6f63d6

To check for available updates for your device, run the following commands

$ qubes-fwupdmgr refresh
$ qubes-fwupdmgr get-updates

Warning

As of QubesOS R4.3 on 02-2026, qubes-fwupdmgr might not work correctly and the updates on LVFS may not be found using this tool. Refer to troubleshooting.

Updating the firmware

Preparation / Prerequisites

Before starting the update, check whether the prerequisites are met.

Update instructions

To update your firmware, run the following commands:

$ fwupdmgr refresh
$ sudo fwupdmgr update

Example of an update process: 
$ fwupdmgr update
Devices with no available firmware updates:
• UEFI dbx
• SSDPR-PX600-250-80
╔══════════════════════════════════════════════════════════════════════════════╗
║ Upgrade System Firmware from 1.0.0 to 1.0.1?                                 ║
╠══════════════════════════════════════════════════════════════════════════════╣
║ New Dasharo firmware release for the NovaCustom Meteor Lake laptops          ║
║                                                                              ║
║ with integrated graphics, featuring numerous bug fixes, performance          ║
║                                                                              ║
║ improvements and stability fixes.                                            ║
║                                                                              ║
║ V54x_6x_TU must remain plugged into a power source for the duration of the   ║
║ update to avoid damage.                                                      ║
╚══════════════════════════════════════════════════════════════════════════════╝
Perform operation? [Y|n]: y
Authenticating…          [***************************************]
==== AUTHENTICATING FOR org.freedesktop.fwupd.update-internal-trusted ====
Authentication is required to update the firmware on this machine
Authenticating as: ubuntu
Password:
==== AUTHENTICATION COMPLETE ====
Waiting…                 [***************************************]
Successfully installed firmware
Do not turn off your computer or remove the AC adapter while the update is in progress.
An update requires a reboot to complete. Restart now? [y|N]: y
==== AUTHENTICATING FOR org.freedesktop.login1.reboot ====
Authentication is required to reboot the system.
Authenticating as: ubuntu
Password:
==== AUTHENTICATION COMPLETE ====

To update your firmware, run the following commands:

$ sudo qubes-fwupdmgr refresh
$ sudo qubes-fwupdmgr update

Warning

As of QubesOS R4.3 on 02-2026, qubes-fwupdmgr might not work correctly and the updates on LVFS may not be found using this tool. Refer to troubleshooting.

To update your firmware, run the following commands:

# fwupdmgr refresh
# fwupdmgr update --no-reboot-check
# reboot

Example of an update process: 
# fwupdmgr update --no-reboot-check
Devices with no available firmware updates:
• UEFI dbx
• SSDPR-PX600-250-80
╔══════════════════════════════════════════════════════════════════════════════╗
║ Upgrade System Firmware from 1.0.0 to 1.0.1?                                 ║
╠══════════════════════════════════════════════════════════════════════════════╣
║ New Dasharo firmware release for the NovaCustom Meteor Lake laptops          ║
║                                                                              ║
║ with integrated graphics, featuring numerous bug fixes, performance          ║
║                                                                              ║
║ improvements and stability fixes.                                            ║
║                                                                              ║
║ V54x_6x_TU must remain plugged into a power source for the duration of the   ║
║ update to avoid damage.                                                      ║
╚══════════════════════════════════════════════════════════════════════════════╝
Perform operation? [Y|n]: y
Waiting…                 [***************************************]
Successfully installed firmware
Do not turn off your computer or remove the AC adapter while the update is in progress.

Warning

After the command finishes, a reboot is necessary to apply the update. The fwupd UEFI application that performs the update will be booted automatically after a reboot, unless there is a user interaction. Entering the Setup Menu, Boot Manager, or interfering in any other way will abort the update. Allow the device to reboot freely, and do not press any buttons until the update finishes unless there is a dialog related to the update.

Devices that have an Embedded Controller might stay powered off after the update and need to be powered on.

Local Update

If using LVFS is undesirable or not possible, a fwupd firmware update can be performed using a locally available cabinet (.cab) file downloaded from any source. We will use novacustom_v54x_mtl_igpu_v1.0.1_btg_prod.cab downloaded from dl.3mdeb.com as an example.

To update your firmware using a locally available cabinet file, follow the steps:

  1. Allow updates from untrusted sources 
    $ printf '[fwupd]\nOnlyTrusted=false\n' | sudo tee /etc/fwupd/fwupd.conf
  2. Perform a local install 
    $ sudo fwupdmgr local-install novacustom_v54x_mtl_igpu_v1.0.1_btg_prod.cab

To update your firmware using a locally available cabinet file, follow the steps:

  1. Allow updates from untrusted sources 
    # printf '[fwupd]\nOnlyTrusted=false\n' > /usr/local/etc/fwupd/fwupd.conf
  2. Perform a local install 
    # fwupdmgr local-install --no-reboot-check novacustom_v54x_mtl_igpu_v1.0.1_btg_prod.cab
  3. Reboot to apply the update 
    # reboot

Update troubleshooting

No output from fwupdmgr update

Depending on the version of fwupdmgr, issues like the AC being disconnected on battery-powered devices might not be printed explicitly right away after trying to perform an update. In such a case, try running the get-devices command and look for the Problems header and red text under device entries.

Example, update rejected, AC was not connected. 
├─System Firmware:
│ │   Device ID:          204ce525ed4dbc468e789eb029f3627dd13d6cf4
│ │   Summary:            UEFI System Resource Table device (updated via NVRAM)
│ │   Current version:    1.0.0
│ │   Minimum Version:    1.0.0
│ │   Vendor:             NovaCustom (DMI:3mdeb)
│ │   Update State:       Success
│ │   Problems:           • Device requires AC power to be connected
│ │   GUID:               f4deb4f3-f673-48fe-a481-627357b00b6a
│ │   Device Flags:       • Internal device
│ │                       • System requires external power source
│ │                       • Supported on remote server
│ │                       • Needs a reboot after installation
│ │                       • Cryptographic hash verification is available
│ │                       • Device is usable for the duration of the update
│ │                       • Updatable
│ │   Device Requests:    • Message
Note that `Update State` is `Success` despite a failure, as it reports the status of the last correctly initiated Update. Without an AC connected, the update did not even start keeping the previous value of `Update State`.

To verify if the problem really occurs, you can run the command in verbose mode:

$ sudo fwupdmgr update -v

The output might suggest what the issue is, for example:

Example of fwupdmgr update -v 
$ sudo fwupdmgr update -v
(pkttyagent:4378): GLib-GIO-DEBUG: 11:44:32.011: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)
(fwupdmgr:4376): GLib-GIO-DEBUG: 11:44:32.019: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’
(fwupdmgr:4376): dconf-DEBUG: 11:44:32.019: watch_fast: "/system/proxy/" (establishing: 0, active: 0)
(fwupdmgr:4376): dconf-DEBUG: 11:44:32.020: watch_fast: "/system/proxy/http/" (establishing: 0, active: 0)
(fwupdmgr:4376): dconf-DEBUG: 11:44:32.020: watch_fast: "/system/proxy/https/" (establishing: 0, active: 0)
(fwupdmgr:4376): dconf-DEBUG: 11:44:32.020: watch_fast: "/system/proxy/ftp/" (establishing: 0, active: 0)
(fwupdmgr:4376): dconf-DEBUG: 11:44:32.020: watch_fast: "/system/proxy/socks/" (establishing: 0, active: 0)
(fwupdmgr:4376): dconf-DEBUG: 11:44:32.020: unwatch_fast: "/system/proxy/" (active: 0, establishing: 1)
(fwupdmgr:4376): dconf-DEBUG: 11:44:32.020: unwatch_fast: "/system/proxy/http/" (active: 0, establishing: 1)
(fwupdmgr:4376): dconf-DEBUG: 11:44:32.020: unwatch_fast: "/system/proxy/https/" (active: 0, establishing: 1)
(fwupdmgr:4376): dconf-DEBUG: 11:44:32.020: unwatch_fast: "/system/proxy/ftp/" (active: 0, establishing: 1)
(fwupdmgr:4376): dconf-DEBUG: 11:44:32.020: unwatch_fast: "/system/proxy/socks/" (active: 0, establishing: 1)
(fwupdmgr:4376): dconf-DEBUG: 11:44:32.021: watch_established: "/system/proxy/" (establishing: 0)
(fwupdmgr:4376): dconf-DEBUG: 11:44:32.021: watch_established: "/system/proxy/http/" (establishing: 0)
(fwupdmgr:4376): dconf-DEBUG: 11:44:32.021: watch_established: "/system/proxy/https/" (establishing: 0)
(fwupdmgr:4376): dconf-DEBUG: 11:44:32.021: watch_established: "/system/proxy/ftp/" (establishing: 0)
(fwupdmgr:4376): dconf-DEBUG: 11:44:32.021: watch_established: "/system/proxy/socks/" (establishing: 0)
(fwupdmgr:4376): GLib-GIO-DEBUG: 11:44:32.021: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ‘gio-vfs’
(fwupdmgr:4376): pxbackend-DEBUG: 11:44:32.021: px_config_sysconfig_set_config_file: Could not read file /etc/sysconfig/proxy
(fwupdmgr:4376): pxbackend-DEBUG: 11:44:32.021: Active config plugins:
(fwupdmgr:4376): pxbackend-DEBUG: 11:44:32.021:  - config-env
(fwupdmgr:4376): pxbackend-DEBUG: 11:44:32.021:  - config-kde
(fwupdmgr:4376): pxbackend-DEBUG: 11:44:32.021:  - config-gnome
(fwupdmgr:4376): pxbackend-DEBUG: 11:44:32.021:  - config-sysconfig
(fwupdmgr:4376): GLib-GIO-DEBUG: 11:44:32.023: Failed to initialize portal (GNetworkMonitorPortal) for gio-network-monitor: Not using portals
(fwupdmgr:4376): GLib-GIO-DEBUG: 11:44:32.024: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)
(fwupdmgr:4376): GLib-GIO-DEBUG: 11:44:32.026: _g_io_module_get_default: Found default implementation networkmanager (GNetworkMonitorNM) for ‘gio-network-monitor’
(fwupdmgr:4376): pxbackend-DEBUG: 11:44:32.026: px_manager_constructed: Up and running
(fwupdmgr:4376): GLib-GIO-DEBUG: 11:44:32.026: _g_io_module_get_default: Found default implementation libproxy (GLibproxyResolver) for ‘gio-proxy-resolver’
(fwupdmgr:4376): Fwupd-DEBUG: 11:44:32.028: Emitting ::status-changed() [idle]
Devices with no available firmware updates:
• SSDPR-PX600-250-80
• UEFI dbx
(fwupdmgr:4376): FuMain-DEBUG: 11:44:32.043: ignoring 204ce525ed4dbc468e789eb029f3627dd13d6cf4: System Firmware is not currently updatable: Device requires AC power to be connected

At the end of the verbose output, we can see the line

(fwupdmgr:4376): FuMain-DEBUG: 11:44:32.043: ignoring 204ce525ed4dbc468e789eb029f3627dd13d6cf4: System Firmware is not currently updatable: Device requires AC power to be connected

Which tells us that the update was rejected, because there's no AC adapter connected.

If you see any errors during the update, check the Troubleshooting section of the Capsule Update guide.

fwupdmgr asks for AC despite it being connected

The check for an AC charger being connected in Linux fails when the firmware configures a charging threshold for the battery that disconnects the charger once the battery reaches the threshold. If the battery is considered full and not charging at the moment, the check in fwupdmgr will think the charger is disconnected.

There are two options to work around this issue:

  • Deplete battery charge a couple of percent, so that it doesn't stop charging for the duration of fwupdmgr running the checks.
  • Disable battery charging thresholds in the firmware.
No updates available (QubesOS)

As of QubesOS R4.3 on 02-2026 qubes-fwupdmgr does not work correctly and the updates on LVFS might not be found using this tool. In such a case, there are still a few options to perform the update. Either use a different update method according to the Firmware Update page for your device in the Supported hardware tab, or perform a Local Update using a fwupd cabinet (.cab) file downloaded manually from fwupd.org.

Verifying the firmware update result

To check the result of your firmware update, run the following command:

$ fwupdmgr get-results

You will be prompted to select a device. For Dasharo firmware updates, select System Firmware or UEFI Device Firmware.

Example of fwupdmgr get-results output after a successful update 
$ fwupdmgr get-results
0.  Cancel
1.  597c1adb5fa5096f1949ae7535b85dc6ddd34f80 ((null))
2.  4bde70ba4e39b28f9eab1628f9dd6e6244c03027 (Core™ Ultra 7 155H)
3.  aec1a869eb0df71b7cea6b3ac71d39b830faf164 (MNE007QS1-4)
4.  5792b48846ce271fab11c4a545f7a3df0d36e00a (Meteor Lake-P [Intel Graphics])
5.  71b677ca0f1bc2c5b804fa1d59e52064ce589293 (SSDPR-PX600-250-80)
6.  204ce525ed4dbc468e789eb029f3627dd13d6cf4 (System Firmware)
7.  c6a80ac3a22083423992a3cb15018989f37834d6 (TPM)
8.  6924110cde4fa051bfdc600a60620dc7aa9d3c6a (UEFI Platform Key)
9.  362301da643102b9f38477387e2193e57abaa590 (UEFI dbx)
Choose device [0-9]: 6
System Firmware:
Device ID:            204ce525ed4dbc468e789eb029f3627dd13d6cf4
Previous version:     1.0.0
Update State:         Success
Last modified:        2026-02-18 14:01
GUID:                 f4deb4f3-f673-48fe-a481-627357b00b6a
Device Flags:         • Internal device
                        • Updatable
                        • System requires external power source
                        • Supported on remote server
                        • Needs a reboot after installation
                        • Cryptographic hash verification is available
                        • Device is usable for the duration of the update

This output means the firmware version has changed to the expected one.

qubes-fwupdmgr doesn't currently support get-results command of fwupdmgr.

The following command is supposed to report update results:

$ fwupdmgr get-results

However, this is likely to not produce any results because fwupd fails to finalize the update. fwupdmgr get-devices incorrectly states that "An update is in progress" along with displaying version that shows the update has already happened.

For another way to verify an update has really happened refer to Checking The Current Firmware Version.

Update result troubleshooting

Failed to run update on reboot: expected ... and got

This Update Error is most often caused by failing to set the Intel ME to Disabled (HAP) mode before running the update.

Example of fwupdmgr get-results output when that happens 
$ fwupdmgr get-results
0. Cancel
1. 597c1adb5fa5096f1949ae7535b85dc6ddd34f80 ((null))
2. 4bde70ba4e39b28f9eab1628f9dd6e6244c03027 (Core™ Ultra 7 155H)
3. aec1a869eb0df71b7cea6b3ac71d39b830faf164 (MNE007QS1-4)
4. 5792b48846ce271fab11c4a545f7a3df0d36e00a (Meteor Lake-P [Intel Graphics])
5. 71b677ca0f1bc2c5b804fa1d59e52064ce589293 (SSDPR-PX600-250-80)
6. 204ce525ed4dbc468e789eb029f3627dd13d6cf4 (System Firmware)
7. c6a80ac3a22083423992a3cb15018989f37834d6 (TPM)
8. 6924110cde4fa051bfdc600a60620dc7aa9d3c6a (UEFI Platform Key)
9. 362301da643102b9f38477387e2193e57abaa590 (UEFI dbx)
Choose device [0-9]: 6
System Firmware:
Device ID:            204ce525ed4dbc468e789eb029f3627dd13d6cf4
Previous version:     1.0.0
Update State:         Failed
Update Error:         failed to run update on reboot: expected 1.0.1 and got 1.0.0
Last modified:        2026-02-18 13:45
GUID:                 f4deb4f3-f673-48fe-a481-627357b00b6a
Device Flags:         • Internal device
                        • Updatable
                        • System requires external power source
                        • Supported on remote server
                        • Needs a reboot after installation
                        • Cryptographic hash verification is available
                        • Device is usable for the duration of the update

When that happens after rebooting, instead of an update progress bar, a message like this will appear on top of the screen:

[FIRMWARE WARNING] Capsule Updates are only supported while Intel ME is in HAP mode!

Make sure the Intel ME mode in the Setup Menu is Disabled (HAP). Refer to the prerequisites section and try again.

References