The expiration of Secure Boot certificates in June 2026 poses a significant security risk for many Windows users, especially those on older hardware. This issue raises an important question: how will this expiration affect your system’s security?
Secure Boot has been a fundamental security feature for Windows for the past 15 years. It ensures that only trusted software runs during the boot process, protecting against various malware attacks. However, as the clock ticks down to June 2026, users must prepare for potential vulnerabilities.
That context matters because approximately 400 million Windows 10 PCs could be locked out of Windows 11 due to strict hardware requirements, including TPM 2.0 and Secure Boot. While Windows 11 users on modern hardware should be fine regarding certificate updates, those on older systems may face significant risks as the expiration date approaches.
Key facts:
- Secure Boot certificates are set to expire in June 2026.
- Windows 10 support officially ended in October 2025, but an Extended Security Update program is available until October 14, 2026.
- The latest Rufus update allows users to bypass Windows 11 requirements without negative effects on installation.
In the midst of these changes, issues have arisen with Rufus version 4.14. This version introduced a silent installation option that is currently broken and does not remember certain Windows User Experience settings between sessions. As noted by developer Pete Batard, “leaving the bypass options enabled has absolutely NO negative incidence or alteration with regards to the final Windows installation on systems that have a TPM.” Yet, there does seem to be some sort of issue with the WUE option to bypass system requirements not persisting.
What happens next remains uncertain. Users need to stay informed about updates related to Secure Boot and its implications. The landscape is shifting rapidly as Microsoft navigates these changes and continues to support its user base amid evolving security needs.
The next few years will be crucial for ensuring that systems remain secure and functional as we approach the critical deadline of June 2026.
