PowerEdge: Server BIOS Update Guidelines for Microsoft Secure Boot Certificates
Summary: Before updating Dell PowerEdge servers running Windows to the December 2025 BIOS release, complete the required pre-requisites. The BIOS update includes new Secure Boot Certificates, and failure to follow the steps below may result in the server entering an undefined state. If Secure Boot is not enabled, the BIOS can be updated through the normal process and this document is not applicable. Note: This document is applicable only if the server has Secure Boot enabled, TPM enabled, and running the Windows Server operating system. ...
Instructions
Failure to follow the steps below may result in the server entering an undefined state.
Undefined State Symptoms:
- Entering BitLocker Recovery screen during system boot.
- Azure Stack or local registration status showing "Out of Policy" error. https://learn.microsoft.com/en-us/previous-versions/azure/azure-local/deploy/troubleshoot-hci-registration#out-of-policy-error
Targeted Servers and Operating Systems
All PowerEdge 14th, 15th, and 16th generations of servers running Windows Server or Azure Stack HCI
Server Generations and BIOS Identifiers
Below are the details of BIOS versions released for different generations of Dell PowerEdge servers which include Microsoft Secure Boot certificates 2023.
|
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 |
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 |
Pre-Requisites
- Server must be running a BIOS version released prior to the versions noted above.
- Server must have TPM2.0, and it should be active.
- Secure Boot should be enabled.
- BitLocker should be disabled. If BitLocker is already in use, it should be temporarily disabled.
- Follow the instructions at the link below to manage BitLocker with Azure Stack HCI Cluster.
- Manage BitLocker encryption on Azure Local
- Users should have administrative rights for the server.
- PowerShell Execution Policy should be set to 'Unrestricted' or 'Bypass'. (Use
Set-ExecutionPolicycommand)
Note: The following files may only be attached to the English version of this article.
Steps to Update Secure Boot Certificates and BIOS.
- Ensure that the server is running a BIOS version prior to what is noted above.
- System should be running the Windows Server 2025, Windows Server 2022, or HCI operating system.
- Download Secure Boot certificates and scripts attached to this KB.
- Copy the Secure Boot certificates to the system.
- For 16G - Copy
16G_Secure_Boot_Cerifcates_pkb.zipand extract into any folder. - For 15G - Copy
15G_Secure_Boot_Cerifcates_pkb.zipand extract into any folder. - For 14G - Copy
14G_Secure_Boot_Cerifcates_pkb.zipand extract into any folder.
- For 16G - Copy
- Run the appropriate script to update Secure Boot certificates.
- For 16G:
16G_SecureBoot_Cert_Update_pkb.ps1 - For 15G:
15G_SecureBoot_Cert_Update_pkb.ps1 - For 14G:
14G_SecureBoot_Cert_Update_pkb.ps1 - The path of the folder where all the required certificate files are stored, must be provided as input.
- For 16G:
- Ensure that the script runs successfully and a reboot message appears.
- Reboot the server.
- NOTE: UEFI0074 warning "The Secure Boot policy has been modified since the last time the system was started" may appear during BIOS POST and in the Lifecycle log.
- Once the server reboots into the operating system, update the BIOS by any update tool/mechanism supported by Dell (Dell Update Package, iDRAC, OpenManage Enterprise, etc).
- Reboot the server again.
- Verify that the server is running the new BIOS.
- Dell suggests checking that the new secure boot certificates are available in the BIOS. This is done by running the following script from within the operating system.
-
Check UEFI KEK, DB, and DBX.ps1 - This script can be downloaded from here: GitHub: Check-UEFISecureBootVariables
-
When the script is run, the output below is expected.
Affected Products
Attachments
16G_Secure_Boot_Cerificates_pkb_en_US_1.zip 15G_SecureBoot_Cert_Update_pkb_en_US_1.ps1 15G_Secure_Boot_Certificates_pkb_en_US_1.zip 14G_SecureBoot_Cert_Update_pkb_en_US_1.ps1 16G_SecureBoot_Cert_Update_pkb_en_US_1.ps1 14G_Secure_Boot_Cerifcates_pkb_en_US_1.zip