Secure Boot expires, and everything keeps booting
On 19 October, the last of the three Secure Boot certificates from 2011 expired. No computer stops because of it. But devices without the 2023 certificates no longer receive fixes for the boot chain, and no error message shows it.
On 19 October 2026, the certificate "Microsoft Windows Production PCA 2011" expired. Microsoft used it to sign the Windows bootloader. It was the last of three Secure Boot certificates from 2011; the other two ran out in June.
In most organisations, nobody noticed. That is by design, and that is exactly the problem.
What has expired
Microsoft lists three certificates, each with a successor from 2023:
- Microsoft Corporation KEK CA 2011, expired on 24 June 2026. It signs changes to the Secure Boot databases, that is, to the list of allowed and revoked boot software. Successor: Microsoft Corporation KEK 2K CA 2023.
- Microsoft UEFI CA 2011, expired on 27 June 2026. It signs bootloaders and firmware extensions from other vendors. It is succeeded by two separate certificates: Microsoft UEFI CA 2023 for bootloaders and Microsoft Option ROM UEFI CA 2023 for expansion cards.
- Microsoft Windows Production PCA 2011, expired on 19 October 2026. It signs the Windows bootloader. Successor: Windows UEFI CA 2023.
What a device without the new certificates notices
Nothing. Microsoft writes that such a device continues to start and run normally, and that regular Windows updates continue to install. What is missing are new protections for the early boot phase: updates to the Windows Boot Manager, to the databases of allowed and revoked boot software, and fixes for newly discovered vulnerabilities in the boot chain. Microsoft explicitly names BitLocker bypass mitigations as an example.
Since 19 October, this is no longer an announcement. In KB article 5132953, Microsoft writes that the last Boot Manager releases signed with the 2011 certificate are frozen and will receive no further security patches. All subsequent bootloader fixes are signed with the 2023 certificate chain only.
Why this gets lost in practice
The usual signals stay green. The computer starts, the patch level is current, vulnerability scanning finds nothing, because it asks about software versions, not about the contents of the firmware database. The gap only becomes visible when the next boot chain vulnerability is published and the fix does not reach part of the estate.
On top of that, not every device gets the new certificates through Windows Update alone. Microsoft points out that some devices need a firmware update from the manufacturer, and that it may only be available for devices still within the manufacturer's support period. Older hardware then stays on the frozen 2011 bootloader.
What to do
- Measure first. Microsoft keeps the status in the registry under
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecureBoot\Servicing, valueUEFICA2023Status. It reads NotStarted, InProgress or Updated. Count per device, not per department. - Then roll out. For managed devices, Microsoft describes the route via Group Policy, Intune or a registry value that triggers the update. Windows Update handles personal devices on its own, managed devices not necessarily.
- Name the old devices. Which devices will not get a firmware update any more? They need a decision: replace them, or keep them as an exception with a reason and an expiry date.
- Do not forget virtual machines. VMs with Secure Boot have their own firmware database too. Microsoft has separate guidance for them, for example for Trusted Launch and Confidential VMs in Azure.
- Check application control rules. Since 19 October, Microsoft no longer signs files with the 2011 certificate. According to Microsoft, anyone whose App Control for Business policies or own verification tools trust exactly this certificate may block the updated files.
- Do not switch Secure Boot off. Microsoft explicitly advises against working around the expiry that way.
The test question
On how many of your Windows devices does UEFICA2023Status read Updated today?
If you do not know the number, you will otherwise learn it with the next bootloader vulnerability.
Sources
Microsoft Support: Windows Secure Boot certificate expiration and CA updates, retrieved 9 November 2026.
Microsoft Support: When Secure Boot certificates expire on Windows devices, retrieved 9 November 2026.
Microsoft Support: KB5132953, Windows Production CA 2011 expiration and bootloader updates, published 22 October 2026.
Microsoft Support: Registry key updates for Secure Boot, Windows devices with IT-managed updates, retrieved 9 November 2026.
Questions about this update?
Talk to us – we are happy to show you this feature in a demo.


