Secure Boot Certificate Expiration 2026: How to Check Your PC and Fix It

The Secure Boot certificate expiration will not stop your Windows PC from starting or installing normal updates. The risk is quieter: a PC that never gets the newer 2023 certificates cannot receive future protections for the early boot process. Microsoft says most Windows devices get the new certificates automatically through Windows Update. Some also need a BIOS or UEFI update from the PC maker.

This guide shows how to check your PC in three ways, what to do if it is not updated, and how to fix the problems people run into. Last checked against Microsoft’s documentation on 25 October 2026.

Quick answer

  • Secure Boot checks that only trusted software runs while your PC starts.
  • Microsoft’s 2011 certificates start expiring in June 2026. All three dates in the table below have now passed.
  • A PC without the 2023 certificates still starts and still installs normal Windows updates. It stops getting new boot-level security protections.
  • Check Windows Security > Device security > Secure Boot, install all Windows updates, restart, and look for a BIOS or UEFI update if the status does not clear.

Jump to: What expires · How to check · Steps to fix · Troubleshooting · Common mistakes · Examples · FAQ

What is Secure Boot, and which certificates expire?

Secure Boot is a UEFI firmware feature. Before Windows loads, the firmware checks the digital signature of the boot software against certificates stored in the firmware. Certificates have an end date, like the ones that secure websites. Every Windows device has carried the same Microsoft certificates since Secure Boot arrived, so they reach the end of their life together. Microsoft explains the plan on its Secure Boot certificate expiration page.

Expiring certificateExpiry dateReplacementWhat it does
Microsoft Corporation KEK CA 201124 June 2026Microsoft Corporation KEK 2K CA 2023Signs updates to the DB and DBX lists
Microsoft UEFI CA 201127 June 2026Microsoft UEFI CA 2023 and Microsoft Option ROM UEFI CA 2023Signs third-party boot loaders and option ROMs
Microsoft Windows Production PCA 201119 October 2026Windows UEFI CA 2023Signs the Windows boot loader

Microsoft’s October 2026 update notes for KB5127648 say the rollout is still in progress. They also say devices that have not yet received the newer certificates keep starting and keep receiving standard Windows updates.

What happens if your PC does not get the new certificates

According to Microsoft, the PC starts and runs normally. What it loses is new protections for the early boot process: updates to Windows Boot Manager, the Secure Boot databases, revocation lists, and fixes for newly found boot-level vulnerabilities. Over time that leaves the PC less protected. Microsoft also says it may affect setups that depend on Secure Boot trust, such as BitLocker hardening or third-party boot loaders.

How to check if your PC has the new certificates

Windows does not announce when the new certificates arrive, so check yourself. Use method 1 first. Methods 2 and 3 give more detail.

Step 0: make sure Secure Boot is on

Press Windows + R, type msinfo32 and press Enter. Look for Secure Boot State. If it says Off or Unsupported, the certificate update will not apply. Microsoft’s FAQ says devices with Secure Boot turned off do not get the new certificates in firmware.

Method 1: the Windows Security app

Since April 2026, Windows Security shows the certificate status. Open Start, search for Windows Security, then go to Device security > Secure Boot. Read the full message, not just the colour. Microsoft warns that a green checkmark alone does not confirm the certificates are updated. Microsoft describes a red status as a boot security update that cannot be delivered to your current boot configuration. Details are in Microsoft’s guide to the status page.

Note: on PCs managed by an organisation, this status display is off by default. If you see nothing, ask your IT team.

Method 2: a PowerShell check

Right-click Start, open Terminal (Admin) or PowerShell (Admin), and run this one line. It only reads data and changes nothing:

([System.Text.Encoding]::ASCII.GetString((Get-SecureBootUEFI db).bytes) -match 'Windows UEFI CA 2023')

True means the Windows UEFI CA 2023 certificate is in your firmware’s allowed list. False means it is not there yet. This command is widely shared by Digital Trends and Pureinfotech, but it is not an official Microsoft tool. It also checks only one certificate. Microsoft says both the DB and the KEK need their 2023 versions, so treat True as a good sign, not a full guarantee.

Method 3: Event Viewer

Open Event Viewer, go to Windows Logs > System, choose Filter Current Log, and pick TPM-WMI as the event source. These are the events people look for:

Event IDWhat it generally means
1808The Secure Boot certificate update finished successfully
1801The update is available or still being processed. Keep updating and restarting
1803The update has started but the KEK step is not finished yet
1802A problem blocked the update. If it stays after a BIOS update, contact the PC maker
1032The update was not applied because of the current BitLocker configuration

Microsoft documents these events in its Secure Boot DB and DBX variable update events article. The 1802 and 1803 meanings above come from PC-maker support pages (ASUS and Framework), not from Microsoft’s own table, so read your maker’s notes if you see them.

What to do, step by step

  1. Install all Windows updates. Open Settings > Windows Update > Check for updates. Microsoft delivers the certificates to eligible devices through Windows Update. If updates fail, see our fix for Windows Update error 0x800f0922.
  2. Restart the PC, then check the status again. Some steps finish only after a restart, and Windows may need more than one restart.
  3. Wait a short time. Microsoft rolls the certificates out in stages, using device data to pick PCs that are ready. A yellow status can simply mean your PC is not in the current batch.
  4. Find your BitLocker recovery key before any BIOS update. If you signed in with a Microsoft account, the key is often saved there. A firmware update can trigger a recovery prompt.
  5. Look for a BIOS or UEFI update on your PC or motherboard maker’s support page, but only if Windows Update has run and the status still does not clear.

Some guides also run Windows’ built-in task by hand to avoid waiting. Pureinfotech shows Start-ScheduledTask -TaskName "\Microsoft\Windows\PI\Secure-Boot-Update" in an admin PowerShell window for this. It starts a task Windows already has, but Microsoft’s pages do not list it as a step, so this is optional. Do not edit the registry or firmware keys by hand.

Troubleshooting: common problems and fixes

ProblemLikely causeWhat to do
Status is yellow, or Event 1801 keeps appearingThe update is still in progress or your PC is waiting for its turnInstall updates, restart a few times, re-check in a few days
Status is red, or “cannot be delivered”Your current boot or firmware configuration blocks the updateCheck your PC maker’s support page for a BIOS/UEFI update. Contact support if none exists
PowerShell returns False after several restartsOld firmware may not accept the new certificateInstall the maker’s BIOS update, then re-check
Secure Boot State is OffSecure Boot disabled, or the PC is not in UEFI modeWindows must be installed in UEFI mode before Secure Boot can be turned on. Check your maker’s steps first
BitLocker asks for the recovery key after an updateFirmware or Secure Boot settings changedEnter the key. Keep a copy before future firmware updates
Event 1032 appearsThe current BitLocker setup would trigger recovery if the update ranHome users: contact the PC maker. IT admins: follow the Microsoft event article
Windows 10 PC, no Extended Security UpdatesThe certificates come through Windows Update, and non-ESU Windows 10 is not expected to get themEnrol in ESU or move to Windows 11 if the PC qualifies

BitLocker loops on some business PCs. One IT blog reported certain HP EliteDesk 800 G6 desktops asking for the recovery key on every restart after a June 2026 update, and said HP had published guidance. That is a single third-party report, so check your own maker’s support page before acting.

Still on Windows 11 24H2 Home or Pro? Microsoft says the October 2026 update was the last one for those editions. I could not find a Microsoft statement on whether certificate delivery continues to them after that. The safe move is to upgrade. See our guides on Windows 11 24H2 end of support and what to do if 26H2 is not showing.

Windows 10 PCs

The certificate change arrives through Windows Update. Reporting by Windows Central and Dark Reading says Windows 10 PCs enrolled in Extended Security Updates get the new certificates, while those outside ESU do not. Microsoft’s FAQ adds that only supported Windows versions get them. Our article on Windows 10 ESU extended to October 2027 explains what that coverage includes.

Common mistakes to avoid

  • Turning Secure Boot off. This removes the protection. It does not fix an expiring certificate, and PCs with Secure Boot off do not receive the new ones.
  • Trusting the green colour alone. Read the full message in Windows Security.
  • Resetting Secure Boot keys to default without a maker update. Microsoft’s FAQ advises against changing the Secure Boot setup unless the PC maker has released a firmware update that carries the new certificates. The reason: a reset can bring back the old certificate set.
  • Copying registry or firmware key edits from random tutorials. A wrong change can leave a PC that will not start.
  • Updating the BIOS without the BitLocker key. You may be locked out until you find it.
  • Assuming no notification means no action. Windows does not tell you when the update lands.

Practical examples

These are illustrative scenarios based on Microsoft’s documentation, not reports from real users.

  • A newer Windows 11 laptop. Windows Security shows an updated message and PowerShell returns True. Nothing to do. Dark Reading notes that PCs made in roughly the last two years often ship with the 2023 certificates already.
  • An older Windows 11 desktop with a yellow status. Install updates, restart twice, wait a few days. If the status is unchanged and PowerShell says False, look for a BIOS update from the motherboard maker. Save the BitLocker key first.
  • A Windows 10 office PC with no ESU. The status may never clear. Decide between ESU and moving to Windows 11 on supported hardware.

Business and IT-managed PCs

Organisations that manage their own updates should follow Microsoft’s Secure Boot guidance for IT instead of waiting for automatic delivery. Microsoft’s FAQ says the customer is ultimately responsible for updating the certificates where the automatic update does not apply. Pilot on a few device models first, because firmware behaviour differs between makers. Check BitLocker behaviour during the pilot.

FAQ

Will my PC stop booting when the certificate expires?

No. Microsoft says devices without the newer certificates continue to start and operate normally.

Can I still get the new certificates after the old ones expired?

Yes. Microsoft says it keeps delivering them to eligible devices through Windows Update, and ASUS states updates with the new certificates can still be applied after expiry.

Do I need to buy anything?

Most Windows 11 PCs need no purchase. Windows 10 PCs outside ESU are the main exception, because ESU is a paid programme.

Does this affect Linux dual-boot PCs?

Microsoft lists third-party boot loaders among the setups that rely on Secure Boot trust. How your distribution is affected depends on the distribution, so check its own guidance before changing anything.

Is it safe to dismiss the Windows Security warning?

You can dismiss it, but Microsoft does not recommend that if your PC has not yet received the certificates.

Official sources

Based on Microsoft’s documentation and the sources linked above, as of 25 October 2026. This is a research-based explainer, not hands-on testing, and Microsoft may change the rollout. Confirm details on your PC maker’s support page before changing firmware.

Share this post:

1 thought on “Secure Boot Certificate Expiration 2026: How to Check Your PC and Fix It”

  1. Pingback: KB5127648 (Oct 2026): Fixes, Known Issues & How to Fix Them

Leave a Comment

Your email address will not be published. Required fields are marked *

WhatsAppFacebookXLinkedInTelegram
Scroll to Top