April 28, 2025 — Microsoft introduces paid hotpatching to Windows Server 2025, marking a major change in how enterprise IT teams will handle updates. Starting July 1, 2025, the feature will transition from a free preview to a subscription model priced at $1.50 per CPU core per month for on-premises and hybrid environments connected through Azure Arc.
Previously exclusive to Azure-only workloads, hotpatching will now become a standard option for Windows Server 2025 Standard and Datacenter editions, extending a modern update mechanism to a broader customer base.
What Is Hotpatching?
Hotpatching is a breakthrough technology that allows security and critical patches to be applied without requiring a server reboot. Instead of restarting services, the system modifies in-memory processes to apply updates seamlessly.
While this concept has been long used in the Linux world via tools like kpatch and ksplice, Microsoft is now bringing similar functionality to Windows Server deployments.
Benefits of Hotpatching:
- Reduced downtime
- Improved operational efficiency
- Faster security response
- Less disruption to critical services
How Hotpatching Works
Hotpatching follows a structured quarterly patching cycle:
| Patch Type | Months | Reboot Required |
|---|---|---|
| Baseline Updates | January, April, July, October | Yes |
| Hotpatches | Other months | No |
- Baseline patches reset the hotpatching cycle and require a reboot.
- In the two months following each baseline, hotpatches are released and applied without any reboots.
- This results in only four scheduled reboots per year, as opposed to monthly reboots.
On rare occasions, Microsoft may release critical patches that require a reboot, even during a hotpatch month.
Why Microsoft Introduces Paid Hotpatching
During its preview phase, hotpatching was free. Now, Microsoft is shifting to a subscription model to reflect the premium value it provides for enterprises that demand high uptime and efficient patch management.
Microsoft’s key justifications:
- Reduced Downtime: No need to plan weekend or off-hours reboot windows.
- Faster Updates: Hotpatches are lightweight and deploy quickly.
- Enhanced Security: Immediate deployment of security patches.
- Operational Simplicity: Fewer change windows and simplified orchestration.
Internal Microsoft teams, including Xbox operations, have already reported dramatic time savings, with patching tasks taking days instead of weeks.
Subscription Details
| Feature | Details |
|---|---|
| Launch Date | July 1, 2025 |
| Price | $1.50 USD per CPU core/month |
| Eligible Editions | Windows Server 2025 Standard and Datacenter |
| Deployment Requirement | Must be connected via Azure Arc |
| Included with | Datacenter: Azure Edition (no extra cost) |
| Patch Frequency | 8 hotpatches/year + 4 reboot-required baseline patches |
Organizations currently enrolled in the free preview must opt out by June 30, 2025, or they will be automatically enrolled into the paid tier in July.
What Hotpatching Does NOT Cover
Although powerful, hotpatching does not replace all traditional updates. Reboots will still be required for:
- Major non-security updates
- .NET Framework updates
- Driver and firmware changes
- Emergency out-of-band patches
Thus, IT teams should still plan for occasional maintenance windows, though far fewer than before.
Final Thoughts
As Microsoft introduces paid hotpatching to Windows Server 2025, enterprises gain a robust new tool for managing updates with minimal disruption. With Azure Arc integration, hybrid and on-premises servers can now benefit from the same near-zero-downtime patching experience previously reserved for Azure-only environments.
For organizations focused on uptime, security, and efficiency, hotpatching represents a strategic investment — and the $1.50 per core/month price tag may be well worth the reduced risk and increased agility.
