How to update firmware on PCs, SSDs, docks and network gear
The five-step method for any firmware update, the path for SSDs, docks, network cards and firewalls, dock firmware best practices, Linux with fwupd, and a ring rollout that keeps BitLocker and bad releases in check.
Updated: November 2026
To update firmware, check the device's current version, download the newer one from the manufacturer or its update tool, keep the power on while it installs, then confirm the new version took. The BIOS gets the attention, but the SSD, the dock, the network card and the firewall in the network closet all run firmware too, and each one updates a different way. Here's the general method, the path for each device type, and the rules that keep an update from turning into a site visit.
Firmware lives in more than the BIOS
Firmware is the small program baked into a piece of hardware that tells it how to behave. The motherboard has it, and so does nearly everything plugged into it: storage drives, network adapters, Thunderbolt and USB-C docks, keyboards, printers, and every switch, access point and firewall on the network.
Vendors ship firmware updates for the same reasons they ship software updates. They fix bugs, patch security holes, and add support for new hardware. The difference is where the code runs. Firmware loads before Windows does, or runs inside a device Windows barely sees, so your endpoint agent often can't tell you what version is installed.
The motherboard layer has its own guide. If that's the one you're after, our BIOS update guide covers what changes, how to check the version and how to run a BIOS policy. The steps below apply to it too, and the rest of this post covers everything else.
How to update firmware in five steps
Every firmware update, from a laptop BIOS to a core switch, follows the same shape. The tool changes by device. The order doesn't.
- Find the current version. On Windows,
msinfo32shows the BIOS version on its summary page, andGet-PhysicalDisk | Select FriendlyName, FirmwareVersionin PowerShell lists drive firmware. Network gear shows it on the admin page or in the vendor's console, and Linux lists it withfwupdmgr get-devices. - Get the update from the manufacturer only. Use the vendor's support page or update tool, match the exact model and hardware revision, and read the release notes for what it fixes and what it requires first.
- Back up what you can't rebuild. Export the config on routers, switches and firewalls, and back up the data on any drive you're about to update.
- Keep the power steady. Laptops on AC, network gear on a UPS, and nobody unplugging anything until it finishes. An interrupted flash is the classic way to brick a device.
- Install, restart, verify. Let it reboot as many times as it wants, then check the version again. A device that still reports the old version didn't update, whatever the installer said.
On a Mac there's no separate step: Apple ships Mac firmware inside macOS updates. Printers and home routers usually update from their own web admin page, often with an automatic update option worth switching on.
How to update firmware on Windows PCs
On a single Windows machine there are two routes, and they overlap.
The first is Windows Update. Hardware vendors can package firmware as a special kind of driver, and Windows installs it through the same pipeline as everything else. Microsoft's own documentation for device makers puts the mechanism plainly: "Because WU can't execute software, the firmware update driver must hand the firmware to Plug and Play (PnP) for installation." In practice, firmware delivered this way shows up in Device Manager under a Firmware category, and in the update history like any driver.
The second is the vendor's own tool. Dell Command Update, HP Image Assistant and Lenovo System Update each know the exact model they're running on and pull firmware for the system, the dock and the storage in one pass. They usually carry updates before Windows Update does, and some firmware never reaches Windows Update at all.
For a fleet, the vendor tools are scriptable. Dell Command Update, for example, lets you choose which categories to install, block specific updates and throttle how they apply. This short walkthrough covers the blocklist and throttling options that matter when you're pushing to hundreds of machines.
Drivers and firmware often ship together in the same tool run. Our guide on updating drivers covers the driver half, including rollback when an update breaks something.
SSDs, docks and NICs need their own path
Storage firmware is where a missed update costs data, not just stability. The best-known case is Samsung's 990 Pro. In early 2023 Samsung released firmware 1B2QJXD7 to stop drives reporting an abnormally fast drop in health. As Puget Systems noted in March 2023, the update halted the decline but didn't reverse it, quoting Samsung that "the S.M.A.R.T. values will not be restored to factory settings after the firmware update." Drives that waited longer for the fix kept the damage.
That's the pattern for storage: the fix only protects you from the day it's applied. SSD vendors publish their own update utilities, and the business-line vendor tools above often include the drive firmware for the models they ship. Retail drives bought separately are the ones that slip through.
Dock firmware update best practices
Docks are the other repeat offender. A dock sits between the laptop and everything else on the desk, so a dock firmware bug looks like a network, display or USB problem. Update the dock with its own vendor utility, and keep the laptop connected to power while it runs. Pulling a dock mid-update is one of the few ways to brick it. On a fleet, update one dock per model first, then the rest, and use the laptop vendor's tool where it covers the dock, as Dell Command Update does for Dell docks. Some docks also update in stages and drop the connection partway through, which looks like a failure and usually isn't, so wait for the tool to report done before touching anything.
Network adapters usually get firmware through the same vendor tools, or bundled into driver packages. The NIC is worth checking first when a machine drops off the network after sleep, or when a dock's Ethernet port misbehaves on one model and not another.
Network gear is where firmware bites
Switches, access points and firewalls run firmware too, and they update through the vendor's own console or management platform, not Windows. They're also the devices attackers go after, because they sit on the edge of the network and rarely run an endpoint agent.
The clearest recent example is Cisco's firewall line. On September 25, 2025, CISA issued Emergency Directive 25-03 for Cisco ASA and Firepower devices after attackers used two zero-day exploits against them. The directive noted that the attacker had "manipulated read-only memory (ROM) to persist through reboot and system upgrade." In other words, updating a compromised box didn't necessarily evict the attacker. CISA's April 2026 update added a hard power-off requirement for affected Firepower and Secure Firewall devices.
Keeping track of which box runs which version is the unglamorous half of the job. In this r/msp thread, an engineer running mostly FortiGate with some Cisco describes checking vendor security advisories against a spreadsheet every month, and missing one by three weeks. The replies point to the vendors' advisory feeds and APIs as the way out.
Both Fortinet and Cisco publish their security advisories as machine-readable feeds. Pull them, match them against your device inventory, and alert only when something you run is affected. That turns a monthly spreadsheet into a notification.
Linux machines with fwupd and LVFS
Linux has a cleaner story than Windows here. Hardware vendors upload firmware to the Linux Vendor Firmware Service (LVFS), and the fwupd daemon on each machine installs it. The whole flow is four commands:
bashfwupdmgr get-devices fwupdmgr refresh fwupdmgr get-updates fwupdmgr update
The first lists every device fwupd can see, the second pulls the latest metadata, the third shows what's available, and the last installs it. Updates that can apply live do so at once, and boot-time updates are staged for the next restart. Not every vendor publishes to LVFS, so check your hardware before assuming coverage.
Roll it out without bricking anything
A firmware update across a fleet is a change, and it deserves the same care as any other change. Three things go wrong most often: BitLocker, power, and a bad release reaching everyone at once.
BitLocker first. A firmware change can make the TPM see a different boot environment, and BitLocker responds by asking for the recovery key. The fix is to suspend BitLocker before the update and let it resume on its own afterwards. In this r/sysadmin thread, a Dell shop reports roughly one machine in ten hitting the recovery screen after firmware updates, even with suspension configured. The most useful reply: some updates restart more than once, so suspend for two reboots, not one.
On Windows that's one line, run before the update: Suspend-BitLocker -MountPoint "C:" -RebootCount 2. If a TPM error turns up afterwards, our TPM troubleshooting guide walks through it.
Then the rollout itself:
- Check power. Laptops on AC, and no updates scheduled during a known outage window.
- Suspend BitLocker for two reboots. Let the vendor tool do it, and verify it did.
- Pilot ring first. A handful of machines per model, left for a few days.
- Broad ring. The rest of the fleet, once the pilot is clean.
- Keep a way back. Block the release in the vendor tool or pause it in the update policy the moment something breaks.
On Windows 11 and 10, Microsoft now gives you a central place to do this. Intune driver update policies, used alone or with Windows Autopatch, list firmware alongside drivers and let you approve it manually or automatically per deployment ring. Microsoft's Autopatch documentation lets you defer automatically approved driver and firmware updates by 0 to 30 days per ring, which is the pilot window built in. It needs Intune Plan 1 and a Windows license with the Autopatch entitlement.
Disclosure: Flamingo, which publishes this guide, builds OpenFrame.
For the machines outside Intune, the same rollout runs as a script. OpenFrame, open, AI-native infrastructure for IT and security, pulls live device inventory through osquery and runs scripts and scheduled scripts across devices with an approval gate before anything risky goes out, so a vendor tool run can follow the same pilot-then-broad pattern.
Keep a list, then keep it current
Firmware updates are dull right up until the one you skipped matters. Know what runs firmware in your fleet, use the vendor tools and update policies to push it in rings, suspend BitLocker for two reboots, and keep a way back.
Start with the devices that sit on the network edge and the drives that hold the data. For the patching side of the same job, our patch management software roundup is the next read.

Aliaska Varieva
VP of Engineering
Hi! I’m Aliaska, and I’ve been working as a software engineer (mostly Java + a bit Kotlin) for over 8 years now. I mostly spend my time building backend services, integrating systems, fixing bugs (the fun part 🙃), and making sure things don’t fall apart behind the scenes.
Related Content
Frequently Asked Questions
/blog/how-to-update-firmware
Still deciding?
Ask Mingo answers from our docs and customer stories.