A computer setup displays UEFI Secure Boot settings, verified certificates, and security status alongside a Windows laptop.
Secure Boot runs before Windows loads, so most people never see it. But in 2026 it hit a deadline. The Microsoft certificates that most Windows PCs have trusted since the Windows 8 era have now expired. Missing the 2023 replacements doesn't stop a PC from booting. It still starts, Patch Tuesday updates still install, and the Windows Security app may still show a green check, so nothing looks wrong.

TweakTown's guides editor Yasir Mahmood checked two of his own PCs and got two different results. His Ryzen desktop already had the new certificates from Windows Update. His HP laptop did not. Windows Update wasn't the cause. He had turned Secure Boot off months earlier to boot from a USB drive and never turned it back on. Plenty of tinkerers have probably done the same.

A computer setup displays UEFI Secure Boot settings, verified certificates, and security status alongside a Windows laptop. The deadline has passed. Here's what expired​

Secure Boot checks the signature on each piece of pre-boot code against certificates stored in the UEFI firmware. If the signature doesn't match a trusted certificate, the code doesn't run. That is how it blocks bootkits from loading underneath Windows.

Microsoft's certificate-expiration documentation (KB5062710) lists three 2011-era certificates and their replacements:

Expiring certificateExpiredReplacementWhat it does
Microsoft Corporation KEK CA 2011June 24, 2026Microsoft Corporation KEK 2K CA 2023Signs updates to the DB and DBX databases
Microsoft UEFI CA 2011June 27, 2026Microsoft UEFI CA 2023Third-party boot loaders and EFI apps
Microsoft UEFI CA 2011June 27, 2026Microsoft Option ROM UEFI CA 2023Third-party option ROMs
Microsoft Windows Production PCA 2011October 19, 2026Windows UEFI CA 2023Signs the Windows boot loader

The old UEFI CA was split in two on purpose. A system can now trust option ROMs, such as the firmware on a graphics card, without also trusting third-party boot loaders. As of this writing, all three 2011 certificates have expired.

What actually breaks? In the short term, nothing you'd notice. Microsoft's guidance for blocked devices (KB5105943) says expired-certificate PCs keep booting, keep installing feature and quality updates, and keep Secure Boot's protection against threats that are already known. What they lose:

  • New Secure Boot and Boot Manager protections can't be applied.
  • Newly discovered malicious or vulnerable boot loaders may not be blocked. That includes revocations of the kind Microsoft has used against BlackLotus-style attacks.
  • Some non-Microsoft components that depend on Microsoft's Secure Boot trust may fail to update.

Microsoft calls this a gradual reduction in long-term security, not an immediate failure. Its Windows Security FAQ adds that over time, newer operating systems, firmware, hardware or Secure Boot-dependent software may fail to load.

Section summary: Your PC won't stop booting. It will slowly stop getting protection at the boot level, and nothing on screen will make that obvious.

Check 1: Read the whole sentence in Windows Security​

The quickest check is in the Windows Security app:

  1. Open Start, type Windows Security, and open the app.
  2. Select Device security in the sidebar.
  3. Scroll to the Secure Boot section and read the text, not just the icon.

Microsoft's own support article on this feature (KB5087130) warns that a green checkmark alone doesn't prove the certificates were updated. The text you want is: "Secure Boot is on and all required certificate updates have been applied. No further certificate changes are needed."

Other messages and what they mean, per Microsoft:

  • "Secure Boot is on, but your device is using an older boot trust configuration that should be updated." Install the latest Windows updates and restart if prompted.
  • Updates "temporarily paused" because of a known issue. No action is needed. Microsoft says the update resumes on its own once the issue is fixed.
  • "Not yet enough data to classify your device." The device needs more validation before the automatic update goes ahead.
  • Hardware or firmware limitations. Contact your PC manufacturer. You may need a firmware update, and some older models may never get one.
  • "Secure Boot is off, your device may be vulnerable." This is a configuration problem rather than a certificate status. It was the message on Mahmood's HP laptop.

Two caveats. First, the expanded status display started rolling out in April 2026 and arrives gradually. Second, Microsoft turns the new Secure Boot badges and notifications off by default on enterprise-managed devices, although the status text still appears. Admins who want the badges can set HideSecureBootStates to 0.

The fix on the HP laptop: turn Secure Boot back on, carefully​

Mahmood's laptop needed a change in the firmware, so he prepared first. That step matters. Changing Secure Boot settings can trigger BitLocker recovery on the next boot. Before touching anything:

  1. Find your BitLocker recovery key and confirm where it's stored.
  2. Note your current BIOS/UEFI settings so you can undo changes.
  3. Suspend BitLocker for one reboot. From an elevated terminal, Mahmood used Suspend-BitLocker -MountPoint "C:" -RebootCount 1. 4sysops gives the command-line equivalent manage-bde -Protectors -Disable C: -RebootCount 1.

On his HP laptop, he pressed F10 during startup, went to the Security tab, opened Secure Boot Configuration, enabled Secure Boot, and saved. That menu path is specific to his HP model. Dell, Lenovo, ASUS, MSI and others put the setting in different places, so check your manual. If something won't boot afterward, he notes you can undo it by turning the same setting off again.

Back in Windows, the Secure Boot section turned green, but the message still didn't mention certificates. To speed things up, he ran the servicing task as an administrator:

Start-ScheduledTask -TaskName "\Microsoft\Windows\PI\Secure-Boot-Update"

He then restarted twice. Within about an hour, the full confirmation sentence appeared.

Why trigger the task manually? According to 4sysops, Windows maintains a scheduled task called \Microsoft\Windows\PI\Secure-Boot-Update that runs every 12 hours, and it reads the AvailableUpdates registry value under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecureBoot. Running it yourself skips the wait. The two restarts aren't superstition either. A Microsoft Q&A answer notes that twice is recommended in the Secure Boot servicing guidance.

A Microsoft Q&A answer also points out that No manual BIOS key reset is required for this process, and Secure Boot should not be disabled.

Section summary: If Secure Boot is off, Windows can't install the certificates. Turn it back on, but only after you've secured your BitLocker recovery key.

Check 2: PowerShell shows the actual certificates​

The Windows Security message is a summary. To see what's actually in the firmware, open an elevated PowerShell window and run:

Get-SecureBootUEFI -Name db -Decoded

Mahmood's version lists each certificate in the firmware's allowed database (DB) along with its expiry date. Before the fix, his laptop showed HP's own key and two Microsoft 2011 certificates. Afterward, it also listed Windows UEFI CA 2023, Microsoft UEFI CA 2023 and Microsoft Option ROM UEFI CA 2023.

If that decoded output isn't available on your build, 4sysops offers a yes/no check that works with the raw database: [System.Text.Encoding]::ASCII.GetString((Get-SecureBootUEFI db).bytes) -match 'Windows UEFI CA 2023'

To track progress, check the servicing status value:

Get-ItemProperty "HKLM:\SYSTEM\CurrentControlSet\Control\SecureBoot\Servicing" | Select-Object UEFICA2023Status

On his laptop, the value moved from NotStarted to InProgress to Updated. Enterprise tooling reports the same states. Mark Orr's Intune deployment scripts on GitHub track UEFICA2023Status (NotStarted/InProgress/Updated/Failed), so "Failed" is also possible. Both commands above only read values and change nothing.

What if it's stuck at InProgress? You're not alone. One Microsoft Q&A thread describes a system where the status remains stuck at InProgress, and the UEFI CA 2023 certificate is not present, along with recurring event 1796 and 1801 errors. In that case, 4sysops recommends checking the UEFICA2023Error value under the same Servicing key. A non-zero code there, matched against the event log, can point to a firmware restriction or a write failure.

Check 3: Event Viewer, and what 1801 really means​

To read the event log:

  1. Open Event Viewer → Windows Logs → System.
  2. Click Filter Current Log.
  3. Enter 1800,1801,1808 in the All Event IDs field.

Here's how Microsoft's event reference (KB5016061) describes each one:

  • Event 1808 (informational): You're done. All required certificates are in the firmware, and the boot manager signed by Windows UEFI CA 2023 is installed. This is the event Mahmood saw after his fix.
  • Event 1800: A Secure Boot update in this boot cycle could conflict with a recent change, such as a boot manager update or virtualization-based security. A restart clears the condition.
  • Event 1801 (error): The updated certificates and boot manager haven't been applied to the firmware yet. The event includes device attributes and a bucket ID that help admins identify which devices still need updating.

Here our reading differs from TweakTown's. Mahmood says 1801 "only means the update started and needs a restart." That may be what happened on his laptop. Microsoft, however, defines 1801 as "not yet applied," not "needs a restart," and the Q&A thread above shows 1801 can keep appearing on a stuck device. If 1801 is still logged after several restarts and there is no 1808, treat it as unfinished work. Look for 1802, which means Microsoft blocked the update on purpose because of a known firmware issue, or 1803, which means no OEM-signed KEK was found for your model. Both point to your PC maker.

Who should check, and who should leave it alone​

The whole check takes a couple of minutes. It's most worth doing on:

  • PCs where someone has changed BIOS settings. A Mindcore Techblog deployment guide lists the case where Secure Boot is disabled as one where Updates cannot apply.
  • Older machines, where Microsoft's troubleshooting guidance says to install OEM firmware updates first.
  • Dual-boot and Linux setups, which depend on the third-party UEFI CA chain.
  • Business fleets, where Microsoft recommends piloting across different OEMs, firmware versions and BitLocker-enabled devices. Its listed deployment methods are Intune, registry keys, CSP and Group Policy.

There's also a counterpoint. If Windows Security says your device is paused or blocked by a firmware limitation, don't force it. Microsoft's troubleshooting page lists BitLocker recovery loops, startup hangs and failure to boot as higher-risk outcomes on outdated firmware. Third-party "force the update" scripts exist, but forcing the update on firmware Microsoft has flagged is how a security fix turns into a trip to the recovery menu. Microsoft is also clear that turning Secure Boot off to avoid the problem is worse than leaving an expired configuration in place.

The bottom line​

Mahmood's headline is fair for his laptop: Windows Update wasn't the problem, his own BIOS change was. That doesn't apply to every PC, though. Microsoft says most PCs get the certificates automatically, while some are waiting on OEM firmware or are blocked by known issues.

So don't take a green check as proof. Read the full Secure Boot sentence in Windows Security, confirm UEFICA2023Status says Updated, and look for event 1808. If all three line up, you're set. If they don't, the message on screen tells you whether to wait, restart, update your firmware, or turn Secure Boot back on.

While you're on the Device security page, it's also worth checking that Core isolation and Memory integrity are enabled.

 

References

  1. My PC missed Microsoft's new Secure Boot certificates, and Windows Update wasn't the problem - TweakTown TweakTown 2026-10-31T15:55:02+00:00
  2. Update Windows Secure Boot DB certificates with Group Policy and PowerShell 4sysops.com
  3. Secure Boot github.com