Secure Boot Certificates Expired: What It Means (2026)
Windows security & licensing · every fact traced to Microsoft KB or Learn pages, re-checked monthly
Quick Answer
This is not a doomsday deadline like Windows 10’s October 2025 cutoff. It is a maintenance event with a quiet failure mode: the PC that misses the rollout keeps working — and quietly stops being protectable at the one stage of boot where malware like BlackLotus used to live.
03 What happens to a PC that never updates? 04 Getting the 2023 certificates installed
05 How to check Secure Boot on your PC 06 FAQ
• Microsoft UEFI CA 2011 (third-party boot software) expired June 27, 2026; Windows Production PCA 2011 (the Windows boot loader cert) expired October 19, 2026.
• Nothing stops booting: un-updated devices “continue to start and operate normally” (Microsoft) — but they stop receiving new early-boot security protections.
• The 2023 replacement certificates have ridden normal Windows Update since 2023 and are valid into 2039–2040.
• The 30-second check: msinfo32 → Secure Boot State, plus Windows Update kept current.
| Windows 11 Pro OEM key BEST SELLER
Best for: Secure Boot-ready upgrades and new installs
|
Check price ↗ |
| Windows 11 Home key
Best for: Home PCs that pass the Secure Boot/TPM check
|
Check price ↗ |
| Windows 10 IoT Enterprise 2021
Best for: Fixed-purpose machines on the LTSC track
|
Check price ↗ |
| Windows Server IoT 2022
Best for: Server and appliance builds
|
Check price ↗ |
Disclosure: links go to KeyStarter products; we may earn from qualifying purchases. Prices are set at checkout.
01What exactly expired in 2026?
Secure Boot works by checking the digital signature of everything that loads before Windows against certificates stored in the PC’s firmware (UEFI). Two of Microsoft’s signing certificates from 2011 have now run out: Microsoft UEFI CA 2011 on June 27, 2026, and Microsoft Windows Production PCA 2011 — the one that signs the Windows boot loader itself — on October 19, 2026.
The replacements have existed since 2023: Windows UEFI CA 2023 and companion 2023 certificates for third-party boot software, valid into 2039–2040. Microsoft announced the transition in June 2025 (KB5062710) and has shipped the new certificates through regular Windows Update channels for Windows 8, 10, 11 and Server ever since.
Bottom line. two 2011-era signing certificates hit their expiry dates in 2026 — and expiry is a maintenance deadline, not a kill switch.
02Is your PC actually affected?
If the machine has taken normal Windows updates since 2023, it almost certainly already trusts the 2023 certificates and nothing changes for you. The affected population is narrower: PCs that have been offline or frozen for years, machines with Windows Update broken, and some virtual machines or managed fleets that never received the rollout.
Bottom line. an internet-connected PC kept current through Windows Update is already carrying the 2023 certificates — the check in section 05 confirms it.
03What happens to a PC that never gets the 2023 certificates?
The failure mode is quiet. The old boot loader keeps passing signature checks against the old certificate in firmware, so the machine boots, runs and installs regular updates exactly as before — Microsoft says so explicitly. What it stops doing is receiving new protections for the early boot process: future DBX revocations (the mechanism that blocks bootkits like BlackLotus) and newly signed boot components can no longer be trusted by that firmware.
| Device state after Oct 19, 2026 | Boots? | Early-boot protections | What to do |
|---|---|---|---|
| Windows 10/11, updates current | Yes | Protected (2023 certs in place) | Nothing — confirm Secure Boot is on |
| Secure Boot turned off in firmware | Yes | Inactive — expiry is irrelevant | Re-enable in UEFI settings when convenient |
| Offline machine, missed the rollout | Yes | Frozen at the 2011 state | Get current via Windows Update once online |
| Third-party boot software (Linux, VeraCrypt) | Depends | Needs the 2023 KEK/option-ROM chain | Follow vendor guidance before changing anything |
Windows 10 machines on Extended Security Updates are in the same boat as everyone else: the certificates shipped through the same update channels, so an ESU-enrolled machine that stays current is covered — our Windows 10 ESU enrollment guide covers that program’s deadlines separately.

Bottom line. nothing breaks on October 19 — the machine just quietly stops being protectable against future boot-level threats until it catches up.
04How do you get the 2023 certificates installed?
For a normal PC, the answer is: keep doing what you are doing. The certificates arrive as part of regular servicing updates from Windows Update — there is no separate purchase, license or download. The only real work is for machines that have drifted:
1Connect to the internet and open Settings → Windows Update, then install everything offered until the page says you’re up to date.
2Reboot when asked — some servicing updates for the boot chain apply across restarts.
3For managed fleets, audit certificate state with Microsoft’s key creation and management guidance (linked in the references) instead of trusting one machine as proof.
Bottom line. Windows Update is the entire delivery mechanism — a current machine is a protected machine.
05How do you check Secure Boot on your own PC?
1Press Win+R, type msinfo32 and press Enter.
2In System Summary, read the Secure Boot State line — On means Secure Boot is active.
3Open Settings → Windows Update → Update history and confirm recent servicing updates install without errors.
Windows does not show a plain “certificate version” screen, so the practical proof is the pair above: Secure Boot On plus a current update history means the machine is on the normal protected path. And because Secure Boot has been a Windows 11 requirement, any machine you are preparing for an upgrade should be checked first — our Windows 11 Pro key buying guide puts that check at step one of the upgrade. If a key is the missing piece, the Windows 11 Pro listing resolves it the same day. And check the OS version while you are at it — Windows 11 24H2 just ended updates for Home and Pro, a deadline our Windows 11 24H2 lifecycle guide explains.
Bottom line. msinfo32 plus update history answers the question in half a minute — no tools, no firmware digging.

06Frequently asked questions
Do I have to replace my PC because the Secure Boot certificates expired?
No. Microsoft states devices without the 2023 certificates continue to start and operate normally, and standard updates keep installing. The gap is only that early-boot security protections stop advancing until the device catches up via Windows Update.
My PC is offline most of the time — is it at risk?
It is in the main affected group: an offline machine may never have received the 2023 certificates. The exposure is modest for a machine that never touches untrusted networks or files, and one Windows Update session whenever it does go online closes the gap.
Does Secure Boot matter when buying a Windows 11 key?
Yes — Secure Boot (with TPM 2.0) is part of the Windows 11 hardware requirement, and the activation check is separate from it. If your PC passes, a matching key from our Windows 11 Pro listing activates the same day; the upgrade walkthrough in our buying guide starts with this exact check.
I dual-boot Linux — is anything different for me?
The third-party side of the chain (Microsoft UEFI CA 2011, expired June 27, 2026) is what signs many Linux bootloaders and tools like VeraCrypt. Moving to the 2023 certificates involves the KEK and option-ROM updates, so follow your distribution’s and vendor’s guidance before changing anything — do not treat this as a routine Windows Update.
External References
- Microsoft Support — Windows Secure Boot certificate expiration and CA updates (KB5062710)
- Windows IT Pro Blog — Act now: Secure Boot certificates expire in June 2026
- Microsoft Learn — Windows Secure Boot key creation and management guidance
- Microsoft Support — KB5025885: Windows Boot Manager revocations (CVE-2023-24932)
- Microsoft Learn — What is Secure Boot for Windows
Written by the KeyStarter Editorial Team, with AI-assisted research; sources verified and linked above.