BIOS and firmware updates by vendor: Dell, HP and ASUS

Verified 2026-10-293 min read

Three vendor toolchains, the order of operations that avoids a bricked board, and how to verify the version actually changed after the reboot.

Tested onPro (26H2) / Server · Build 26300.9457 / 26100.33650 · x64

Build: 26300.9457 / 26100.33650
Edition: Pro (26H2) / Server
Architecture: x64
Support: Documentation (E1)
Evidence: E1Official documentation
Verified: 2026-10-29
Page type: Task

The short answer

Firmware updates fix real problems (memory training, USB/TB stability, security advisories) and carry one real risk: the machine must not lose power mid-flash.

The safe pattern is the same for all three vendors:

Record the current version (so you can prove it changed).
Suspend BitLocker if the drive is encrypted.
AC power, no battery-only, close every other app.
Flash with the vendor tool.
Verify the version after the reboot; confirm BitLocker protection came back.

Vendor toolchains differ. Dell and HP ship a Windows agent that also handles drivers; ASUS expects you to flash from the UEFI itself or with its own utility.

Before you start

# current firmware and board identity
Get-CimInstance Win32_BIOS | Select-Object Manufacturer,SMBIOSBIOSVersion,ReleaseDate,Version
Get-CimInstance Win32_BaseBoard | Select-Object Manufacturer,Product,Version
Get-CimInstance Win32_ComputerSystem | Select-Object Manufacturer,Model,SystemFamily
# is BitLocker on?  (Pro/Enterprise; Home lacks manage-bde)
manage-bde -status C:

Write the SMBIOSBIOSVersion down. After the update it should change — that is your only reliable proof, because the vendor UI will happily say “up to date” while reporting the old version.

Suspend-BitLocker -MountPoint C: -RebootCount 2

Dell — Command Update

Dell’s tool is a single agent that inventories the machine, then offers BIOS, driver and firmware packages together.

Step	Action
1	Install Dell Command \| Update from Dell’s support site for your service tag
2	Run a Check — it lists BIOS plus driver updates with criticality
3	Install BIOS first if both BIOS and chipset appear, then reboot
4	Re-run Check to catch anything that depended on the new BIOS

Notes that matter:

Dell may block downgrades after a certain version; check the release notes before updating a stable machine.
Command Update can be scheduled, which is convenient and also how a fleet reboots itself at 3am. If you schedule it, control the maintenance window.
The service tag is the identity — driver pages keyed to the model alone can offer the wrong package.

HP — Image Assistant / SoftPaqs

HP splits the job: HP Image Assistant analyses the machine and produces a SoftPaq list; individual SoftPaqs are the packages. BIOS is delivered as a SoftPaq that runs a flash utility.

Step	Action
1	Install HP Image Assistant (or use HP Support Assistant for single machines)
2	Analyze — it reports recommended vs critical updates
3	Install the System BIOS SoftPaq, allow the reboot
4	Re-analyze; ME/EC firmware often follows the BIOS

Notes:

HP’s flash utility asks for confirmation and may require the BIOS administrator password if one is set.
Some business models expose “BIOS rollback” in the UEFI; consumer models often do not.
HP Sure Start (business) can self-heal a corrupted BIOS — a genuine safety net, not a licence to flash carelessly.

ASUS — EZ Flash / USB BIOS FlashBack

ASUS expects the firmware file, not an agent:

Method	When
EZ Flash 3 in UEFI	normal path: copy the `.CAP` to a FAT32 USB stick
USB BIOS FlashBack	the board will not POST — flashes without CPU/RAM on supported boards
Armoury Crate / MyASUS	convenience path on laptops and some boards

Procedure:

Download the BIOS for the exact board model (not the series) from ASUS support.
Extract the .CAP; many boards require renaming via the bundled renamer.
Format a USB stick FAT32, copy the file to the root.
Enter UEFI (Del at POST) → Tool → ASUS EZ Flash → select the file.
Do not power off during the flash; the board reboots itself, sometimes twice.

Notes:

Do not cross-flash a different model’s BIOS, even from the same series.
A BIOS update on AM5/LGA1700 platforms can reset XMP/EXPO, fan curves and boot order — re-check them afterwards.
FlashBack needs the file in the specifically named USB port, usually marked on the rear I/O.

After the flash: verify

Get-CimInstance Win32_BIOS | Select-Object SMBIOSBIOSVersion,ReleaseDate
Confirm-SecureBootUEFI
Get-BitLockerVolume | Select-Object MountPoint,ProtectionStatus,KeyProtector

Checklist:

Version string changed
Secure Boot still True
BitLocker back to Protection On (not Suspended)
XMP/EXPO and fan curves re-applied
Boot order unchanged
TPM still owned and ready (Get-Tpm)

If BitLocker is still suspended, Resume-BitLocker -MountPoint C:.

Lab boundary

E1. The vendor toolchains are documented by Dell, HP and ASUS; the version-check commands are Microsoft-documented. This lab is a Proxmox host with no physical Dell/HP/ASUS machine, so no flash was performed.