Microsoft Extends Windows Server 2022 Hotpatching Through October 2027

Microsoft has extended hotpatching support for Windows Server 2022 Datacenter: Azure Edition by a full year, moving the deadline from October 2026 to October 2027. The change is effective immediately and applies only to servers enrolled in the hotpatch program, the company said in a Windows release health dashboard update. The existing monthly hotpatch cadence stays unchanged through the new end date.

The extension lands three months before Windows Server 2022 reaches the end of mainstream support on October 13, 2026. Hotpatching normally ends with mainstream support, and the reprieve is limited to a single SKU line. On-premises installations of Windows Server 2022 Standard, Datacenter, and Essentials are still left out, and they continue to face the same restart-heavy update cycle as before. For shops running the Azure Edition in production, the practical question is no longer how soon they must upgrade; it is whether the extra year should change their Windows Server 2025 migration plan at all.

Microsoft’s One-Year Hotpatch Reprieve

Microsoft said the extension lets enrolled Azure Edition servers keep receiving monthly security updates without a restart through October 2027. The company described the change in a Monday message center note and on its Windows Release Health dashboard.

Microsoft wrote on its release health dashboard that hotpatch update support for Windows Server 2022 Datacenter: Azure Edition has been extended through October 2027, with enrolled devices continuing to receive monthly security updates without requiring a restart. The same note framed hotpatching as a way to maintain uptime and shorten the time it takes to respond to vulnerabilities. Mainstream support for the broader Windows Server 2022 product still ends on October 13, 2026. Extended support for every Windows Server 2022 edition, including Datacenter, Datacenter: Azure Edition, Essentials, and Standard, remains scheduled to end on October 14, 2031. The cadence and experience remain consistent with prior hotpatch releases.

By the numbers

• October 2027: new hotpatch end date for Windows Server 2022 Datacenter: Azure Edition
• October 13, 2026: mainstream support end date for Windows Server 2022
• October 14, 2031: extended support end date for all Windows Server 2022 editions
• February 2022: month hotpatching reached general availability for Server 2022 Datacenter: Azure Edition
• One: number of Windows Server 2022 editions covered by the hotpatch extension

How Hotpatching Patches a Running Server

Hotpatching is a different mechanic from a standard Windows cumulative update. The update applies to the in-memory code of a running process instead of replacing the on-disk binaries. That is why no restart is needed to put the patch into effect.

The cadence follows a quarterly rhythm. Once a quarter, an enrolled server receives a baseline cumulative update that does require a reboot. For the two months between baselines, the server receives hotpatches that flow straight into memory and keep running workloads online. Microsoft delivers security updates this way without restarting the process or rebooting the device, per the full announcement text that detailed the extension. Servers still need a restart for non-security patches and for updates that fall outside the hotpatch program, including .NET updates. The result is fewer of the relentless monthly reboots that regular Windows servicing demands.

Microsoft has been rolling hotpatching out across more of its lineup over the past four years. The sequence below shows how the Server 2022 extension fits into a wider pattern across the Microsoft stack. Each step has widened the share of the fleet that can be patched without a restart.

Hotpatching rollout at a glance

1. February 2022: hotpatching reaches general availability for Windows Server 2022 Datacenter: Azure Edition.
2. September 2024: hotpatching for Windows Server 2025 enters public preview.
3. November 2024: testing begins for Windows 11 24H2 and Windows 365.
4. April 2025: hotpatch updates become generally available for Windows 11 Enterprise 24H2 on x64.
5. May 2026: hotpatch security updates are enabled by default for eligible Windows devices managed through Microsoft Graph API and Microsoft Intune.

Only the Azure Edition Gets the Extension

The reprieve is narrower than it sounds. The extension covers only one of the four Windows Server 2022 editions Microsoft sells, and only on virtual machines that match a specific set of Azure marketplace images. Standard, Essentials, and the on-premises Datacenter SKU do not qualify for hotpatching, even though they fall under the same Fixed Lifecycle Policy. Administrators running those editions will continue to follow the regular update cycle and will need to restart as before. Even with the extension in place, on-premises shops gain no new reboot-free patching capability.

Within the Azure Edition line, only four eligible SKUs are part of the program. Each maps to a different Azure VM image size, and the technical documentation for hotpatching lists them explicitly.

Eligible Azure marketplace SKUs

• 2022-Datacenter-Azure-Edition-Core
• 2022-Datacenter-Azure-Edition-Core-smalldisk
• 2022-Datacenter-Azure-Edition-Hotpatch
• 2022-Datacenter-Azure-Edition-Hotpatch-smalldisk

Microsoft uses the publisher MicrosoftWindowsServer and the offer WindowsServer for the four eligible SKUs, and the same approach applies to Server 2025. The four editions of Windows Server 2022 fall under the Fixed Lifecycle Policy as listed on the official lifecycle page for Server 2022. The lifecycle page is also where Microsoft publishes future support timeline changes for the broader Server 2022 family. Servers running anything other than the listed SKUs, including custom images or Windows Server container base images, are not eligible. Administrators can check enrollment through the Windows Autopatch management interface or through the Azure portal. On-premises Windows Server 2022 users remain out of luck.

The Migration Math Just Shifted by a Year

The headline effect of the announcement is operational. Azure Edition operators get twelve more months of reboot-free patching for the workloads they already have running. The consequential effect is on Server 2025 migration plans. Those plans, for many shops, just got pushed back a year.

Microsoft says the decision to move to Windows Server 2025 can now be made on operational needs rather than end-of-support deadlines. The company would still prefer administrators to migrate, and its encouragement is now backed by an extra year of runway for those who defer. Windows Server 2025 LTSC went on general availability on November 1, 2024. Its mainstream support runs until November 13, 2029, with extended support scheduled to end on November 14, 2034. Server 2025 also adds new security capabilities that the older release lacks. Petri.com lists enhanced Active Directory security, stronger SMB protections, improved hybrid-cloud integration through Azure Arc, and better storage performance. The comparison table below frames how the two releases stack up for a Datacenter: Azure Edition shop weighing its next move.

Server 2022 Azure Edition vs Server 2025 LTSC

Server 2025 hotpatching is delivered through Azure Arc, which can extend to on-premises installations, a path the Server 2022 Azure Edition never offered. Microsoft extended hotpatching support through October 2027 specifically for Datacenter: Azure Edition, not for Standard, Essentials, or Datacenter. The end-of-support dates for the broader Windows Server 2022 family remain unchanged. The implication is that shops comfortable with Azure can stretch their Server 2022 lifecycle by a year, but on-premises shops cannot. Migration planning, for them, still needs to happen on the original calendar.

Microsoft still recommends planning the move to Windows Server 2025. Teams that already have a Server 2025 plan in flight should keep their schedule. Teams without one can use the year to build it. The decision to migrate can now be driven by features and operational fit rather than by end-of-support pressure. The extended support end date for Windows Server 2022 remains October 14, 2031. Microsoft extended hotpatching support through October 2027 specifically for Datacenter: Azure Edition; Standard, Essentials, and on-premises Datacenter are not part of the reprieve.

Microsoft Is Pressing a Wider Restart-Free Push

The Server 2022 extension is the latest move in a broader Microsoft effort to shrink restart-related downtime across the Windows stack. Over the past four years, the company has widened hotpatching from a single Azure Edition SKU in February 2022 to a default behavior on many enterprise Windows 11 endpoints. Public preview for Windows Server 2025 hotpatching began in September 2024. Testing then opened up for Windows 11 24H2 and Windows 365 two months later in November 2024. April 2025 brought general availability for Windows 11 Enterprise 24H2 on x64 systems. Most recently, May 2026 marked the point at which Microsoft began enabling hotpatch updates by default for eligible devices managed through Microsoft Graph API and Microsoft Intune.

The Server 2022 extension also changes which customers sit inside the safety net. Microsoft says the Azure Edition shops enrolled in the program can keep their existing monitoring, scheduling, and operational practices through October 2027 without modification. The hotpatch cadence stays monthly, and the published calendar continues. The Register frames the move as Microsoft being mindful of users who depend on the technology while still nudging them toward newer releases and toward Azure.

Hotpatching is designed to deliver protections against security threats without requiring a device restart. By applying updates directly to running processes, hotpatching helps maintain uptime, reduces servicing disruptions, and shortens the time it takes to respond to vulnerabilities.

The push is consistent with Microsoft’s stated goal of reducing servicing disruptions for production workloads. The competitive backdrop matters: Linux tooling like Ksplice has long offered reboot-free kernel patching. Microsoft is now matching that capability across more of its Windows portfolio. For shops already running Azure Edition, the practical question is no longer whether hotpatching works. The question now is how to fit the extra runway into a multi-year migration roadmap.

What IT Teams Should Check This Week

For shops running Windows Server 2022 Datacenter: Azure Edition, the next step is verification. Administrators can confirm hotpatch enrollment through the Windows Autopatch management interface or by opening the Updates blade under Operations on the VM’s Azure portal Overview page. Both views show whether the VM is enrolled and which patches are queued for the current baseline cycle. The Get-HotFix cmdlet in PowerShell also lists installed patches across the last 30 days for a quick sanity check. Microsoft recommends that organizations continue to plan their Windows Server 2025 migration alongside the extended hotpatch runway. The company would still prefer administrators to migrate off the older release when operationally possible. For IT teams that already have a Server 2025 plan in flight, the extra year does not change the schedule.

Microsoft has been clear that the extension does not change the underlying extended support end date of October 14, 2031 for the Windows Server 2022 family. Migration planning still needs to happen, just on a calendar that now has more room in it. For shops running Standard, Essentials, or on-premises Datacenter, the announcement does not move the needle; those editions never had hotpatching and still do not. Recent emergency hotpatches on Windows 11, such as the emergency patch that closed the RRAS remote code execution hole and the emergency Bluetooth visibility patch from March 2026, show the same restart-free approach scaling across the broader Windows portfolio.

Frequently Asked Questions

Does this extension also cover mainstream support for Windows Server 2022?

No. Mainstream support still ends on October 13, 2026. Only the hotpatch program for Datacenter: Azure Edition has been extended, and only through October 2027.

Do on-premises Windows Server 2022 servers get the extension?

No. Only Datacenter: Azure Edition virtual machines enrolled in hotpatching receive the extension. Standard, Essentials, and on-premises Datacenter installations remain on the standard restart-requiring update cycle.

Do Azure Edition servers still need to reboot at all?

Yes, but rarely. The monthly security hotpatches do not require a reboot, but the quarterly baseline cumulative update, non-security Windows patches, and .NET updates still do.

Should organizations now skip migrating to Windows Server 2025?

Microsoft still recommends migrating. The extension defers the urgency by a year but does not extend the Windows Server 2022 extended support end date of October 14, 2031.

How do administrators check if their servers are enrolled in hotpatching?

Open the Updates blade under Operations on the Azure portal Overview page for the VM, or use the Windows Autopatch management interface. The Get-HotFix PowerShell cmdlet lists installed patches over the past 30 days.