Windows 11 Enterprise machines can now get updates while you work—no reboot required

Microsoft Hotpatch Updates
(Image credit: Microsoft)

Microsoft has officially announced the release of hotpatch updates for Windows 11 Enterprise builds. This new updating protocol is currently for Enterprise 11 versions 24H2, which applies to AMD and Intel x64 devices. This isn't the first time the new hotpatching system has been mentioned, but it is the first time it's become widely available across Windows 11 Enterprise 24H2 devices.

If you're new to the hotpatching system, the biggest takeaway is the ability to apply updates without the need to restart. This is definitely ideal for corporate environments, letting users continue to work not only without the interruption caused by a reboot, but also without excessive CPU usage.

There are quarterly updates that will likely still require a reboot outside of the regular hotpatch updates. Still, this is a significant change compared to the monthly reboot requirements presently in place.

Latest Videos FromTom's Hardware
TOPICS
Ash Hill
Contributing Writer

Ash Hill is a contributing writer for Tom's Hardware with a wealth of experience in the hobby electronics, 3D printing and PCs. She manages the Pi projects of the month and much of our daily Raspberry Pi reporting while also finding the best coupons and deals on all tech.

  • Ful4n1t0c0sme
    Wow! Like GNU/Linux from 20 years ago to now!
    Reply
  • Heat_Fan89
    Ful4n1t0c0sme said:
    Wow! Like GNU/Linux from 20 years ago to now!
    Once upon a time this was common on OS X. Now you apply security updates in macOS and it sometimes becomes reboot city. Linux now has joined the club. I recently installed some system updates to Ubuntu LTS and it required a reboot.
    Reply
  • Heat_Fan89 said:
    Once upon a time this was common on OS X. Now you apply security updates in macOS and it sometimes becomes reboot city. Linux now has joined the club. I recently installed some system updates to Ubuntu LTS and it required a reboot.
    Outside the corporate server world anything that touches the kernel or a library in active use will, for the most part, always require a reboot to clean things up.
    Reply