UEFI

Winsage
August 15, 2026
Windows 11 requires a compatible 64-bit processor with a minimum speed of 1 GHz and at least two cores, 4GB of RAM, and 64GB of available storage. The system must use UEFI firmware with Secure Boot capability, support Trusted Platform Module (TPM) 2.0, and have graphics hardware compatible with DirectX 12 or later with a WDDM 2.0 driver. A high-definition display with a resolution of at least 720p, measuring more than 9 inches diagonally, and supporting 8 bits per color channel is also necessary. Microsoft provides the PC Health Check app to assess compatibility with Windows 11. If a PC cannot upgrade, users can enroll in the Consumer Extended Security Updates (ESU) program for Windows 10 version 22H2, which extends security updates until October 12, 2027, without introducing new features. Enrollment options include syncing settings for free, redeeming 1,000 Microsoft Rewards points, or paying a fee, with a license applicable to up to 10 devices.
Winsage
August 15, 2026
In 2026, Microsoft Windows 11 requires specific hardware criteria for installation, including a 64-bit processor (1 GHz or faster with at least two cores), a minimum of 4GB of RAM, at least 64GB of available storage, UEFI firmware with Secure Boot, TPM version 2.0 support, and graphics hardware that supports DirectX 12 or later with a WDDM 2.0 driver. A high-definition display with a resolution of at least 720p and a diagonal measurement exceeding 9 inches is also necessary. Compatibility can be checked using the PC Health Check app, which may take up to 24 hours to reflect recent hardware upgrades. For Windows 10 users unable to upgrade, the Consumer Extended Security Updates (ESU) program provides security updates until October 12, 2027, without new features. Enrollment options include syncing settings for free, using Microsoft Rewards points, or paying a fee, with each license applicable to up to 10 devices.
Winsage
July 29, 2026
Microsoft reassured Windows 11 and Windows 10 users that their PCs will continue to boot normally and receive updates even if they have not yet received the new Secure Boot 2023 certificates. The rollout of these certificates is expected to continue over the upcoming months. The initial Secure Boot certificate expired on June 24, 2026, and Microsoft has been replacing older 2011 certificates since 2024. The latest update, KB5101650, transitioned Windows 11 to OS builds 26200.8875 and 26100.8875 for versions 25H2 and 24H2, respectively. The 2023 certificates replace older certificates with modern cryptographic standards, allowing Microsoft to deliver DBX revocation updates without interruption. Devices using the 2011 KEK can only receive DBX updates signed with that key, which is no longer valid after June 24. Microsoft has been rolling out the 2023 certificates for the past two years, and many devices remained in a yellow or red status by the June deadline. To check Secure Boot status, users can navigate to Windows Security > Device Security. A green checkmark indicates successful application of the certificates, while yellow and red alerts indicate compatibility issues or firmware incompatibility. PCs that are older or operating in Legacy BIOS mode will not receive the updates. Windows 10 also receives Secure Boot updates, but enrollment in Extended Security Updates (ESU) is required.
Winsage
July 20, 2026
Microsoft is set to release Windows 11 version 26H2, an enablement package based on version 25H2, without introducing new features at launch. The update will require only a single restart for devices on versions 25H2 or 24H2, while users on older versions, such as 23H2 or Windows 10, will need a full feature update. Both versions share identical features and are built on the same platform, with version 26H2 using build numbers in the 26300 series. The update process will vary depending on the current version, and version 26H2 will not change hardware requirements. Microsoft plans a gradual rollout of the update, initially as an optional install. Version 26H2 aims to extend support, adding approximately a year to the support timeline, with version 25H2 support continuing until October 2027. Users should verify their current version and back up important files before upgrading.
Winsage
July 19, 2026
Microsoft is set to launch the 2026 Update for Windows 11, known as version 26H2, later this year. This will be the fifth feature update for the operating system. The upgrade from version 25H2 to 26H2 will utilize an Enablement Package (eKB), allowing for a transition similar to a standard monthly cumulative update without requiring a full reinstallation. Users can also upgrade from Windows 10 using an ISO file or Microsoft installation media, which ensures files, applications, and settings remain intact. Upgrading to version 26H2 extends the support lifecycle of devices by an additional year, with Microsoft providing 24 months of support for Home and Pro editions and 36 months for Enterprise and Education editions. Version 25H2 will continue to receive support until October 2027, and users are advised to plan upgrades before this support ends. Windows 11 version 26H2 has the same hardware requirements as version 25H2, which include a 1GHz processor with at least two cores, 4GB of RAM, 64GB of storage, UEFI firmware with Secure Boot, TPM version 2.0, DirectX 12 compatible graphics, and a high-definition display. The rollout of the update will be gradual, following a Controlled Feature Rollout (CFR) strategy, meaning not all devices will receive the update immediately.
Winsage
July 18, 2026
Microsoft held its OEM Secure Boot Office Hours event on July 15, where engineers collaborated with OEM representatives from companies like Acer, Asus, Cisco, Dell, and HP. IT administrators were able to ask live questions about the Secure Boot 2023 rollout. The discussion thread became a detailed technical record, especially following the expiration of the first certificates three weeks prior. Concerns raised by IT admins included BitLocker recovery loops, stuck confidence ratings, and unhelpful Intune error codes. Key facts include: - Devices offline for long periods will still receive the 2023 certificates upon reconnecting to Windows Update. - Devices with existing 2023 certificates in firmware will switch to the new boot manager after the latest Windows patches are installed. - A new script, Detect-SecureBootCertUpdateStatus.ps1, is available in Windows for checking certificate status. - BIOS updates may reset a device’s confidence rating to unrated, which is normal and does not indicate certificate failure. - Admins should edit the AvailableUpdates registry key, not the AvailableUpdatesPolicy, which is managed by Intune and Group Policy. - A licensing bug affecting AvailableUpdatesPolicy on devices upgraded from Pro to Enterprise was resolved by Microsoft in 2026. - BitLocker recovery is not typically linked to the certificate update process but may relate to firmware or PCR issues. - Dell and HP provided guidance on which BIOS versions include the 2023 certificates for their newer models. - Older HP EliteBook 840 G5 units require a manual update package for the new certificates. - Eligible devices can still receive the 2023 certificates in the future, and Surface devices released from 2024 onward come pre-equipped with them. - Microsoft confirmed that devices running 2011 certificates will not lose the ability to receive the 2023 chain. - The Microsoft Corporation KEK CA 2011 and Microsoft UEFI CA 2011 certificates have expired, with the Microsoft Windows Production PCA 2011 set to expire on October 19, 2026.
Winsage
July 10, 2026
Microsoft has acknowledged that some Windows 11 PCs are facing issues with Secure Boot certificate updates, which may fail to install or be blocked. The company is working with PC manufacturers to develop a patch, while users may need to take proactive measures if their certificates are obstructed. Microsoft has temporarily halted the rollout of Secure Boot for certain devices due to complications, and affected users will receive detailed error messages in the Windows Security app regarding their Secure Boot certificates. Secure Boot certificates issued in 2011 have expired, and Microsoft is replacing them with new certificates issued in 2023. Most modern hardware is already utilizing the new certificates, but some devices may have disabled Secure Boot or faulty firmware. Users can check their Secure Boot status in the Windows Security app. HP has confirmed that Secure Boot updates are being blocked on some of its PCs due to a BitLocker issue, which prevents the installation of new certificates. Microsoft has paused Secure Boot certificate updates for devices affected by known issues while collaborating with manufacturers to identify specific devices or firmware complications. A firmware update will be necessary for affected devices, but it is not yet available. The majority of PCs have received the Secure Boot certificates via Windows Update, but compatibility issues may prevent some devices from receiving the update. Older devices or those not among the OEM’s top-selling models may not receive updates if the UEFI firmware is unsupported. Secure Boot is a security feature required for Windows 11, preventing unauthorized software from executing at boot. While an expired Secure Boot certificate does not stop a PC from functioning, it may limit long-term security protection. Microsoft advises users not to disable Secure Boot, as it would compromise security further.
Winsage
July 4, 2026
Windows 11 allows users to limit RAM usage through the System Configuration tool (msconfig) for testing and troubleshooting purposes. Users can specify the maximum memory in megabytes, but there is no simple option to set a fixed amount like "4GB of RAM." Limiting RAM can degrade performance and may cause applications to become sluggish. To limit RAM, users must navigate to the Boot tab in msconfig, check the Maximum memory option, and enter the desired amount. To restore full RAM access, users need to uncheck the Maximum memory option in the same tool. On some modern systems with UEFI firmware and Secure Boot enabled, the Maximum memory setting may not be accessible, and disabling Secure Boot may be necessary to apply the limit. Disabling Secure Boot can reduce security against boot-level malware.
Search