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

AI Memory Security in Microsoft 365 Explained

Microsoft has outlined how it secures AI memory in Microsoft 365, addressing emerging risks such as memory poisoning and delayed tool execution. The update matters because persistent AI memory can improve personalization and agent performance, but it also creates new security, compliance, and audit requirements for IT and security teams.

Security

Parallel Threat Activity: Microsoft DART Findings

Microsoft Incident Response detailed a complex intrusion in which two unrelated threat actors operated simultaneously in the same environment, complicating attribution and detection. The case highlights how ransomware activity, SharePoint exploitation, trusted tool abuse, and identity compromise can overlap across hybrid estates, reinforcing the need for strong telemetry, patching, and coordinated response.

Security

AutoJack RCE in AutoGen Studio: Security Lessons

Microsoft security researchers detailed AutoJack, an exploit chain in AutoGen Studio that could let untrusted web content rendered by an AI browsing agent trigger remote code execution on the host. Although the vulnerable MCP WebSocket surface was never shipped in a PyPI release and the issue was hardened upstream during development, the findings highlight important security risks for agent frameworks that combine web browsing with privileged local services.

Security

Microsoft Security Forrester Study Reports 124% ROI

A new Forrester Total Economic Impact study found that organizations consolidating on Microsoft Security could see a projected 124% ROI over three years. The report highlights lower breach risk, reduced remediation costs, lower technology spend, and productivity gains as key reasons unified security platforms matter in the AI era.

Security

Mastra npm Supply Chain Attack: What IT Teams Need to Know

Microsoft has detailed a large-scale npm supply chain compromise affecting more than 140 Mastra packages after an attacker took over a maintainer account and injected a malicious dependency. The attack is significant because the payload executed during npm install, putting developer workstations and CI/CD pipelines at risk even if the package was never directly used in code.

Security

Crypto Clipper Malware Uses Tor and USB Worm Spread

Microsoft has detailed a Windows-based crypto clipper campaign that uses malicious shortcut files, a bundled Tor client, and worm-like USB propagation to steal wallet data and maintain persistence. The threat matters because it combines clipboard theft, screenshot exfiltration, and remote code execution with stealthy Tor-based command and control, making behavioral detection critical for defenders.