PowerEdge: Server BIOS Update Guidelines for Microsoft Secure Boot Certificates

Summary: This article provides guidance for Dell PowerEdge servers requiring remediation for the Microsoft Secure Boot certificate expiration (June 2026). It applies to UEFI-based systems with Secure Boot enabled and older Secure Boot certificates affected by the Microsoft Secure Boot certificate expiration (June 2026). The operating system primarily manages Secure Boot certificate updates, and customers should ensure they update their systems using supported Microsoft update mechanisms. It applies to Windows Server operating systems affected by this change, as defined by Microsoft, running on physical systems with customer-managed firmware and Secure Boot configuration. It does not apply to cloud platforms or appliances where the provider manages firmware and Secure Boot keys, such as Microsoft Azure, AX, or APEX-Managed Cloud. Systems already running BIOS versions that include the updated Secure Boot certificates may not require this procedure. ...

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Instructions

Targeted Servers and Operating Systems

This guidance applies to:

  1. Dell PowerEdge servers that support UEFI boot mode and Secure Boot
  2. Systems running supported Windows Server operating systems affected by the Microsoft Secure Boot certificate expiration (June 2026), as defined by Microsoft. For operating systems other than Microsoft Windows, the normal BIOS update process can be followed to get the new certificates added.
  3. Physical servers, including 14th, 15th, and 16th generations

 

For virtual machines (UEFI-based), follow the guidance provided by the Hypervisor vendor.

Microsoft Hyper-V: Secure Boot Certificate updates: Guidance for IT professionals and organizationsThis hyperlink is taking you to a website outside of Dell Technologies.

VMware ESXi: Secure Boot Certificate Expirations and Update Failures in VMware Virtual MachinesThis hyperlink is taking you to a website outside of Dell Technologies.

 

Server Generations and BIOS Identifiers

The BIOS versions listed below represent minimum releases that include the updated Microsoft Secure Boot certificates. BIOS versions newer than those listed below also contain the new secure boot certificates.

 

Platform

BIOS Version

R260, R360, T160, T360

 2.4.0

R660, R760, R860, R760XD2, R760XA, XE8640, XE9680, HS5620, XR7620, R760XS, XR5610, XR8610T, XR8620T, R960, T560, MX760C, XC760, VS-760, XC660, XC760XD2, VE660, VP-760, XC660XS, XC760XA, VP-760XA, R660xs, MC-760

 2.8.2

 R6625, R7625

 1.15.3

C6615

 1.10.3 

R6615, R7615

 1.15.3

R750, R750xa, R750xs, R650, R650xs, R550, R450, C6520, MX750c, T550

 1.19.2

XR4510c, XR4520c

 1.21.1

R350, R250, T350, T150

 1.13.0

R6515, R7515

 2.22.0 

R6525, R7525

 2.22.0

R7425

1.23.0

R7415, R6415

1.23.0

R740, R740XD, R640, R940

 2.25.0

C4140

 2.25.0 

R840, R940XA

 2.25.0

T640

 2.25.0

R540, R440, T440

 2.25.0 

R740XD2

 2.25.0 

MX740C

 2.25.0 

MX840

 2.25.0

M640, FC640, M640(VRTX)

 2.25.0

C6420

 2.25.0

XE7420, XE7440

 2.25.0

XE2420

 2.25.0

R340, T340, R240, T140

 2.21.0

 

Important
Before proceeding with the below steps, verify that Secure Boot is enabled and configured using the default (Standard) Secure Boot policy.

Systems using custom or third‑party Secure Boot policies may require additional review before Secure Boot certificate updates can be applied.

If Secure Boot is not enabled, follow the traditional BIOS update process. Steps below are not required.

 

Note: The following files may only be attached to the English version of this article.

 Recommended Procedure

  1. Verify system configuration
    • If BitLocker is enabled, temporarily suspend BitLocker protection before proceeding to avoid recovery prompts after reboot.
    • If required, temporarily set the PowerShell Execution Policy to 'Unrestricted' or 'Bypass' to allow script execution. (Set-ExecutionPolicy command)
    • For Failover clusters (S2D, SAN Attached) - Add 'Suspend-ClusterNode -Drain' to pause the node and move clustered roles to another node.
    • System firmware (BIOS) is at a supported and stable release (for example, a current or production‑approved BIOS version for the platform). Systems already running BIOS versions that include the updated Secure Boot certificates do not require this procedure.
  2. Run the Microsoft Secure Boot 2023 certificate update scripts
    • Download and extract the Secure Boot update scripts attached to this article
      • For 16G - Copy 16G_Secure_Boot_Certificates_pkb.zip and extract into any folder.
      • For 15G - Copy 15G_Secure_Boot_Certificates_pkb.zip and extract into any folder.
      • For 14G - Copy 14G_Secure_Boot_Certificates_pkb.zip and extract into any folder. 
    • Run the scripts using an elevated (Administrator) command prompt as documented by Microsoft
      • For 16G: 16G_SecureBoot_Cert_Update.ps1
      • For 15G: 15G_SecureBoot_Cert_Update.ps1
      • For 14G: 14G_SecureBoot_Cert_Update.ps1
    • Follow the on‑screen instructions
    • Reboot the server when prompted

 

Note: During execution, systems may log informational events such as UEFI00074. These messages are expected and do not indicate a failure.

 

  1. Apply Windows Updates
    • After the reboot, ensure that the system is fully updated with the latest available Windows cumulative updates for the installed operating system. Windows updates are required to ensure Secure Boot certificate updates, and revocations are fully applied and kept current within the operating system.
  2. Validate Secure Boot certificate state
  3. Post‑update validation
    • Confirm the system boots successfully
    • Verify Secure Boot remains enabled

Additional considerations:

  • BIOS updates may change platform measurements used by BitLocker and VBS.
  • In rare cases, systems with BitLocker enabled may prompt for recovery after firmware updates.
  • Suspending BitLocker prior to BIOS and Secure Boot updates is recommended to avoid recovery prompts.

      Affected Products

      Dell XC Core XC660, Dell XC Core XC660xs, Dell XC Core XC760, Dell XC Core XC760xa, OEMR R240, OEMR R250, OEMR R260, OEMR R340, OEMR R350, OEMR R360, OEMR R440, OEMR R450, OEMR R540, OEMR R550, OEMR R640, OEMR R6415, OEMR R650, OEMR R650xs , OEMR R6515, OEMR R6525, OEMR R660, OEMR R6615, OEMR R6625, OEMR R740, OEMR R740xd, OEMR R740xd2, OEMR R7415, OEMR R7425, OEMR R750, OEMR R750xa, OEMR R750xs, OEMR R7515, OEMR R7525, OEMR R760, OEMR R760xa, OEMR R760XD2, OEMR R7615, OEMR R7625, OEMR R840, OEMR R860, OEMR R940, OEMR R940xa, OEMR R960, OEMR T140, OEMR T150, OEMR T340, OEMR T350, OEMR T360, OEMR T440, OEMR T550, OEMR T560, OEMR T640, OEMR XR4510c, OEMR XR4520c, OEMR XR5610, OEMR XR7620, OEMR XR8610t, OEMR XR8620t, Poweredge C4140, PowerEdge C6420, PowerEdge C6520, PowerEdge C6615, PowerEdge FC640, PowerEdge HS5620, PowerEdge M640, PowerEdge M640 (for PE VRTX), PowerEdge MX740C, PowerEdge MX750c, PowerEdge MX760c, PowerEdge MX840C, PowerEdge R240, PowerEdge R250, PowerEdge R260, PowerEdge R340, PowerEdge R350, PowerEdge R360, PowerEdge R440, PowerEdge R450, PowerEdge R540, PowerEdge R550, PowerEdge R640, PowerEdge R6415, PowerEdge R650, PowerEdge R650xs, PowerEdge R6515, PowerEdge R6525, PowerEdge R660, PowerEdge R6615, PowerEdge R6625, PowerEdge R740, PowerEdge R740XD, PowerEdge R740XD2, PowerEdge R7415, PowerEdge R7425, PowerEdge R750, PowerEdge R750XA, PowerEdge R750xs, PowerEdge R7515, PowerEdge R7525, PowerEdge R760, PowerEdge R760XA, PowerEdge R760xd2, PowerEdge R7615, PowerEdge R7625, PowerEdge R840, PowerEdge R860, PowerEdge R940, PowerEdge R940xa, PowerEdge R960, PowerEdge T140, PowerEdge T150, PowerEdge T160, PowerEdge T340, PowerEdge T350, PowerEdge T360, PowerEdge T440, PowerEdge T550, PowerEdge T560, PowerEdge T640, PowerEdge XE2420, PowerEdge XE7420, PowerEdge XE7440, PowerEdge XE8640, PowerEdge XE9680, PowerEdge XR4510c, PowerEdge XR4520c, PowerEdge XR5610, PowerEdge XR7620, PowerEdge XR8610t, PowerEdge XR8620t, VxRail VE-660, VxRail VP-760, VxRail VS-760 ...

      Products

      OEMR R660xs, PowerEdge R660xs

      Attachments

      14G_Secure_Boot_Certificates_pkb_en_US_1.zip 15G_Secure_Boot_Certificates_pkb_en_US_1.zip 16G_Secure_Boot_Certificates_pkb_en_US_1.zip

      Article Properties
      Article Number: 000402373
      Article Type: How To
      Last Modified: 18 ذو الحجة 1447
      Version:  8
      Find answers to your questions from other Dell users
      Support Services
      Check if your device is covered by Support Services.