# Confirm drive and vendor compatibility before a Windows firmware update

> What should be established before using Windows to update drive firmware?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260908-030-confirm-drive-and-vendor-compatibility-before-a-windows-firmware-update/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-08T18:16:41+00:00
- Modified: 2026-09-08T18:17:14+00:00
- Last reviewed by DSE: 2026-09-08
- Resource type: Guide
- DSE priority: Information
- Topics: Business Continuity, IT
- Reading time: 1 minutes

## What you need to know

What should be established before using Windows to update drive firmware?

## Potentially affected

Use this review when preparing a drive firmware change.

## DSE recommendation

Create a drive-specific plan naming the current firmware, proposed image, hardware identity, and vendor support reference.

## Article

## Source facts

Windows-native firmware updating requires drives that implement the relevant supported commands; Microsoft describes hardware testing requirements for SAS, SATA, and NVMe devices. Microsoft recommends applying the firmware recommended by the hardware vendor or OEM before a server enters production. The documented ability to update a production drive without downtime is conditional on support for the Windows firmware-update mechanism. [Microsoft documentation](https://learn.microsoft.com/en-us/windows-server/storage/update-firmware).

## Applicability

Use this review when preparing a drive firmware change. Identify the complete supported storage solution, not just a drive model. Review the vendor instructions and the source’s production-update precautions for the actual deployment.

## DSE recommendation

Create a drive-specific plan naming the current firmware, proposed image, hardware identity, and vendor support reference. Have the storage owner approve the update sequence and workload acceptance test. Confirm the available recovery arrangements and monitoring coverage before execution. Pilot the approved image on an appropriate representative device and retain the original inventory for comparison.

## Verification

After the approved update, query the actual firmware revision and compare it with the intended image. Examine storage and application health through the agreed workload test. Record any interruption observed instead of assuming none occurred. Preserve the result for each drive and pause the remaining sequence if the image or health evidence differs from the plan.

## Official references

[Microsoft Learn: Updating drive firmware](https://learn.microsoft.com/en-us/windows-server/storage/update-firmware). Source reviewed September 8, 2026.

## Primary reference

- Name: Updating drive firmware
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/windows-server/storage/update-firmware
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Confirm drive and vendor compatibility before a Windows firmware update,” DSE Security, https://update.dsesecurity.com/updates/dse-20260908-030-confirm-drive-and-vendor-compatibility-before-a-windows-firmware-update/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.