Microsoft Confirms Extra Reboot in Windows 11 KB5083631 Update

Microsoft has released Windows 11 KB5083631 for versions 24H2 and 25H2, and some users may notice their systems restarting more than once during installation. This behavior may look unusual, but it is expected and not caused by a bug.

The company clarified that the extra restart happens as part of a security-related process, not due to an issue with the update itself.

Why KB5083631 may restart your PC twice

The additional reboot is tied to the deployment of updated Secure Boot certificates. Microsoft is rolling out newer certificates as part of a broader initiative to refresh the Secure Boot infrastructure across Windows devices.

During the update process, certain systems need an extra restart to properly apply these new security components. This ensures that the updated certificates integrate correctly into the system’s boot process.

Secure Boot changes explained

Secure Boot plays a critical role in protecting systems from low-level threats such as bootkits. These attacks target the startup process before the operating system fully loads, making them difficult to detect and remove.

The original Secure Boot keys used across many systems are now approaching their expiration window, roughly 15 years after their introduction. Many of these keys are set to expire around 2026.

To avoid disruptions and maintain system trust, Microsoft has started deploying updated certificates issued in 2023. These new keys ensure that devices continue to verify trusted software during startup without interruptions.

Limited impact, expected behavior

Not all systems will experience the additional restart. Microsoft notes that only a limited number of devices require this extra step, depending on their current configuration and certificate state.

For affected users, the system may reboot once more than usual during the update process. After that, the installation continues normally without further issues.

Part of a broader rollout

This is not the first time Microsoft has introduced this behavior. A similar pattern appeared in a previous update, KB5083769, which also included Secure Boot-related changes.

The approach reflects a longer-term effort to strengthen platform security while preparing systems for upcoming certificate transitions.

Focus on long-term protection

Although multiple restarts can seem unexpected, the behavior serves a clear purpose. By updating Secure Boot certificates now, Microsoft ensures that Windows systems remain protected against evolving threats and continue operating securely beyond the current certificate lifecycle.

Overall, the extra reboot in KB5083631 is intentional, limited in scope, and part of a wider push to maintain system integrity and security.

Via Neowin