Windows 11 Hotpatch PCs Need Restarts in September and October

Windows 11 hotpatch devices will require a restart when installing the September 2026 security update, Microsoft has confirmed.

The change appears in Message Center advisory MC1462918 and temporarily removes one of hotpatching’s main advantages.

September hotpatch update requires a restart

Microsoft says the September security update includes security features for Windows components that cannot take effect without restarting the device.

Hotpatching normally allows organizations to install many security updates without rebooting PCs, helping reduce downtime.

The September update will break that pattern temporarily, but Microsoft says devices will remain enrolled in hotpatching after the restart.

The company is not changing the configuration of the hotpatching service itself.

The restart requirement applies to enterprise devices enrolled in Windows Autopatch, Windows 11 hotpatch, or Windows Server hotpatch.

Devices that do not use hotpatching will not see any change related to this requirement.

October will require another restart

Hotpatch devices will also need a restart for the October 2026 security update.

October is a quarterly baseline month, and baseline updates normally require a reboot. Microsoft expects regular reboot-free hotpatch updates to resume in November 2026.

That means organizations using hotpatching will face restart requirements for two consecutive monthly security updates.

What IT admins should do

Microsoft recommends that IT administrators inform affected users about the temporary restart requirement before deploying the September update.

Admins should also review maintenance windows and monitor deployments once the security update starts rolling out.

The change could create additional disruption for organizations that adopted hotpatching specifically to limit downtime and reduce the number of required restarts.

In other Windows 11 news, Microsoft confirmed that KB5120998 has mouse cursor problems. The company also confirmed that KB5121003 crashes are caused by RGB software rather than the update itself.

Via Neowin