Secure Boot Certificates Are Expiring: How to Use the New Windows Warning Properly | 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 all about the often misunderstood Secure Boot. More precisely: the certificates that tell your PC which drivers and bootloaders are trustworthy. These certificates have an expiry date, and for many systems that date is now dangerously close. If you don't act in time, you could suddenly be facing a black screen – or worse: a PC that refuses to start Windows.

Why is Windows suddenly so vocal about this?

In the past, you'd only get such critical warnings 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 rules of 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 advert, but is neatly integrated into the Windows Security Centre. It might sound like a small thing, but it's actually a huge step forward. Because until now, many users didn't even know whether their Secure Boot was active – let alone that the underlying keys become invalid after a few years.

The certificates that Microsoft has been shipping since Windows 8 are nearing the end of their 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 in the worst case, 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 to do. Follow this checklist to make sure your system still boots cleanly 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", restart into the UEFI-BIOS (usually by pressing F2 or Del 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 onwards already have the extended certificates on board. For older models (2016–2019), you should pay particularly close attention.

After a reboot, repeat the check in msinfo32. If the status still says "On" and no warning message appears, you're safe. However, if an error message does appear (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 the regular Windows Defender enough?" Short answer: No. Secure Boot is your first line of defence against rootkits and bootkits – that is, malware that loads even before the operating system. Even if you accidentally plug in an infected USB stick, a properly configured Secure Boot will prevent the malware from taking over your boot process. Microsoft's new warning policy isn't forcing you to perform complicated actions, but rather gives you a friendly kick up the backside: "Just do it now."

For power users who dual-boot with Linux or other operating systems, the certificate expiry can be annoying, though. In that case, you'll either need to manually add the new Microsoft keys to your own Secure Boot database (using mokutil under Linux) or temporarily disable Secure Boot – but I only recommend that as a temporary solution. The clean way is: switch to a current distribution that already signs with 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 over the next few weeks, don't ignore it. Open it, click on "Show details" and follow the wizard. In most cases, a single reboot followed by an update is all it takes. Your future self – the one who won't suddenly be facing a non-booting PC – will thank you for it.