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

Secure BootUEFI firmwareWindows updatescertificate lifecycleendpoint security

Related Posts

Security

Microsoft Sentinel Named a 2026 SIEM Leader

Microsoft has been named a Leader in the 2026 Gartner Magic Quadrant for SIEM, highlighting the continued momentum behind Microsoft Sentinel. The announcement also underscores Microsoft's push toward integrated, AI-powered security operations through deep Sentinel integration with the new Integrated Security Operations Center in Microsoft Defender.

Security

Microsoft Perception GA: Agentic Security at Ignite

Microsoft has made Microsoft Perception generally available, introducing an agentic security platform that coordinates red, blue, and green team agents through automated playbooks. Announced at Ignite 2026, the update also expands Defender and Sentinel capabilities to help security teams detect, investigate, and remediate AI-speed threats while keeping administrators in control.

Security

Device Code Phishing Risks for AI Coding Agents

Microsoft warns that device code phishing can be used against AI coding agents such as GitHub Copilot CLI, not just user mailboxes or cloud apps. In a controlled lab, a single approved device code sign-in could enable remote session steering, memory poisoning, synced session exposure, and private repository access depending on account permissions and enabled features.

Security

Microsoft 365 Outage Phishing Campaign Targets Users

Microsoft Threat Intelligence reported a high-volume phishing campaign that impersonates Microsoft 365 service-health notifications to trick users into clicking malicious links. The campaign matters because it uses outage-themed urgency and recipient-specific tracking to target multiple industries, increasing the risk of credential theft and follow-on account compromise.

Security

SCKit ScreenConnect Attack: MSPs Must Hunt Now

Microsoft Threat Intelligence confirmed a campaign abusing ConnectWise ScreenConnect to deploy unauthorized remote-access clients and the SCKit worm on MSP-managed endpoints. The activity can also target technician sessions, making this a high-priority incident for defenders because removing a rogue client alone does not eliminate persistence or invalidate exposed sessions.

Security

AI Agent Supply Chain Attacks Target Coding Tools

Microsoft Security researchers detailed two post-training supply chain attack paths that can backdoor coding and terminal agents: dataset poisoning and model poisoning. The findings matter because compromised agents can misuse tools, execute commands, and access sensitive environments even when prompts appear benign, reinforcing the need for stronger controls around training data, model provenance, and tool permissions.