{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-029-locate-the-failed-layer-in-a-drive-firmware-update-attempt/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260908-029-locate-the-failed-layer-in-a-drive-firmware-update-attempt/", "slug": "dse-20260908-029-locate-the-failed-layer-in-a-drive-firmware-update-attempt", "url": "https://update.dsesecurity.com/updates/dse-20260908-029-locate-the-failed-layer-in-a-drive-firmware-update-attempt/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260908-029-locate-the-failed-layer-in-a-drive-firmware-update-attempt.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-029-locate-the-failed-layer-in-a-drive-firmware-update-attempt/" }, "title": "Locate the failed layer in a drive firmware-update attempt", "summary": "How should a failed Windows drive firmware update be investigated?", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "continuity-recovery", "label": "Continuity & recovery", "alt": "Paired infrastructure paths converging on a stable recovered service.", "card_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "business-continuity", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "slug": "it", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "author": { "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team", "type": "Organization" }, "publisher": { "name": "Detection Systems & Engineering", "url": "https://dsesecurity.com/" }, "published_at": "2026-09-08T18:16:42+00:00", "modified_at": "2026-09-08T18:17:14+00:00", "reviewed_on": "2026-09-08", "reading_minutes": 2, "word_count": 226, "potentially_affected": "Use this review after a drive firmware operation fails or capability is uncertain.", "dse_recommendation": "Reproduce the capability query without changing the firmware first.", "primary_source": { "name": "Troubleshooting drive firmware updates", "url": "https://learn.microsoft.com/en-us/windows-server/storage/troubleshoot-firmware-update", "published_on": null, "authority": "Microsoft Learn" }, "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usage_info": "https://update.dsesecurity.com/usage/", "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "content_html": "

Source facts

\n

Microsoft explains that the PowerShell firmware-update path depends on Windows storage APIs, drivers, hardware, and their implementation of the required commands. Failures can arise at several of these layers. The documentation uses Get-StorageFirmwareInfo with a PhysicalDisk object to check whether a device exposes the expected command support. For unsupported commands, Microsoft directs administrators to the vendor or Windows Server Catalog for suitable firmware or devices. Microsoft documentation.

\n

Applicability

\n

Use this review after a drive firmware operation fails or capability is uncertain. Identify the exact drive, controller, driver, and attempted operation before retrying. Keep the original error and the device’s reported firmware version.

\n

DSE recommendation

\n

Reproduce the capability query without changing the firmware first. Compare the returned information with the intended device and the vendor documentation. Escalate a command-support gap with the hardware details and original failure evidence. Ask the storage owner to approve any further update attempt, including its workload impact, instead of treating repeated retries as a diagnostic method.

\n

Verification

\n

Retain the query output and identify the layer for which support remains unconfirmed. If a vendor-approved correction is later tested, compare the before-and-after capability and firmware observations. Check the associated workload through the agreed acceptance procedure. Close the issue only when the original failure and the corrective action are both accounted for.

\n

Official references

\n

Microsoft Learn: Troubleshooting drive firmware updates. Source reviewed September 8, 2026.

", "content_text": "Source facts\nMicrosoft explains that the PowerShell firmware-update path depends on Windows storage APIs, drivers, hardware, and their implementation of the required commands. Failures can arise at several of these layers. The documentation uses Get-StorageFirmwareInfo with a PhysicalDisk object to check whether a device exposes the expected command support. For unsupported commands, Microsoft directs administrators to the vendor or Windows Server Catalog for suitable firmware or devices. Microsoft documentation.\nApplicability\nUse this review after a drive firmware operation fails or capability is uncertain. Identify the exact drive, controller, driver, and attempted operation before retrying. Keep the original error and the device’s reported firmware version.\nDSE recommendation\nReproduce the capability query without changing the firmware first. Compare the returned information with the intended device and the vendor documentation. Escalate a command-support gap with the hardware details and original failure evidence. Ask the storage owner to approve any further update attempt, including its workload impact, instead of treating repeated retries as a diagnostic method.\nVerification\nRetain the query output and identify the layer for which support remains unconfirmed. If a vendor-approved correction is later tested, compare the before-and-after capability and firmware observations. Check the associated workload through the agreed acceptance procedure. Close the issue only when the original failure and the corrective action are both accounted for.\nOfficial references\nMicrosoft Learn: Troubleshooting drive firmware updates. Source reviewed September 8, 2026.", "content_markdown": "## Source facts\n\nMicrosoft explains that the PowerShell firmware-update path depends on Windows storage APIs, drivers, hardware, and their implementation of the required commands. Failures can arise at several of these layers. The documentation uses Get-StorageFirmwareInfo with a PhysicalDisk object to check whether a device exposes the expected command support. For unsupported commands, Microsoft directs administrators to the vendor or Windows Server Catalog for suitable firmware or devices. [Microsoft documentation](https://learn.microsoft.com/en-us/windows-server/storage/troubleshoot-firmware-update).\n\n## Applicability\n\nUse this review after a drive firmware operation fails or capability is uncertain. Identify the exact drive, controller, driver, and attempted operation before retrying. Keep the original error and the device’s reported firmware version.\n\n## DSE recommendation\n\nReproduce the capability query without changing the firmware first. Compare the returned information with the intended device and the vendor documentation. Escalate a command-support gap with the hardware details and original failure evidence. Ask the storage owner to approve any further update attempt, including its workload impact, instead of treating repeated retries as a diagnostic method.\n\n## Verification\n\nRetain the query output and identify the layer for which support remains unconfirmed. If a vendor-approved correction is later tested, compare the before-and-after capability and firmware observations. Check the associated workload through the agreed acceptance procedure. Close the issue only when the original failure and the corrective action are both accounted for.\n\n## Official references\n\n[Microsoft Learn: Troubleshooting drive firmware updates](https://learn.microsoft.com/en-us/windows-server/storage/troubleshoot-firmware-update). Source reviewed September 8, 2026." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/dse-20260908-029-locate-the-failed-layer-in-a-drive-firmware-update-attempt/", "url": "https://update.dsesecurity.com/updates/dse-20260908-029-locate-the-failed-layer-in-a-drive-firmware-update-attempt/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-08" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260908-029-locate-the-failed-layer-in-a-drive-firmware-update-attempt/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Locate the failed layer in a drive firmware-update attempt", "item": "https://update.dsesecurity.com/updates/dse-20260908-029-locate-the-failed-layer-in-a-drive-firmware-update-attempt/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260908-029-locate-the-failed-layer-in-a-drive-firmware-update-attempt/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260908-029-locate-the-failed-layer-in-a-drive-firmware-update-attempt/", "url": "https://update.dsesecurity.com/updates/dse-20260908-029-locate-the-failed-layer-in-a-drive-firmware-update-attempt/", "headline": "Locate the failed layer in a drive firmware-update attempt", "description": "How should a failed Windows drive firmware update be investigated?", "abstract": "How should a failed Windows drive firmware update be investigated?", "articleBody": "Source facts\nMicrosoft explains that the PowerShell firmware-update path depends on Windows storage APIs, drivers, hardware, and their implementation of the required commands. Failures can arise at several of these layers. The documentation uses Get-StorageFirmwareInfo with a PhysicalDisk object to check whether a device exposes the expected command support. For unsupported commands, Microsoft directs administrators to the vendor or Windows Server Catalog for suitable firmware or devices. Microsoft documentation.\nApplicability\nUse this review after a drive firmware operation fails or capability is uncertain. Identify the exact drive, controller, driver, and attempted operation before retrying. Keep the original error and the device’s reported firmware version.\nDSE recommendation\nReproduce the capability query without changing the firmware first. Compare the returned information with the intended device and the vendor documentation. Escalate a command-support gap with the hardware details and original failure evidence. Ask the storage owner to approve any further update attempt, including its workload impact, instead of treating repeated retries as a diagnostic method.\nVerification\nRetain the query output and identify the layer for which support remains unconfirmed. If a vendor-approved correction is later tested, compare the before-and-after capability and firmware observations. Check the associated workload through the agreed acceptance procedure. Close the issue only when the original failure and the corrective action are both accounted for.\nOfficial references\nMicrosoft Learn: Troubleshooting drive firmware updates. Source reviewed September 8, 2026.", "datePublished": "2026-09-08T18:16:42+00:00", "dateModified": "2026-09-08T18:17:14+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260908-029-locate-the-failed-layer-in-a-drive-firmware-update-attempt/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/dse-20260908-029-locate-the-failed-layer-in-a-drive-firmware-update-attempt/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Locate the failed layer in a drive firmware-update attempt" }, "articleSection": [ "Business Continuity", "IT" ], "keywords": [ "Business Continuity", "IT", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "wordCount": 226, "timeRequired": "PT2M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "Troubleshooting drive firmware updates", "url": "https://learn.microsoft.com/en-us/windows-server/storage/troubleshoot-firmware-update" } } ] } }