Windows Server hotpatching installs monthly security updates by patching the code of running processes in memory, so the server does not need to restart. On Windows Server 2025 Standard and Datacenter, it works on-premises through Azure Arc, and since 15 May 2026 that service carries no extra charge. Restarts still happen, but the plan is four baseline months a year rather than twelve.
| Question | Short answer (November 2026) |
|---|---|
| Which editions? | Server 2025 Standard and Datacenter (via Azure Arc); Datacenter: Azure Edition (built in) |
| Where can it run? | On-premises, other clouds, Azure and Azure Local |
| What does it cost outside Azure? | No extra charge since 15 May 2026 (previously US$1.50 per core per month) |
| Restarts per year | Four planned baselines, plus any unplanned baselines |
| Key technical requirement | UEFI with Secure Boot and virtualization-based security (VBS) |
| What is not hotpatched? | Non-security fixes, .NET, drivers and firmware |
What is hotpatching in Windows Server?
Hotpatching is a way of delivering Windows security updates that changes the in-memory code of running processes without restarting them. Applications keep running and users stay connected, while the server receives the same security fixes as the regular cumulative update channel. It covers Windows security updates only, so other update types still need a restart.
Microsoft first offered hotpatching on Windows Server 2022 Datacenter: Azure Edition virtual machines in Azure. Windows Server 2025 is the first version where standard on-premises servers can use it, through the Azure Arc management service.
The practical benefit is fewer maintenance windows. On a typical monthly patch cycle, a server restarts twelve times a year for security updates; with hotpatching, most of those months need no restart at all.
How does the Windows Server 2025 hotpatch schedule work?
Hotpatching runs on a quarterly cycle. In the first month of each quarter the server installs a baseline, which is a full cumulative update that needs a restart. In the following two months it receives hotpatch updates containing only security fixes, which install without a restart. Microsoft publishes the planned cycle in its hotpatch calendar.
A planned year therefore includes four baselines and eight hotpatch months. Microsoft can also issue an unplanned baseline, for example for an urgent zero-day fix that cannot be delivered as a hotpatch. That replaces the hotpatch for that month and requires a restart.
The real calendar shows unplanned baselines do happen. In Microsoft's Windows Server release information, 2026 so far includes restart months in January, April, June, July, September and October, with hotpatch months in February, March, May and August. November and December 2026 are scheduled as hotpatch months.
What we commonly see: administrators expect exactly four restarts a year and plan staffing around that. Treat four as the minimum, not the guarantee, and keep a monthly maintenance window available in case Microsoft issues an unplanned baseline.
Which Windows Server editions support hotpatching?
Windows Server 2025 Standard and Windows Server 2025 Datacenter support hotpatching when the machine is connected to Azure Arc and hotpatch is enabled in the Azure portal. Windows Server 2025 Datacenter: Azure Edition supports it by default on Azure and Azure Local without Arc. Both Server Core and Desktop Experience installations are supported.

| Edition | Hotpatch route | Runs on |
|---|---|---|
| Windows Server 2025 Standard | Azure Arc, enabled in portal | Physical or virtual, any location |
| Windows Server 2025 Datacenter | Azure Arc, enabled in portal | Physical or virtual, any location |
| Windows Server 2025 Datacenter: Azure Edition | Built in on supported images | Azure and Azure Local VMs only |
| Windows Server 2022 Datacenter: Azure Edition | Built in on supported images | Azure and Azure Local VMs only |
| Windows Server 2022 Standard/Datacenter and older | Not supported | Not applicable |
Preview and Insider builds are not supported, and the server must run Windows Server 2025 build 26100.1742 or later. Container base images and custom Azure images are also excluded.
How much does Windows Server hotpatching cost?
For Windows Server 2025 Standard and Datacenter connected through Azure Arc, Microsoft now provides hotpatching at no extra cost. Billing for enrolled machines stopped on 15 May 2026. Before that, the service was a paid subscription at US$1.50 per CPU core per month after it became generally available in July 2025. Azure Edition VMs have always included it.
You still need a valid Windows Server 2025 licence for each server, and an Azure subscription to connect the machine to Azure Arc. A free Azure account is enough to start, and Microsoft's hotpatch overview on Microsoft Learn confirms the no-extra-cost status. Other Arc services you choose to enable, such as monitoring, can carry their own charges.
Cause and effect: removing the per-core fee changes the arithmetic for small businesses. On a 16-core server the old fee would have been US$24 a month; at no cost, the only remaining trade-off is the Azure Arc agent and the VBS requirement.
What are the requirements for hotpatching on-premises?
An on-premises server needs Windows Server 2025 Standard or Datacenter, UEFI firmware with Secure Boot enabled, virtualization-based security (VBS, also called Virtual Secure Mode) running, the Azure Connected Machine agent installed and connected to Azure Arc, and an Azure subscription. On Hyper-V, the server must be a Generation 2 virtual machine.
- Firmware: UEFI with Secure Boot. A server installed in legacy BIOS mode cannot run VBS, so it needs reinstalling.
-
VBS running: check with
Get-CimInstance -Namespace 'root/Microsoft/Windows/DeviceGuard' -ClassName 'win32_deviceGuard' | Select-Object -ExpandProperty 'VirtualizationBasedSecurityStatus'. A result of2means VBS is running. - Connectivity: the Connected Machine agent needs outbound HTTPS access to Azure endpoints.
- Patch level: the server must be on a supported baseline; Microsoft's known-issues notes show that some out-of-band updates can make a machine ineligible until the next baseline.
Our Windows Server 2025 system requirements guide explains how to confirm UEFI, Secure Boot and TPM status before deployment.
How do I enable hotpatching on Windows Server 2025?
Connect the server to Azure Arc, confirm virtualization-based security is running, then open the machine in the Azure Arc portal, select Hotpatch and confirm. After about ten minutes the setting applies, and the server starts receiving hotpatches from Windows Update in the next hotpatch month. No product key change is involved.
- Install the Azure Connected Machine agent and onboard the server to Azure Arc.
- Check VBS status with the command above. If it is not running, set
HKLM\System\CurrentControlSet\Control\DeviceGuard\EnableVirtualizationBasedSecurityto1and restart. - In the Azure portal go to Azure Arc > Machines and select your server.
- Select Hotpatch, then Confirm.
- Wait about ten minutes. If the status stays Pending, follow Microsoft's Azure Arc agent troubleshooting steps.
- Optionally, use Azure Update Manager, Group Policy or SConfig to schedule installation.
The step-by-step reference is Microsoft's enable hotpatch for Azure Arc-enabled servers article. Use Get-HotFix afterwards to confirm which updates are installed.
Which updates still need a restart with hotpatching?
Quarterly baselines, unplanned baselines, non-security Windows updates, .NET updates and non-Windows updates such as drivers and firmware all still need a restart. Hotpatching covers only Windows security updates in hotpatch months, so applications, agents and hardware updates remain part of your normal maintenance routine.
There is also no automatic rollback. If a hotpatch causes a problem, Microsoft's guidance is to uninstall the latest update, install the last working baseline and restart. That makes a tested backup just as important as before.
Advanced nuance: hotpatching reduces restarts for the operating system, not for workloads with their own update cycles. A server running SQL Server or line-of-business software with monthly vendor patches will still restart for those, so check what drives your current reboot schedule before promising users fewer interruptions.
Is hotpatching worth it for a small business?
Hotpatching is worth it for small businesses that run Windows Server 2025 on UEFI hardware, can allow an outbound connection to Azure, and find monthly restarts disruptive. With the fee removed, the main costs are setting up Azure Arc and meeting the VBS requirement. Servers that are rarely used out of hours gain less.
It is a strong fit for single-server offices where the server runs file shares, line-of-business apps or Remote Desktop all day, because every avoided restart is an avoided interruption. It is less useful if the server already restarts monthly for application updates, or if policy forbids cloud management agents.
If you are still on Windows Server 2019, an in-place upgrade is the first step; our Server 2019 to 2025 upgrade guide covers it. A Windows Server 2025 Standard licence is enough for hotpatching, so there is no need to buy Datacenter for this feature alone; see the current price on the product page. For a wider view of the release, see our Windows Server 2025 new features guide.
Frequently asked questions
Does hotpatching work on Windows Server 2022?
Only on Windows Server 2022 Datacenter: Azure Edition virtual machines running on Azure or Azure Local from supported images. Standard and Datacenter editions of Windows Server 2022 cannot use hotpatching on-premises; that capability arrived with Windows Server 2025 and Azure Arc. Upgrading to 2025 is the route for on-premises servers.
Is Azure Arc hotpatching really free now?
Yes. Microsoft states that Azure Arc-enabled hotpatch for Windows Server 2025 is available at no extra cost, with billing for enrolled machines ending on 15 May 2026. You still need a Windows Server 2025 licence and an Azure subscription, and any other paid Azure services you choose to enable are billed separately.
Can I use hotpatching without an internet connection?
No. Enrolment depends on the Azure Connected Machine agent, which needs outbound connectivity to Azure, and hotpatches are delivered through Windows Update or your update management tool. Fully air-gapped servers cannot enrol through Azure Arc, so they continue on the regular monthly cumulative updates with restarts.
Do I need to restart after enabling hotpatch?
Enabling hotpatch in the Azure Arc portal does not itself require a restart, but turning on virtualization-based security does if it was not already running. The server also restarts for the next baseline before the hotpatch cycle begins, so plan the first month as a normal maintenance window.
Does hotpatching replace a backup or patch testing?
No. Hotpatches contain the same security fixes as the regular cumulative updates and can still cause compatibility problems. There is no automatic rollback, so keep testing updates on a non-critical server first and maintain a current, restorable backup of every production server.
Related guides
- Windows Server 2025 vs 2022: should you upgrade?
- Windows Server 2025 new features
- Windows Server 2025 system requirements
- Windows Server Standard vs Datacenter vs Essentials
Links in this guide
| Link | Type | Why it helps |
|---|---|---|
| Windows Server release information (Microsoft Learn) | External | Official hotpatch and baseline calendar |
| Hotpatch for Windows Server (Microsoft Learn) | External | How hotpatch works, supported platforms, cost status |
| Enable hotpatch for Azure Arc servers (Microsoft Learn) | External | Prerequisites and enablement steps |
| Windows Server 2025 system requirements | Internal | Checking UEFI, Secure Boot and TPM |
| Upgrade Windows Server 2019 to 2025 | Internal | Getting older servers onto 2025 |
| Windows Server 2025 Standard | Internal | Edition that supports Arc hotpatching |
| Windows Server 2025 new features | Internal | Wider overview of the release |
