Secure Boot Certificate Warning in Windows 11? Check the Status Before Changing BIOS

A Secure Boot certificate warning is a prompt to check your PC’s update state. Start with the exact message in Windows Security. Use it to distinguish a pending update, a compatibility hold, and a hardware or firmware limitation before deciding whether you need Windows Update, your device manufacturer, or your IT team.

Evidence and scope. Microsoft documentation was checked on 14 November 2026. CoreSecTech did not reproduce a certificate-update failure or test firmware changes. The steps below collect and interpret evidence. They do not change Secure Boot, BitLocker, or firmware settings.

Why the certificate transition matters

Microsoft lists some 2011 Secure Boot certificate expirations in June 2026 and identifies 19 October 2026 for Microsoft Windows Production PCA 2011. Affected PCs can continue to start and receive ordinary Windows updates while missing newer protections for early-boot components. A working desktop can therefore coexist with an incomplete Secure Boot certificate transition. Microsoft certificate expiration and CA updates · Microsoft’s explanation of what expiration means

A certificate-update warning alone does not establish that the PC has been compromised.

1. Record the warning and the device state

Open Windows Security → Device security → Secure Boot and record the full status text. Include the observation date, PC manufacturer and model, Windows build, firmware version, and any update error or pending restart. Note whether the device is managed by work or school. Keep serial numbers, account information, and recovery keys out of screenshots and public tickets. If the status is missing, record it as unavailable. Windows Security device security

Press Windows + R, enter msinfo32, and look for Secure Boot State. On confirms Secure Boot is enabled. Certificate completion requires separate evidence. Use the full Windows Security certificate message or the supported administrator checks below. If Secure Boot State reports Off, record it and consult the guidance for your exact device or contact IT before changing firmware settings. Microsoft guidance for devices receiving Microsoft-managed updates

2. Interpret the status before taking action

Status interpretation checked 14 November 2026. Windows Security wording can vary. Match the complete message and any recent device evidence to the applicable row.

What you seeWhat it meansSafe next step
Windows Security confirms all required updates, or System log event 1808 records completionThe required certificates were applied and the updated boot manager was installed when completion was recorded.No certificate-specific action is indicated if current evidence agrees.
Windows Security reports that updates are needed, or recent event 1801 records an incomplete updateThe required certificates and boot manager have yet to be applied to firmware. Event 1801 alone does not identify the cause.Check for an offered Windows update or pending restart. If the status persists, look for related events in the same time window.
Event 1800 reports a required restartThe update is waiting for a restart.Save your work, restart through Windows when appropriate, then recheck the status.
Windows Security reports a known-issue pause, or event 1802 describes a firmware blockMicrosoft blocked an update operation for a known device condition.Record the event’s known-issue details and follow Microsoft or manufacturer guidance for the exact model. Keep the hold in place.
Event 1795 reports a firmware error, or event 1803 reports a missing platform-key-signed Key Exchange KeyEvent 1795 identifies a firmware error during a variable update. Event 1803 identifies missing model-specific key provisioning for the KEK update.Save the full event and contact IT or the device manufacturer for a supported resolution.
Windows Security reports limited information, an unsupported automatic path, or that required boot protections can no longer be receivedThese messages call for different actions. A missing or generic badge provides too little evidence to distinguish them.Follow the linked status guidance. For a hardware limitation, contact the manufacturer. If Windows Security says required protections can no longer be received, follow Microsoft’s linked recovery guidance promptly.

Microsoft Windows Security status guidance · Secure Boot event reference

3. Read Event Viewer and registry indicators when you need more evidence

In Event Viewer → Windows Logs → System, look for the relevant TPM-WMI events. Record the event ID, timestamp, full message, and any error code or known-issue identifier. Compare events from the current update attempt. For example, an earlier 1801 followed by a later 1808 is consistent with the update completing after the incomplete state was logged. If the current Windows Security message and event history disagree, record both and escalate with the timestamps. Microsoft Secure Boot event reference

For authorized IT administrators, Microsoft’s client deployment guidance documents status values under:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecureBoot\Servicing
  • UEFICA2023Status reports NotStarted, InProgress, or Updated. Updated indicates completion of the documented deployment.
  • UEFICA2023Error holds a nonzero error code if the process encounters a fault. Correlate it with the relevant System log event. Microsoft’s inventory guidance also collects UEFICA2023ErrorEvent where available.
  • If a status value is missing, keep the result unknown unless another supported source establishes completion. WindowsUEFICA2023Capable is a reference value. Microsoft directs administrators to use UEFICA2023Status for deployment status.

Read and record these values only. Changing a status or deployment value is outside this diagnostic workflow. Microsoft registry reference · Microsoft IT guidance

4. Use the supported update and recovery path

For a personal Windows 11 PC, open Settings → Windows Update. Review offered updates, restart requests, and Update history. Back up important files and save work before restarting. After the supported update and any requested restart, revisit Windows Security and compare the full status with your earlier record. An installed update entry gives useful context. Completion comes from the certificate status or supported administrator evidence. Microsoft Windows Update FAQ

If Microsoft or your manufacturer identifies a firmware procedure for your exact model, confirm the model, current firmware, prerequisites, and power requirements. If BitLocker or Device Encryption is enabled, verify access to the correct recovery key from a trusted device before starting. Stop before firmware work if you cannot retrieve the key. Keep it private. Avoid generic fixes such as disabling Secure Boot, clearing the TPM, resetting keys, switching boot modes, or importing certificates from an unofficial script. Microsoft BitLocker recovery-key guidance · Microsoft Secure Boot troubleshooting guide

5. Escalate with the evidence that identifies the next step

For a managed PC, give IT the model, firmware version, Windows build, exact status, recent event IDs and timestamps, and the relevant update-history entry. Managed devices can show different notifications from personal PCs. Keep missing evidence separate from a confirmed incomplete update. For a fleet rollout, pilot by hardware and firmware group and check completion, normal boot, and unexpected BitLocker recovery prompts before expanding. Microsoft’s managed-device status guidance · Microsoft Windows client remediation guidance

If the issue remains open, ask support whether the exact model is on a compatibility hold, lacks a supported automatic update path, or needs a documented manufacturer procedure. Record the trigger for the next check, such as an offered update, an OEM advisory, or an IT-approved pilot. Mark the issue resolved when current evidence shows certificate-update completion.