Secure Boot Certificates Are Expiring: How to Use the New Windows Warning Correctly | 2026 Update Guide

If you've spotted a small but noticeable notice in your Windows settings over the past few days – you're not alone. Microsoft is tightening the screws, but thankfully in a helpful way. It's about the often misunderstood Secure Boot. More precisely: the certificates that tell your PC which drivers and bootloaders are trustworthy. These certificates have an expiration date, and for many systems, that date is now dangerously close. If you don't act in time, you could suddenly be staring at a black screen – or worse: a PC that refuses to start Windows.

Why is Windows suddenly warning so loudly?

In the past, you'd only get critical notices like this hidden in the Event log, or not at all. With the latest updates (which are now pretty much mandatory for Windows 11 and 10), Microsoft is changing the game. The system now proactively tells you: "Hey, your Secure Boot certificates need attention." The message doesn't appear as an annoying pop-up ad, but is neatly integrated into the Windows Security Center. It sounds like a small thing, but it's actually a huge step. Because many users didn't even know whether their Secure Boot was active at all – let alone that the underlying keys become invalid after a few years.

The certificates that Microsoft has been shipping since Windows 8 are approaching their end of life. Specifically: older Secure Boot databases (the so-called "db" and "KEK" entries) will no longer be valid after a certain date. Your computer would then block foreign bootloaders or updated hardware drivers – and worst of all, right after a major Windows update. So the new warning is your lifeline. It appears before disaster strikes and gives you a clear Secure Boot Guide instruction: "Update your BIOS/UEFI now or install the latest cumulative update."

How to run a Secure Boot review on your PC

Don't want to wait for the automatic warning? No problem. A manual Secure Boot review is quick and easy. Follow this checklist to make sure your system boots cleanly even after the certificates expire:

• Open System Information: Press Win + R, type msinfo32 and confirm. Under "Secure Boot State", it must say "On". If it says "Off" or "Supported but disabled", boot into the UEFI-BIOS (usually by pressing F2 or Delete during startup) and enable the option.
• Check Windows Update: Go to "Settings" > "Windows Update" > "Advanced options" > "Optional updates". There you'll often find separate firmware updates that contain exactly these certificate renewals. Install anything that sounds like "Secure Boot" or "UEFI revocation".
• Use manufacturer tools: Dell, Lenovo, HP and others offer their own update assistants. Download the latest BIOS/UEFI image – many devices from 2020 or 2021 already have the extended certificates on board. For older models (2016–2019), you should pay especially close attention.

After a restart, repeat the check in msinfo32. If the status still says "On" and no warning message appears anymore, you're safe. However, if an error message appears (e.g., "Secure Boot revocation failed"), a manual reset of the Secure Boot keys to factory defaults often helps – you'll find that in the UEFI menu under "Secure Boot > Reset to Setup Mode".

How to use Secure Boot properly – without panic

Many people ask: "Do I really need to learn how to use Secure Boot? Isn't regular Windows Defender enough?" Short answer: No. Secure Boot is your first line of defense against rootkits and bootkits – that is, malware that loads before the operating system. Even if you accidentally insert an infected USB stick, a properly configured Secure Boot will prevent the malware from taking over your boot process. Microsoft's new warning policy doesn't force you to do complicated tasks, but gives you a friendly kick in the pants: "Just do it now."

For power users who dual-boot with Linux or other operating systems, the expiration of certificates can be annoying. In that case, you'll either need to manually add the new Microsoft keys to your own Secure Boot database (keyword: mokutil under Linux) or temporarily disable Secure Boot – though I only recommend that as a temporary solution. The clean way is: switch to a current distribution that already signs the fresh Microsoft certificates (Ubuntu 24.04 LTS or Fedora 40+ do this automatically).

One thing is clear: the era of silent certificate expirations is over. Microsoft has finally understood that security shouldn't be a hidden expert discipline. If you see the yellow info box in your Windows settings in the coming weeks, don't ignore it. Open it, click "Show details" and follow the wizard. In most cases, a single restart followed by an update is all it takes. Your future self – who won't suddenly be facing a non-booting PC – will thank you for it.