Security

Windows Secure Boot Certificate Update for June 2026

3 min read

Summary

Microsoft says the original Windows Secure Boot certificates from 2011 will begin expiring in late June 2026, and it is pushing updated certificates to supported devices through regular Windows updates, with some systems also needing OEM firmware updates first. This matters because devices that don’t receive the refresh may still boot, but they could lose access to future boot-level security protections, making this a key maintenance deadline for IT teams.

Need help with Security?Talk to an Expert

Introduction: why this matters

Secure Boot is one of Windows’ most important boot-time protections, ensuring only trusted, digitally signed components run before the OS loads. That trust is anchored in certificates stored in UEFI firmware—and Microsoft has confirmed the original Secure Boot certificates introduced in 2011 are reaching end of lifecycle and begin expiring in late June 2026. For IT teams, this is a time-bound, ecosystem-wide security maintenance event: if devices miss the certificate refresh, they may continue to boot, but they’ll lose the ability to take future boot-level protections.

What’s new

Secure Boot “root of trust” is being refreshed

  • The long-lived Secure Boot certificates are expiring starting late June 2026.
  • New certificates are being deployed to in-support Windows devices through the normal monthly Windows update cadence.
  • This is a coordinated effort across Windows servicing, OEM firmware, and UEFI providers to minimize risk and disruption.

Broad OEM readiness (especially newer devices)

  • Many PCs built since 2024—and nearly all devices shipped in 2025—already include the updated certificates.
  • For a smaller subset of in-market devices, applying the new certificates may require an OEM firmware update first.

Improved visibility and phased rollout

  • Microsoft is rolling out the change in a careful, staged approach informed by testing and telemetry-based readiness.
  • Status messaging about certificate updates is expected in the Windows Security app in the coming months to help users track progress.

Impact to IT administrators and end users

If devices don’t get the new certificates in time

  • Devices will likely continue to function and existing software will still run.
  • However, they enter a degraded security state and may be unable to receive future boot-level mitigations (e.g., when new boot vulnerabilities are discovered).
  • Over time, compatibility risks increase: newer OS/firmware/hardware or Secure Boot–dependent software may fail to load.

Unsupported Windows versions are a key risk

  • Devices on unsupported versions (notably Windows 10 after support ended on Oct 14, 2025, unless enrolled in ESU) will not receive the updates through Windows Update.
  • Those endpoints should be treated as priority remediation items (upgrade/replace or ensure ESU eligibility and update strategy).
  1. Inventory and scope
    • Identify all Windows and Windows Server endpoints in scope, including kiosks, specialized servers, and IoT/edge devices that may have atypical servicing.
  2. Validate servicing path
    • Confirm devices are receiving the latest monthly cumulative updates (Microsoft-managed where applicable).
    • Ensure diagnostic/telemetry requirements used for readiness validation align with your organization’s policies.
  3. Firmware readiness check
    • Proactively review OEM advisories and support pages (Dell/HP/Lenovo and others) and schedule required UEFI/firmware updates.
    • Pilot firmware updates on representative hardware models before broad deployment.
  4. Plan for exceptions
    • For devices not confidently validated via Microsoft’s staged approach, use the Microsoft IT administrator playbook guidance and your existing tools (Intune, Configuration Manager, or third-party) to deploy and monitor.
  5. Prepare support runbooks
    • First-line steps: apply latest Windows updates, verify latest OEM firmware, then escalate via Microsoft/OEM support channels if issues persist.

Need help with Security?

Our experts can help you implement and optimize your Microsoft solutions.

Talk to an Expert

Stay updated on Microsoft technologies

Read the original article by Nuno Costa
Secure BootUEFI firmwareWindows updatescertificate lifecycleendpoint security

Related Posts

Security

Trivy Supply Chain Compromise: Defender Guidance

Microsoft has published detection, investigation, and mitigation guidance for the March 2026 Trivy supply chain compromise that affected the Trivy binary and related GitHub Actions. The incident matters because it weaponized trusted CI/CD security tooling to steal credentials from build pipelines, cloud environments, and developer systems while appearing to run normally.

Security

AI Agent Governance: Aligning Intent for Security

Microsoft outlines a governance model for AI agents that aligns user, developer, role-based, and organizational intent. The framework helps enterprises keep agents useful, secure, and compliant by defining behavioral boundaries and a clear order of precedence when conflicts arise.

Security

Microsoft Defender Predictive Shielding Stops GPO Ransomware

Microsoft detailed a real-world ransomware case in which Defender’s predictive shielding detected malicious Group Policy Object abuse before encryption began. By hardening GPO propagation and disrupting compromised accounts, Defender blocked about 97% of attempted encryption activity and prevented any devices from being encrypted through the GPO delivery path.

Security

Microsoft Agentic AI Security Tools Unveiled at RSAC

At RSAC 2026, Microsoft introduced a broader security strategy for enterprise AI, led by Agent 365, a new control plane for governing and protecting AI agents that will reach general availability on May 1. The company also announced expanded AI risk visibility and identity protections across Defender, Entra, Purview, Intune, and new shadow AI detection tools, signaling that securing AI usage is becoming a core part of enterprise security operations as adoption accelerates.

Security

Microsoft CTI-REALM Benchmarks AI Detection Engineering

Microsoft has introduced CTI-REALM, an open-source benchmark designed to test whether AI agents can actually perform detection engineering tasks end to end, from interpreting threat intelligence reports to generating and refining KQL and Sigma detection rules. This matters because it gives security teams a more realistic way to evaluate AI for SOC operations, focusing on measurable operational outcomes across real environments instead of simple cybersecurity question answering.

Security

Microsoft Zero Trust for AI: Workshop and Architecture

Microsoft has introduced Zero Trust for AI guidance, adding an AI-focused pillar to its Zero Trust Workshop and expanding its assessment tool with new Data and Network pillars. The update matters because it gives enterprises a structured way to secure AI systems against risks like prompt injection, data poisoning, and excessive access while aligning security, IT, and business teams around nearly 700 controls.