How To

Windows Server 2025 Hotpatching: Requirements, Azure Arc and Cost

Outside Azure, Windows Server 2025 hotpatching has one dependency you cannot design around. The server has to be connected to Azure Arc, whether it runs in your own racks or another cloud. The fee that used to come with it is gone, because Microsoft dropped the $1.50 per core per month charge in May 2026. What’s left is a short list of platform requirements, and the one that trips up virtualized fleets is virtualization-based security (VBS), which has to be running, not just switched on.

Original content from computingforgeeks.com - post 180456

This piece works through the requirements, the Arc question, the cost history and the restart calendar you actually get. We built it on a Windows Server 2025 Datacenter VM on Proxmox VE in October 2026, so the VBS results, the CPU-type failure and the Arc agent output are real. The Arc enrollment itself was not run, because the lab has no Azure subscription attached, and we say so wherever that matters.

Hotpatching without Azure Arc

You cannot hotpatch Windows Server 2025 Standard or Datacenter without Azure Arc. Microsoft’s own wording is that the server “must be connected to Azure Arc”, and none of its pages describe a WSUS, Configuration Manager or plain Windows Update route that enrolls a machine on its own. The only edition that skips Arc is Datacenter: Azure Edition, and that edition runs on Azure itself or on Azure Local, not on your VMware or Proxmox hosts.

The table sorts the paths by where the server runs, because that decides everything else.

Where the server runsEditionArc neededHotpatch fee (Oct 2026)
Azure VMDatacenter: Azure EditionNo, on by defaultNone
Azure Local VMDatacenter: Azure EditionNoNone
On premises, VMware, Hyper-V, Proxmox, AWS, GCPStandard or DatacenterYesNone since May 2026
Anywhere, no Arc connectionStandard or DatacenterNot connectedNot eligible: monthly cumulative updates with a restart

In practice this means the decision is not “hotpatch or not” but “do we accept an Arc agent on every server”. Once a machine is enrolled, the updates still flow through the normal Windows Update client, so Group Policy, SConfig on Server Core, Azure Update Manager or a third-party patch tool can all orchestrate them. One catch for shops that patch through a WSUS server: Microsoft publishes hotpatch packages to Windows Update only, with no Update Catalog or WSUS download, so an enrolled server pointed solely at WSUS never sees them. Let those servers scan Windows Update directly, or move them to Azure Update Manager, before you enroll.

The requirements Microsoft checks

Microsoft’s Arc hotpatch prerequisites fit on one screen. The first five items below come from that page, and the last one is the condition that silently drops a server back to restart-every-month updates:

  • Edition: Windows Server 2025 Standard, Datacenter, or Datacenter: Azure Edition. Desktop Experience and Server Core both qualify, and preview or Insider builds do not.
  • Build: 26100.1742 or later, the build Windows Server 2025 shipped on at general availability in November 2024.
  • Firmware: UEFI with Secure Boot enabled. On Hyper-V that means a Generation 2 VM, and on Proxmox an OVMF VM whose EFI disk has pre-enrolled Secure Boot keys.
  • VBS running: the portal checks Virtual Secure Mode when you enable hotpatch, and enrollment fails if it is not running.
  • Azure Arc: an Azure subscription, the Connected Machine agent’s network prerequisites, and the machine connected to Arc. Azure Edition is exempt.
  • Update level: not on the prerequisite page, but it follows from how the cycle works. Hotpatches build on the current baseline, so a server is only offered them once it sits on the latest baseline cumulative update, the October 2026 baseline (KB5126646) at the time of writing.

TPM is not on Microsoft’s list, and neither is a minimum core count. The update level is the one people forget: Microsoft’s Arc page still carries the October 2025 incident, where servers that installed the wrong October package got regular restart-required updates until the January 2026 baseline. A server that falls off the baseline does not error out. It just goes back to normal monthly cumulative updates, so you only notice when the reboot prompts come back.

A local check of edition, build and firmware

Before touching Azure at all, we’d confirm the edition, build and firmware locally, because those three cannot be fixed from the portal. Run these in an elevated PowerShell session on the server. The first command reads the edition and the exact build, including the update revision (UBR):

Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion' | Select-Object ProductName, EditionID, InstallationType, CurrentBuild, UBR, DisplayVersion | Format-List

Our lab server, cloned from a template built in January, reported Datacenter on build 26100 with revision 32230:

ProductName      : Windows Server 2025 Datacenter
EditionID        : ServerDatacenter
InstallationType : Server
CurrentBuild     : 26100
UBR              : 32230
DisplayVersion   : 24H2

Revision 32230 is the January 2026 baseline (KB5073379). That clears the 26100.1742 floor easily, but it’s five baselines behind October (April, July and October plus unplanned ones in June and September), so this server would need the current cumulative update and one restart before it’s offered a single hotpatch. InstallationType : Server is Desktop Experience; Server Core reports Server Core and is equally eligible. Next, check the firmware type and Secure Boot:

$env:firmware_type
Confirm-SecureBootUEFI

Both have to come back as below. A BIOS-mode VM prints Legacy instead, and moving it to UEFI means converting the disk to GPT and changing the VM firmware, so this is the check to run before anything else:

UEFI
True

The installed updates tell you which baseline the server sits on, and they’re also how you’ll later confirm a hotpatch landed, since Microsoft points to Get-HotFix for exactly that:

Get-HotFix | Sort-Object InstalledOn | Select-Object HotFixID, Description, InstalledOn | Format-Table -AutoSize

KB5073379 in the list is the January 2026 baseline. On an enrolled server, a hotpatch month adds a different KB number from the regular cumulative update of the same month. August 2026’s hotpatch was KB5120228, while the cumulative update was KB5120233, so matching KB numbers against Microsoft’s calendar tells you which track a machine is on.

HotFixID  Description     InstalledOn
--------  -----------     -----------
KB5072725 Security Update 1/14/2026 12:00:00 AM
KB5073379 Security Update 1/14/2026 12:00:00 AM
KB5066131 Update          1/14/2026 12:00:00 AM

Edition, build and firmware all pass on this box. The remaining local requirement is VBS, and that’s where a virtual machine can pass every other check and still fail.

Virtualization-based security on the server

VBS runs part of the kernel inside a small hypervisor-protected region, and hotpatching depends on it, which is why the portal refuses enrollment without it. Microsoft gives a single WMI property to check, VirtualizationBasedSecurityStatus in the Win32_DeviceGuard class, where 2 means running. Read it along with the services VBS is carrying:

Get-CimInstance -Namespace root/Microsoft/Windows/DeviceGuard -ClassName Win32_DeviceGuard | Select-Object VirtualizationBasedSecurityStatus, AvailableSecurityProperties, RequiredSecurityProperties, SecurityServicesRunning | Format-List

Our template-built server had it off. Status 0 means VBS is not enabled at all, which is normal on a server where nothing else (Credential Guard, memory integrity) has asked for it:

VirtualizationBasedSecurityStatus : 0
AvailableSecurityProperties       : {2, 4, 5, 8}
RequiredSecurityProperties        : {0}
SecurityServicesRunning           : {0}

Microsoft’s documented switch is one registry value under the DeviceGuard key. Set it, then restart, because VBS only starts at boot:

New-ItemProperty -Path 'HKLM:\System\CurrentControlSet\Control\DeviceGuard' -Name 'EnableVirtualizationBasedSecurity' -PropertyType 'Dword' -Value 1 -Force
Restart-Computer

For a fleet, the same setting lives in Group Policy under Computer Configuration, Administrative Templates, System, Device Guard, “Turn On Virtualization Based Security”, which saves you scripting the registry on every host. We did not test the policy route. It also offers memory integrity (Virtualization Based Protection of Code Integrity), which can stop incompatible drivers from loading, so if hotpatching is the only goal, set Platform Security Level to Secure Boot, leave code integrity Not Configured and avoid the UEFI lock option. After the restart, read the status again:

Get-CimInstance -Namespace root/Microsoft/Windows/DeviceGuard -ClassName Win32_DeviceGuard | Select-Object -ExpandProperty VirtualizationBasedSecurityStatus

Our server came back with 2 on the first reboot, which is the value the Arc enrollment check wants to see:

2

That result depended on one Proxmox setting we hadn’t thought about until we changed it. The template VM uses cpu: host, which passes the physical CPU’s virtualization extensions into the guest so Windows can start its own hypervisor.

VirtualizationBasedSecurityStatus stays at 1 on a Proxmox or KVM guest

We shut the same VM down, switched its CPU type to Proxmox’s default x86-64-v2-AES, and booted it with the registry value still set to 1. VBS dropped to status 1, which means enabled but not running. Windows accepted the configuration and then couldn’t start the hypervisor underneath it, and the server boots normally, so nothing looks wrong until enrollment fails. The processor check shows why:

Get-CimInstance -ClassName Win32_Processor | Select-Object Name, VirtualizationFirmwareEnabled, VMMonitorModeExtensions, SecondLevelAddressTranslationExtensions | Format-List

With the generic CPU model, the guest sees no VT-x and no second-level address translation, so there’s nothing for VBS to run on:

Name                                    : QEMU Virtual CPU version 2.5+
VirtualizationFirmwareEnabled           : False
VMMonitorModeExtensions                 : False
SecondLevelAddressTranslationExtensions : False

Under cpu: host the same three properties read True on our Intel Core i7-1165G7 node, and VBS ran. On Proxmox or plain KVM, the fix we tested is the CPU type host plus nested virtualization enabled on the node. Then stop and start the VM from the hypervisor, since a reboot from inside Windows keeps the old CPU model. On vSphere the equivalent is the VM’s “Enable Virtualization Based Security” option, and on Hyper-V Microsoft’s minimum is a Generation 2 VM with Secure Boot on. Our Windows Server template on Proxmox already uses OVMF with pre-enrolled Secure Boot keys and a vTPM, so the CPU type was the only change needed.

The Arc agent half of the build

The Arc side splits cleanly into two parts: installing the Azure Connected Machine agent, which needs nothing from Azure, and connecting it to a subscription, which does. We ran the first part in the lab. The second needs a subscription and a service principal or an interactive sign-in, which this lab does not have, so Arc onboarding and the hotpatch enrollment were not tested here.

Download the agent package from Microsoft’s short link and install it silently with a log, which is how you’d push it from a deployment tool anyway:

Invoke-WebRequest -Uri 'https://aka.ms/AzureConnectedMachineAgent' -OutFile "$env:TEMP\AzureConnectedMachineAgent.msi" -UseBasicParsing
Start-Process msiexec.exe -ArgumentList "/i `"$env:TEMP\AzureConnectedMachineAgent.msi`" /qn /l*v `"$env:TEMP\azcmagent-install.log`"" -Wait

The MSI was 116 MB and installed version 1.69.03579.3449 on our server. It starts its services even before the machine is connected, so check the three main ones came up:

Get-Service himds, GCArcService, ExtensionService | Format-Table Name, Status, DisplayName -AutoSize

The Hybrid Instance Metadata Service (himds) is the agent itself, and the two Guest Configuration services handle policy and extensions once it’s connected:

Name              Status DisplayName
----              ------ -----------
ExtensionService Running Guest Configuration Extension Service
GCArcService     Running Guest Configuration Arc Service
himds            Running Azure Hybrid Instance Metadata Service

The step we’d always run before asking anyone for Azure credentials is the agent’s connectivity check, because a proxy or an outbound firewall rule is the usual reason an Arc rollout stalls on the second server. Pass the Azure region you plan to register the machines in:

& "$env:ProgramFiles\AzureConnectedMachineAgent\azcmagent.exe" check --location westeurope

The command first prints the same status block as azcmagent show, which on our machine read Agent Status : Disconnected with all four agent services running (these three plus the Arc proxy), then tests every core endpoint. This is the endpoint table it produced:

time="2026-10-30T09:44:31Z" level=info msg="Cloud: AzureCloud"
time="2026-10-30T09:44:31Z" level=info msg="Testing connectivity to endpoints that are needed to connect to Azure... This might take a few minutes."
Use Case  |Endpoint                                              |Reachable  |Private  |TLS      |Proxy
core      |https://agentserviceapi.guestconfiguration.azure.com  |true       |false    |TLS 1.3  |not used
core      |https://gbl.his.arc.azure.com                         |true       |false    |TLS 1.3  |not used
core      |https://gbl.his.arc.azure.com/weu/his                 |true       |false    |TLS 1.3  |not used
core      |https://login.microsoftonline.com                     |true       |false    |TLS 1.3  |not used
core      |https://management.azure.com                          |true       |false    |TLS 1.3  |not used
core      |https://pas.windows.net                               |true       |false    |TLS 1.3  |not used
core      |https://westeurope-gas.guestconfiguration.azure.com   |true       |false    |TLS 1.3  |not used

Seven endpoints, all reachable over TLS 1.3 with no proxy. Any false in the Reachable column is the line to hand to your network team, and on a segment that only allows traffic through a proxy the Proxy column shows whether the agent picked it up. Those hostnames cover the Arc connection only. Each enrolled server also needs Windows Update reachable to download the hotpatches themselves.

From there, Microsoft documents the rest: azcmagent connect with a subscription, resource group and region registers the machine, and then you open the machine under Azure Arc, Machines, select Hotpatch and confirm. Microsoft says to allow about 10 minutes for the change, with the status moving from Pending to Enabled; Azure Update Manager has the same switch for enabling many machines at once. We haven’t run those steps, so treat the timing as Microsoft’s figure rather than ours.

What hotpatching costs in 2026

Hotpatching an Arc-connected Windows Server 2025 machine costs nothing in October 2026. The Azure Update Manager hotpatch page puts it plainly: as of May 19, 2026 there is “no per-core meter, no hourly charge, and no separate Hotpatch line item on your invoice”, for any edition and any underlying platform. The fee only ever existed for about ten months, as the history shows.

PeriodArc-connected Standard or DatacenterAzure Edition on Azure or Azure Local
Preview, until mid-July 2025FreeIncluded
July 16, 2025 to May 2026$1.50 per CPU core per monthIncluded
From May 19, 2026No chargeIncluded

You’ll see two dates for the change, and both come from Microsoft. The Learn page above says May 19, 2026, while the FAQ in Microsoft’s Azure Arc blog announcement says billing for machines already enrolled stopped on May 15. Either way, enrolled servers needed no action and stayed enrolled. If you priced hotpatching from a 2025 article, the old number was material: a two-socket host licensed for 32 cores ran $48 a month, or $576 a year, which is why many teams parked it.

The fee going away does not make the surrounding stack free, so budget for these separately.

  • Arc connection: no charge for the basic inventory and management tier, and hotpatch itself carries no charge since May 2026 per the Update Manager page above.
  • Azure Update Manager: optional for hotpatch. It is free for servers covered by Software Assurance or Extended Security Updates once they are attested through Windows Server Management enabled by Azure Arc, or with Defender for Servers Plan 2, and otherwise billed per Arc server per month. Check its pricing before you make it the orchestration layer.
  • Windows Server licences: unchanged. Hotpatch needs no extra licence, but Arc does not license the OS for you.

If you orchestrate hotpatches through Group Policy settings for the Windows Update client, or a patch tool that drives that client, the bill for hotpatching an on-premises server is zero. The real cost becomes the change process for putting an Azure agent on every machine.

Azure Edition versus an Arc-connected server

Both routes deliver the same hotpatch packages on the same calendar, so the choice comes down to where the workload already lives. Datacenter: Azure Edition is the simpler build because hotpatch is on by default and no agent is involved, but it only runs on Azure and Azure Local:

AspectDatacenter: Azure EditionStandard or Datacenter with Arc
Runs onAzure VMs, Azure Local VMsAny physical or virtual host, any cloud
AgentNoneAzure Connected Machine agent
EnrollmentEnabled by defaultPer machine in Arc or Update Manager
FeeNoneNone since May 2026
Windows Server 2022Supported (2022 Azure Edition)Not supported, 2025 only
VBS, UEFI, Secure BootRequiredRequired

The 2022 row is the one that changes plans. If part of your fleet is still on Windows Server 2022 outside Azure, Arc cannot hotpatch it, so those servers keep monthly restarts until they’re upgraded. On Azure itself we’d pick Azure Edition every time, and outside Azure the Arc route is the only route, which makes the comparison less of a choice than it first looks. For servers you manage through Windows Admin Center, Arc onboarding is also available from there, which suits teams that do not live in the Azure portal.

The restart calendar you actually get

The marketing figure is four restarts a year: a baseline cumulative update in January, April, July and October, then two hotpatch months after each. 2025 matched that exactly. 2026 didn’t, and Microsoft’s hotpatch calendar shows why: when a fix cannot ship as a hotpatch, Microsoft replaces that month’s hotpatch with an unplanned baseline that needs a restart.

Month20252026
JanuaryBaseline (restart)Baseline (restart), KB5073379
FebruaryHotpatchHotpatch, KB5075942
MarchHotpatchHotpatch, KB5078736
AprilBaseline (restart)Baseline (restart), KB5082063
MayHotpatchHotpatch, KB5087423
JuneHotpatchBaseline (restart), KB5094125
JulyBaseline (restart)Baseline (restart), KB5099536
AugustHotpatchHotpatch, KB5120228
SeptemberHotpatchBaseline (restart), KB5122871
OctoberBaseline (restart)Baseline (restart), KB5126646
NovemberHotpatchHotpatch (scheduled)
DecemberHotpatchHotpatch (scheduled)

Ten months into 2026, an enrolled server has restarted for six of them, against ten for a server on regular cumulative updates. If November and December ship as scheduled, the year ends at six restarts instead of the promised four, still a 50% cut. That’s the honest number to put in a change-advisory slide, and it varies by year because unplanned baselines follow the vulnerabilities, not the calendar.

Three more limits shape the maintenance windows, and each one puts a restart back into a month you might have planned as restart-free.

  • Scope: hotpatches carry security fixes only. Non-security Windows updates, .NET updates, drivers and firmware still need a restart in hotpatch months if you install them then.
  • Rollback: there is no automatic rollback. Backing out a bad hotpatch means uninstalling it and reinstalling the last good baseline, with a restart.
  • Firmware work: Secure Boot certificate updates and similar firmware-level changes sit outside hotpatch and get their own window.

We would group driver and .NET updates into the baseline months, so the hotpatch months stay genuinely restart-free and the six-restart figure holds.

The enrollment decision by fleet

With the fee gone, the case rests on restarts saved against an agent added, and it lands differently by fleet:

  • Clustered or stateful 2025 servers: enroll. Each avoided restart is a drain and failover you do not schedule, and six restarts a year instead of twelve adds up across a cluster.
  • Servers already on Arc for Defender or policy: enroll, because the agent is already there and the remaining work is VBS plus the baseline.
  • Air-gapped or no-cloud-agent environments: skip it. There is no non-Arc path for Standard or Datacenter, so plan regular cumulative updates.
  • Fleets still on Windows Server 2022 outside Azure: not eligible until the upgrade, so hotpatching becomes one more line in the case for moving to 2025.

For a fleet of fifty VMs, the work is mostly two template changes rather than fifty manual jobs: CPU passthrough plus VBS in the VM template, and the Arc agent with its endpoint check in your build pipeline. If you’re still building the base image, start from our Windows Server 2025 install guide, set VBS before sysprep, and every clone comes up ready for enrollment on its first baseline month.

Keep reading

Create a Bootable Windows 11 USB and Install Windows 11 Windows Create a Bootable Windows 11 USB and Install Windows 11 Set Up a Samba Share on Windows 11 and Access It from Linux Networking Set Up a Samba Share on Windows 11 and Access It from Linux Create Disk Partitions in Windows Using diskpart Windows Create Disk Partitions in Windows Using diskpart Windows LAPS Setup with Group Policy on Windows Server 2025 Security Windows LAPS Setup with Group Policy on Windows Server 2025 Windows Run Commands Cheat Sheet: .msc, .cpl, ms-settings (PDF) Cheat Sheets Windows Run Commands Cheat Sheet: .msc, .cpl, ms-settings (PDF) How To Run Arch Linux on Windows WSL Arch Linux How To Run Arch Linux on Windows WSL

Leave a Comment

Press ESC to close