Microsoft confirms Windows 11 may restart multiple times after updates and your PC isn’t broken, as it’s due to Secure Boot 2023
May 5, 2026
Upon installing the April 2026 Patch Tuesday update, the experience was anything but swift. My PC underwent two reboots and spent over 20 minutes finalizing the update. A moment of panic struck as I pondered the possibility of a corrupted Windows 11 installation. However, this was not a malfunction; rather, it was an expected behavior acknowledged by Microsoft, attributed to the Secure Boot process.
Ordinarily, Windows updates are designed to complete with a single reboot, a standard that holds true for all monthly updates, including those optional updates released in the fourth week. It is only during annual feature updates that multiple reboots become necessary. Therefore, encountering multiple reboots is uncommon unless there are pending driver updates or firmware/BIOS updates.
Recently, however, both Windows Latest and numerous users have reported experiencing two or even three reboots following monthly updates. Microsoft clarified that this is intentional, as the system attempts to install the Secure Boot 2023 certificates. An updated support document revealed that a select number of computers may reboot more than once to successfully apply these certificates.
Microsoft elaborated, stating, “With recent and upcoming Windows updates over the next few months, a limited number of consumer and business devices might experience one additional restart during installation. This one-time restart occurs after a Secure Boot certificate update is applied as part of the Secure Boot update process.” The rollout of this update coincided with Windows 11’s April 2026 updates, including the optional update released on April 30. For context, the Secure Boot 2023 certificates are set to replace older certificates issued in 2011, which will expire in June 2026.
Microsoft is now exposing Secure Boot status via the Windows Security app
If your PC has undergone two or more reboots and you’re uncertain whether it pertains to a Secure Boot certificate, you can easily check its status through the Windows Security app. This information is accessible under the Secure Boot section within the Device Security tab in Windows Settings. The Secure Boot status is indicated by three badges: green, yellow, and red.
For most PCs equipped with updated BIOS or firmware, a green check mark signifies that the system is in good standing, requiring no further action. I, too, have received the green badge, confirming that my Secure Boot certificates are up to date. However, it’s crucial not to assume that Secure Boot is functioning properly solely based on the green badge. It must also indicate, “Secure Boot is on and all required certificate updates have been applied.”
In cases where the status is less favorable, a yellow warning badge suggests that Windows is still operating with the older boot trust configuration, with an expectation that Windows Update will automatically apply the newer certificate. In the most concerning scenario, a red badge signals that Windows requires your intervention, as it is unable to install the newer certificates.
The Secure Boot section showing the “Not yet updated” status with a yellow warning icon.The Secure Boot section showing the “Requires action” status with a red stop icon.
Microsoft has expressed its commitment to managing Secure Boot certificates on modern PCs. However, users with older machines lacking OEM support may find themselves unable to receive the necessary Secure Boot certificate updates. These updates still hinge on having an updated BIOS or firmware; without it, Windows Update may falter.
Our investigation has uncovered that Secure Boot certificate failures are prevalent among thousands of older PCs due to firmware limitations, potentially explaining why some systems have yet to receive the update. Microsoft is actively working to distribute the certificate to as many PCs as possible. Still, if it remains absent and the Security app displays a red warning, only your OEM can provide assistance.
What about your experience? Is Secure Boot functioning correctly on your PC? Feel free to share your thoughts in the comments below.
Microsoft confirms Windows 11 may restart multiple times after updates and your PC isn’t broken, as it’s due to Secure Boot 2023
Upon installing the April 2026 Patch Tuesday update, the experience was anything but swift. My PC underwent two reboots and spent over 20 minutes finalizing the update. A moment of panic struck as I pondered the possibility of a corrupted Windows 11 installation. However, this was not a malfunction; rather, it was an expected behavior acknowledged by Microsoft, attributed to the Secure Boot process.
Ordinarily, Windows updates are designed to complete with a single reboot, a standard that holds true for all monthly updates, including those optional updates released in the fourth week. It is only during annual feature updates that multiple reboots become necessary. Therefore, encountering multiple reboots is uncommon unless there are pending driver updates or firmware/BIOS updates.
Recently, however, both Windows Latest and numerous users have reported experiencing two or even three reboots following monthly updates. Microsoft clarified that this is intentional, as the system attempts to install the Secure Boot 2023 certificates. An updated support document revealed that a select number of computers may reboot more than once to successfully apply these certificates.
Microsoft elaborated, stating, “With recent and upcoming Windows updates over the next few months, a limited number of consumer and business devices might experience one additional restart during installation. This one-time restart occurs after a Secure Boot certificate update is applied as part of the Secure Boot update process.” The rollout of this update coincided with Windows 11’s April 2026 updates, including the optional update released on April 30. For context, the Secure Boot 2023 certificates are set to replace older certificates issued in 2011, which will expire in June 2026.
Microsoft is now exposing Secure Boot status via the Windows Security app
If your PC has undergone two or more reboots and you’re uncertain whether it pertains to a Secure Boot certificate, you can easily check its status through the Windows Security app. This information is accessible under the Secure Boot section within the Device Security tab in Windows Settings. The Secure Boot status is indicated by three badges: green, yellow, and red.
For most PCs equipped with updated BIOS or firmware, a green check mark signifies that the system is in good standing, requiring no further action. I, too, have received the green badge, confirming that my Secure Boot certificates are up to date. However, it’s crucial not to assume that Secure Boot is functioning properly solely based on the green badge. It must also indicate, “Secure Boot is on and all required certificate updates have been applied.”
In cases where the status is less favorable, a yellow warning badge suggests that Windows is still operating with the older boot trust configuration, with an expectation that Windows Update will automatically apply the newer certificate. In the most concerning scenario, a red badge signals that Windows requires your intervention, as it is unable to install the newer certificates.
Microsoft has expressed its commitment to managing Secure Boot certificates on modern PCs. However, users with older machines lacking OEM support may find themselves unable to receive the necessary Secure Boot certificate updates. These updates still hinge on having an updated BIOS or firmware; without it, Windows Update may falter.
Our investigation has uncovered that Secure Boot certificate failures are prevalent among thousands of older PCs due to firmware limitations, potentially explaining why some systems have yet to receive the update. Microsoft is actively working to distribute the certificate to as many PCs as possible. Still, if it remains absent and the Security app displays a red warning, only your OEM can provide assistance.
What about your experience? Is Secure Boot functioning correctly on your PC? Feel free to share your thoughts in the comments below.