We have observed update times range from fewer than 5 seconds to more than 30 seconds. How long a drive takes to activate depends on its design and the type of firmware you update. Here's an example of the cmdlet in action: $pd | Update-StorageFirmware -ImagePath -SlotNumber 0įirmwareVersionInSlot : typically do not complete I/O requests when they activate a new firmware image. An application accessing data on this drive would have to wait for a response until the firmware activation completes. This means that this drive serves no data during the activation. During this time the drive will not be able to respond to I/O commands as an internal reset occurs. While this happens, I/O typically continues. The drive will first load the new firmware image to an internal staging area. You should obtain this image file from the OEM or drive vendor directly.īefore updating any production hardware, test the particular firmware image on identical hardware in a lab setting. The second cmdlet, Update-StorageFirmware, enables administrators to update the drive firmware with an image file, if the drive supports the new firmware update mechanism. Note that SAS devices always report 'SupportsUpdate' as 'True', since there is no way of explicitly querying the device for support of these commands. Here's an example: Get-PhysicalDisk | Get-StorageFirmwareInformation In this case, the machine only contains a single SATA SSD with 1 firmware slot. The first cmdlet provides you with detailed information about the device's capabilities, firmware images, and revisions. SAS: .Sas - in the Firmware Download & Activate section SATA: .Sata - in the Firmware Download & Activate section Here are links to the various requirements:

To support these requirements, there is a new HLK test to verify if vendor products support the right commands and get them implemented in future revisions.Ĭontact your solution vendor for info about whether your hardware supports Windows updating the drive firmware.

These requirements outline which commands a SATA, SAS, or NVMe device must support to be firmware-updatable using these new, Windows-native PowerShell cmdlets. To ensure common device behavior, we began by defining new and - for Windows 10 and Windows Server 2016 - optional Hardware Lab Kit (HLK) requirements for SAS, SATA, and NVMe devices. To use Windows Server to update drive firmware, you must have supported drives. Administrators should read the release notes a given update comes with to determine its impact and applicability. It is possible that new firmware on unsupported hardware could negatively affect reliability and stability, or even cause data loss. Firmware updates are a potentially risky maintenance operation and you should only apply them after thorough testing of the new firmware image.

Upgrade firmware version 1.255