Thanks for helping me walk through the info. I'll summarize what you said and my findings for people who might be searching for this information:
The updated Secure Boot certificate appears to have been added by the Dell BIOS (probably by 1.33.0) and is available as a fallback in case of a system reset.
Microsoft doesn't appear to have enough reliability signal yet to push the update to my system; whether this is common to all OptiPlex 5000 MFF models is unknown.
Unless my system has other configurations (not mentioned above), Microsoft will most likely update my system automatically. I won't be doing anything for now.
The soft dateline when certificates start expiring is in June 2026, and the hard deadline when Microsoft might start removing expired certificates is in October. If I still don't see the update in November, I should try a manual update.
Claude AI suggested the following Powershell steps (not checked for correctness; effectiveness unknown):
After May 2026 Patch Tuesday update, the certificate has been updated. The powershell command shown in the OP returned true. And the Windows Security screen showed this:
I don't have the same machine. But, you can run Windows update until you receive Secure Boot Allowed Key Exchange Key (KEK) Update. That should make Powershell command returns a True.
You can verify if the system has been updated with KEK update. While on Windows Update page, select Update history. There should be 4 groups, select the last one, Other updates and check for any KEK update.
Another way to check is going to Windows Security, click on Device Security and checking the status of Secure Boot. If it has been updated with KEK update, the status will say everything is okay, no other change needed.
I checked Other updates in Windows Update History—there’s nothing about KEK. I also checked Secure Boot under Device Security; it says I’m still on the older boot-trust configuration.
It's back to square one, my first response. With the new BIOS update, you would get a true for 2023 certificate is in firmware database. With the Windows update with KEK update, you will get a true for 2023 certificate actively being used at boot.
Just verify your system for UEFI mode is ON, Secure Boot is ON, and TPM is ON, Run update again, then use computer for whatever purpose you need. The KEK update will run by itself and sending you notification (on system tray) to restart the system. After KEK update applied, you will get a true.
All mentioned—UEFI, Secure Boot, and TPM—have always been on.
I found another PowerShell command from a search (screenshot attached) that returns True, but since my OP screen returns False and the Device Security screen still shows the "old trust configuration," I don't know how it affects the active certificate status on my system. Supposedly the secondary PowerShell command polls the "Default Database" (the backup certificates stored in BIOS). Do you know the differences?
Although there are some ways to run manually to get the update, just wait until next Tuesday and run update again. It's very likely that your system will be updated with all require certificates before June.
tikmokf5d6ac
1 Rookie
•
12 Posts
•
50 Points
0
0
Posted May 7th, 2026 10:56
Thanks for helping me walk through the info. I'll summarize what you said and my findings for people who might be searching for this information:
Claude AI suggested the following Powershell steps (not checked for correctness; effectiveness unknown):
1. Tell Windows to apply the cert
Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\SecureBoot" -Name "AvailableUpdates" -Value 0x40
2. Kick off the scheduled task immediately
Start-ScheduledTask -TaskName "\Microsoft\Windows\PI\Secure-Boot-Update"