Windows Server 2022 Hotpatching Extended to October 2027

Did Microsoft really extend Windows Server 2022 hotpatching to 2027?

Yes. Microsoft extended hotpatch update support for Windows Server 2022 by one full year, pushing it from the original October 2026 cutoff to October 2027. The catch is that this only applies to Windows Server 2022 Datacenter: Azure Edition systems already enrolled in hotpatching, and the existing patch cadence stays exactly the same through that new date.

For anyone running production workloads, websites, or application servers on that platform, this buys roughly twelve extra months of reboot-light security updates before you have to think seriously about moving to Windows Server 2025. That sounds like a small administrative footnote, but uptime is money. Every forced reboot is a maintenance window, a risk of something not coming back cleanly, and a few minutes where your site or app is unreachable. Understanding exactly what this extension covers — and what it quietly does not — saves you from planning around the wrong date.

What hotpatching actually does for uptime

Hotpatching deploys security updates by patching the in-memory code of running processes, so the server keeps running without a restart after each installation. Normally Windows wants a reboot to load patched binaries from disk. Hotpatching sidesteps that for most security fixes, which is the entire point: fewer reboots means more continuous uptime.

The schedule runs on a quarterly rhythm. Four times a year you get a baseline month — a full cumulative update that does require a reboot — followed by two months of hotpatch-only updates that do not. That drops a typical patch year from twelve reboots down to four.

One thing most coverage glosses over: hotpatching only covers Windows security updates. Non-security Windows updates, and out-of-band patches like .NET runtime updates, still ride the regular update channel and can still demand a restart. So hotpatching reduces reboots dramatically — it does not eliminate them. If you are quoting an internal SLA, plan for the occasional unplanned restart outside the four baseline months.

Who actually qualifies — and the catch in the fine print

This is where the headline gets people into trouble. The 2027 extension is narrow on purpose.

• It covers only Datacenter: Azure Edition. If you run standard Windows Server 2022 Datacenter, Standard, or Essentials on bare metal or a non-Azure VM, this hotpatch extension does not apply to you.
• You must already be enrolled in hotpatch updates. The extension keeps an existing capability alive; it is not a new door opening for everyone.
• End of support is a separate clock. Windows Server 2022 as a product still reaches its extended end-of-support date on October 14, 2031. The 2027 date is specifically about how long the reboot-light hotpatch stream keeps flowing, not when the OS stops getting security fixes entirely.

So there are really two dates to track: October 2027 for hotpatching on the qualifying Azure Edition, and October 2031 for broader extended support. Confusing the two is the easiest way to either panic early or get caught flat-footed late.

If you are running Windows Server 2022 outside Azure and assumed this extension covers you, it does not — your patch-and-reboot routine is unchanged, and your real migration planning horizon is the 2031 support date.

How this compares to the Windows Server 2025 hotpatch subscription

The reason this extension matters is what comes after it. Hotpatching used to be a free perk. On Windows Server 2025, Microsoft turned it into a paid subscription. It became generally available on July 1, 2025, after the free preview ended, and it is billed through Azure Arc.

That subscription is billed every month at the same rate, whether or not a given month actually ships a hotpatch, so your cost is predictable across the year. For a modest 16-core server that is roughly $24 a month, or about $288 a year, purely for the privilege of fewer reboots. On a fleet of servers it adds up fast. The 2022 extension is, in effect, a one-year reprieve from that bill — a window to budget, test Windows Server 2025, and decide whether reboot-light patching is worth a recurring per-core fee for your particular workload.

What this means if you just want your website online

If you run a Windows-based application server yourself, this directly affects your patch calendar. But a lot of people reading about "server uptime" are really asking a simpler question: how do I keep my site fast and online without becoming a part-time sysadmin?

For most websites, the honest answer is that you should not be hand-patching an operating system at all. The whole value of managed hosting is that uptime, security patching, and reboots are the provider's problem, not yours. Most modern web hosting runs on Linux with technologies like NVMe storage and LiteSpeed for low TTFB, and the host handles kernel-level security updates — often with live patching of their own — so your site stays up while the maintenance happens underneath you.

This is where choosing the right host matters more than memorizing Microsoft's patch calendar. A provider like LaunchPad Host takes on the patching, uptime monitoring, and server maintenance as part of managed hosting, so the question of "which month needs a reboot" never reaches you. If your needs are privacy-forward or you want crypto-friendly, offshore-hosted infrastructure, that managed layer still applies — you get the uptime benefits without running and patching the box yourself. Run your own Windows server only when an application genuinely requires it; otherwise let the host carry the maintenance burden.

Should you ride out 2022 or move to Windows Server 2025?

If you qualify for the extension, you have a legitimate reason to wait. Twelve more months of free reboot-light patching is real value, and there is no urgency to pay the new per-core subscription before you have tested Windows Server 2025 properly.

Use the runway deliberately rather than drifting:

1. Confirm your edition. Verify you are actually on Datacenter: Azure Edition with hotpatching enrolled — otherwise the 2027 date is irrelevant to you and 2031 is your real planning horizon.
2. Cost the subscription. Multiply your total CPU cores by $1.50 and twelve months. That number tells you whether reboot-light patching is worth paying for once the free ride ends.
3. Test before you migrate. Stand up a Windows Server 2025 instance, validate your applications, and confirm hotpatching behaves the way you expect before committing production workloads.
4. Question whether you need the server at all. If the workload is a website or standard web app, managed hosting may remove the entire patch-and-reboot problem for less money and less effort.

The extension is good news, but it is a deadline with a countdown, not a permanent reprieve. Track October 2027 for hotpatching and October 2031 for support, decide whether the WS2025 subscription fits your budget, and — if you are really just running a website — seriously weigh letting a managed host handle all of it for you.