Why Secure Boot Certificates Are Expiring in 2026
Microsoft's three original Secure Boot certificate authorities, issued in 2011, are beginning to expire starting June 2026. These certificates are embedded in virtually every Windows PC built since 2012 and are used to validate boot-level software. Once expired, devices that have not received the new 2023 certificates will:
- Lose the ability to install Secure Boot security updates after June 2026
- Not trust third-party firmware signed with new certificates
- Not receive security fixes for Windows Boot Manager by October 2026
- Remain vulnerable to bootkits like BlackLotus (CVE-2023-24932)
Microsoft is distributing three replacement certificates issued in 2023 through Windows Update in a phased rollout:
- Windows UEFI CA 2023 — replaces Windows Production PCA 2011 (signs Windows bootloader)
- Microsoft UEFI CA 2023 / Microsoft Option ROM UEFI CA 2023 — replaces UEFI CA 2011 (signs third-party drivers)
- Microsoft Corporation KEK 2K CA 2023 — replaces KEK CA 2011 (signs updates to DB and DBX)
Many PCs manufactured since 2024 already include these certificates. Older devices receive them via monthly Windows updates.
Step 1 — Check if Secure Boot Is Enabled
Open PowerShell as Administrator (right-click Start → Windows PowerShell (Admin) or Terminal (Admin)) and run:
Confirm-SecureBootUEFITrue = Secure Boot is enabled. False = Secure Boot is disabled — you cannot receive or apply the 2023 certificates with Secure Boot off. Do not toggle Secure Boot on/off, as this can reset UEFI certificate variables to factory defaults.
Step 2 — Check for the Windows UEFI CA 2023 Certificate (One Command)
This is the official and simplest way to verify. In the same PowerShell (Admin) window, run:
([System.Text.Encoding]::ASCII.GetString((Get-SecureBootUEFI db).bytes) -match 'Windows UEFI CA 2023')True = Your PC has the new Windows UEFI CA 2023 certificate. You are protected.
False = Your PC still uses the expiring 2011 certificate. Check Windows Update for pending updates (including Optional/firmware updates).
Step 3 — Check All Three 2023 Certificates
To verify all three replacement certificates (DB and KEK), run these commands:
# Check DB (signature database) for both new 2023 certs
$db = [System.Text.Encoding]::ASCII.GetString((Get-SecureBootUEFI db).bytes)
$db -match 'Windows UEFI CA 2023' # Should return True
$db -match 'Microsoft UEFI CA 2023' # Should return True
# Check KEK for new 2023 cert
$kek = [System.Text.Encoding]::ASCII.GetString((Get-SecureBootUEFI KEK).bytes)
$kek -match 'KEK 2K CA 2023' # Should return TrueAll three returning True means your system is fully updated with the 2023 certificates.
What to Do if the Result is False
If any result returns False, your PC has not yet received the 2023 certificates. Follow these steps:
- Open Settings → Windows Update and click Check for updates
- Under Advanced options → Optional updates, look for firmware or driver updates and install them
- The update KB5074109 (January 2026 and later) initiates the verification and certificate deployment process — ensure it is installed
- Restart your PC after installing updates
- Re-run the PowerShell check above to confirm
Important: Microsoft is rolling these updates out in phases. If you see False, it may simply mean the update has not yet reached your device. Keep Windows Update enabled and check back after a few weeks.
Event Viewer: TPM-WMI Event ID 1801
After the February 2026 Patch Tuesday update, many Windows 11 users see TPM-WMI Event ID 1801 in Event Viewer. This is not an error — it is a log entry confirming that Windows has checked or updated your Secure Boot certificate status. No action is required if this event appears alongside a True result in the PowerShell check above.
Enterprise and IT Admin Considerations
For organizations managing fleets of Windows devices via WSUS, Configuration Manager, or Microsoft Intune:
- Microsoft strongly recommends applying certificate updates well before June 2026
- SCCM/MEM 2509 and later include a new option on boot images: "Use Windows Boot Loader signed with Windows UEFI CA 2023"
- Devices with Secure Boot disabled cannot receive the certificate updates — inventory these devices and enable Secure Boot before the rollout
- Test certificate updates in a pilot group before broad deployment — incompatible firmware may require OEM updates first
- Monitor the Microsoft Secure Boot certificate rollout landing page for phased rollout status



