Event banner
Event details
Hi, is there any plan to also support Server 2022 for Arc enabled servers?
thks
saksh1030Microsoft
For Azure Arc connected servers, hotpatching is only applicable for Server 2025 and there is no ongoing plan to support Server 2022.
1. Is windows 2024 ltsc supported ? In my company mainly these computers are mission critical, it would be good if they did not have to be rebooted ?
2. Are there plans for on premises for server 2022 and lower ?
3.Will VBS work without device guard feature enabled ?- David_Callaghan
1) Yes. Windows 11 version 24H2 LTSC supported.
2) Currently on prem is Server 2025.
3) VBS can function independently of Device Guard in 24H2. The minimum requirement for hotpatch is VBS.
How do the .NET CU's work with hotpatching. It is very frequent that these updates require reboots? Also there are some tools and features that require the latest CU for them to work properly. Does this mean we will be forced to defer these updates until the next baseline? Will this not cause more issues? Or will we receiving these updates anyways and be forced to reboot. This also applied to driver updates that uses are running on a monthly basis.
- Nevine_Geissa
.NET updates are not covered by hotpatching. If a .NET update requires a reboot, the system will need to restart just as it would outside of hotpatching. You won’t have to wait until the next baseline—you can still install the .Net update when needed. However, a reboot may be required to complete the installation.
However, if a standard Windows Update is required for a dependency, then yes, you may need to wait until the next baseline unless you choose to install the standard update manually (which would require a reboot).
Regarding driver updates, hotpatching does not change driver update behavior. Drivers will still follow their normal update cycle, and if a driver update requires a reboot, the system will prompt for it as usual.
We understand the need to balance security with feature updates and stability. If you have specific use cases where waiting for a baseline could cause issues, we’d love to hear more about them to help improve the experience!
I use Windows Enterprise multisession image from Azure. Unfortunately, this image is not supported by Azure Update Manager. Do you know if, it will be supported?
hey vhrios do you mean Hot Patching or Azure Update Manager? I thought, but not tested yet, Win11ENT Multisession is supported by AUM...because its a "Server OS"...
- VishalBajaj
On Azure we support only published Azure Edition images for htpatching. For more details visit About Hotpatch
If you're managing your devices with Intune, use Settings Catalog to enable VBS.
Settings Catalog > Device Guard > Enable Virtualization Based Security- Heather_Poulsen
Community Manager
Thanks for joining today’s session on “The hottest way to update Windows 11 and Windows Server 2025” at Microsoft Technical Takeoff. Q&A will remain open through Friday so keep your comments and questions coming! Up next: The path ahead: The roadmap for Windows in the cloud
Here are the resources we mentioned in today’s session:- Hotpatch updates
- Release notes for hotpatch public preview on Windows 11, version 24H2 Enterprise clients
- Release notes: Windows 11, version 24H2 - December 10, 2024 - KB5048667
- December 10, 2024—Hotpatch public preview KB5048794 (OS Build 26100.2528)
- aka.ms/GetHotpatch
- Release notes for Hotpatch on Windows Server 2025 Datacenter Azure Edition
- Skilling snack: Hotpatch on Windows client and server
Nice presentation. Thank you!
- David_Callaghan
Appreciate the feedback. Hope you enjoy many patch Tuesdays in the future with no disruptions :)!
Nice job! This has the potential to improve the experience for admins and users.
- David_Callaghan
Thank you for the feedback. We're hoping this content gives you all insights and information you need to successfully deploy hotpatch updates across all your computing needs whether its Windows 11 24H2 PCs or the cloud and on prem with Azure Arc and Server 2025.
This is an outstanding Presentation!!!! Thank you!!!!
- David_Callaghan
Thanks for your feedback, I'm so glad you enjoyed the content. Wishing you a happy Patch Tuesday with no disruption next week 3B hotpatch is on the way!
Hotpatching should be for specific use-case devices, not everything.
Additionally, regarding VBS being a pre-req, any device that has been installed with Win11 22H2 or later has HVCI and VBS enabled by default. You can also enable VBS via the Settings Catalog in Intune, and it's really poor that option wasn't shown in the video at all. Just don't assign it to devices or you'll get a reboot during Autopilot.
- David_Callaghan
New Windows 11, version 24H2 PCs will have VBS enabled by default. A PC upgraded to Windows 11 24H2 will maintain the older OS's VBS config state. So be sure to check VBS status on upgraded machines or anytime you expect the device to receive the hotpatch update but it doesn't. Great feedback on using Intune to set the OS configuration settings.
So we can not use Hotpatching for example Citrix VMs, because it is not supported by Citrix Hypervisor (VBS requires nested virtualization support).
Right?- VishalBajaj
VBS does not require nested virtualization support. It can work in Guest mode too. But you will need a hypervisor that can
1) Expose Virtual Trust Levels (VTLs) interfaces (which do not exist other than HyperV) OR
2) Create a VM with nested virtualization support
There is no need to create a nested VM in the VM
