Windows Server 2025 Hotpatch on a VPS: Azure Arc Setup Guide

Updated on Nov 21, 2026
Mila H
8 MINS READ
Table of Contents
Azure Arc Hotpatch for Windows Server 2025

Hotpatch installs Windows security updates without a restart in most months. On a VPS outside Azure, it works only if you connect the server to Azure Arc, meet a few boot and security rules, and turn it on in the Azure portal. In this guide, you will learn to check your server, connect it to Azure, turn on hotpatch, and confirm it works.

This guide covers Windows Server 2025 Hotpatch with Azure Arc from start to finish, including the limits you need to know.

What You Need Before You Start

Before you plan Windows Server 2025 Hotpatch with Azure Arc, you must know that hotpatch still needs some reboots, and not every VPS can use it. First of all, check this list:

  • Edition: Windows Server 2025 Standard or Datacenter. Desktop Experience and Server Core both work. Datacenter: Azure Edition already has hotpatch and does not need Arc. Other editions, like Essentials, are not supported.
  • Build: 26100.1742 or later. Preview and Insider builds do not work.
  • Boot mode: UEFI with Secure Boot on. On Hyper-V, use a Generation 2 VM.
  • VBS: Virtualization-based security (VBS) must be on and running.
  • Azure Arc: The server must be connected to Azure Arc. Without it, there is no hotpatch.
  • Azure account: You need an Azure subscription and a role that can add machines, like Azure Connected Machine Onboarding or Contributor.
  • Internet: The server must reach Azure over outbound HTTPS.

Licensing and the Azure Arc Dependency

For Windows Server 2025 Hotpatch with Azure Arc, there is no extra fee for hotpatch. It does not depend on Software Assurance, which other Arc benefits do need. You still need a valid, activated Windows license. Many VPS plans include one, but ask your provider to confirm.

The Azure link is not optional. The Azure Connected Machine agent runs on your server and talks to Azure. Azure Update Manager uses this link to show update status and manage updates. If the server goes offline or the agent breaks, you lose this control.

Do not install Arc on a VM that already runs in Azure. Use Arc only on machines outside Azure, unless you are testing.

Check If Your VPS Can Run Hotpatch

Most VPS plans fail at this step when people try Windows Server 2025 Hotpatch with Azure Arc. VBS needs virtualization features inside your VM. On a KVM VPS, your provider must share these CPU features with your VM. Without them, VBS cannot run.

Your VPS may not work if any of these are true:

  • It boots in legacy BIOS mode instead of UEFI.
  • Secure Boot is off, and you cannot change it.
  • The host does not expose virtualization features to the VM, so VBS cannot run.
  • The edition is not Standard or Datacenter, or the build is too old.
  • Outbound HTTPS to Azure is blocked.
  • The VM is short-lived, or you usually rebuild it from a clone. Arc is not a good option for short-lived servers. Cloned images also need extra steps before you connect them to Arc.

Note: Before you buy, ask your provider if the plan has UEFI, Secure Boot, and the CPU features VBS needs. If you want full control over these settings, a dedicated server gives you the whole machine, so no shared host limits you.

Once you know your VPS can support it, follow the steps below to set up hotpatch.

Step 1: Verify the Server

Open PowerShell as Administrator and check the edition and build:

PowerShell
Get-ComputerInfo | Select-Object WindowsProductName, OsVersion, OsBuildNumber

The product name must be Standard or Datacenter, and the build must be 26100.1742 or higher. Next, check Secure Boot:

PowerShell
Confirm-SecureBootUEFI

True means UEFI with Secure Boot is on. An error means the VM is not in UEFI mode, or the platform does not support it. Now check VBS:

PowerShell
(Get-CimInstance -ClassName Win32_DeviceGuard -Namespace root\Microsoft\Windows\DeviceGuard).VirtualizationBasedSecurityStatus

The value 2 means VBS is running. Any other value means you must fix it before you continue. Also, you can run msinfo32 and look for "Virtualization-based security: Running".

Step 2: Turn On VBS if Needed

If the value is not 2, you can turn VBS on with this command:

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

After the restart, run the VBS check again. If it still does not show 2, the problem is usually the host. The VPS may not have UEFI or the CPU features VBS needs. Only your provider can change this. Stop here and ask them. Hotpatch will not work until VBS is running.

Step 3: Prepare Azure

At this point, you can sign in to the Azure portal and register the resource providers for Arc. You can use Azure CLI:

Bash
az account set --subscription "YOUR_SUBSCRIPTION_NAME"az provider register --namespace Microsoft.HybridComputeaz provider register --namespace Microsoft.GuestConfigurationaz provider register --namespace Microsoft.HybridConnectivityaz provider register --namespace Microsoft.Compute

Microsoft.Compute is needed for Azure Update Manager. Then, create or pick a resource group for your servers.

Step 4: Connect the VPS to Azure Arc

Now go to Azure Arc > Machines > Add/Create > Add a machine. Choose Add a single server, pick your subscription, resource group, and region, and select Windows as the OS.

Azure builds an onboarding script for you. Copy the script. On the VPS, open PowerShell as Administrator and run it. It installs the Azure Connected Machine agent and asks you to sign in to Azure.

When it finishes, check the agent with the command below:

PowerShell
azcmagent show

The status should say Connected. If it does not, test the network path:

PowerShell
azcmagent check

This command tests the connection to the Azure endpoints. Fix any blocked outbound traffic before you move on.

Step 5: Turn On Hotpatch in the Azure Portal

At this step, you must turn on hotpatch. This is the main action in Windows Server 2025 Hotpatch with Azure Arc.

  1. Open the Azure portal and go to Azure Arc > Machines.
  2. Select your server.
  3. Select Hotpatch.
  4. Review the message and select Confirm.
  5. Wait about 10 minutes.

Also, you can do this in Azure Update Manager. Go to Resources > Machines, select the server, and under Recommended updates, select Change next to Hotpatch. Choose the option for monthly hotpatch updates, then Enable Hotpatching and Confirm.

If the portal says VSM is not running, go back to Step 2. If the status stays on Pending, check that the Arc agent is connected.

One more rule: You can only get hotpatch after the latest baseline update is installed. Run Windows Update first and install the newest cumulative update.

Step 6: Check Update Status

In the Azure portal, open Azure Update Manager > Machines and select your server. Look at Recommended updates and confirm that Hotpatch shows as enabled. Use Check for updates to run a fresh scan, and One-time update to install updates now.

On the server, you can list installed updates with:

PowerShell
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5

You can use Get-HotFix to see installed patches. Also, you can open Settings > Windows Update > Update history. 

To see schedules and full update history, use Windows Server 2025 Hotpatch with Azure Arc together with Azure Update Manager.

When Hotpatch Still Needs a Reboot

Hotpatch does not remove all restarts, so plan your Windows Server 2025 Hotpatch with Azure Arc schedule around them. It runs in a three-month cycle. The first month is a baseline month. It brings a full update and needs a restart. The next two months are hotpatch months, and they usually need no restart.

Month type Update Restart?
Baseline (Jan, Apr, Jul, Oct) Full cumulative update Yes
Hotpatch (the other two months) Security-only hotpatch Usually no

That means up to four planned restarts a year. Some updates still need a restart, even in hotpatch months. These include non-security Windows updates, .NET updates, and drivers or firmware. Sometimes an urgent fix cannot ship as a hotpatch. In that case, you get an extra baseline update and must restart. You cannot predict when this will happen.

Plan a reboot window for each baseline month. Pick a quiet time, tell your users, and take a backup or snapshot. For example, if you run one app on the VPS, you can set the window for Saturday at 03:00 in the server's time zone.

How to Roll Back a Hotpatch Update

Hotpatch has no automatic rollback. If an update causes a problem, you must remove the latest update and install the last working baseline update. This step requires a restart. Take a VPS snapshot before every baseline month, and keep this step in your Windows Server 2025 Hotpatch with Azure Arc routine, because a snapshot is the fastest way to go back.

To leave the program, turn hotpatch off on the same portal page. After that, the server follows normal Windows Update with regular restarts.

Common Hotpatch Problems and Fixes

Sometimes hotpatch does not turn on or does not work as expected. Most problems come from VBS, the Arc agent, or a missing update. Here are the common problems and how to fix them:

  • Enable fails: VBS is not running. Check Step 1 again.
  • Stuck on Pending: The Arc agent is offline. Run azcmagent show and azcmagent check.
  • Hotpatch not offered: The latest baseline update is missing. Install it first.
  • VBS will not start: The VPS host does not pass the needed features. Ask your provider for another plan or server.

If you need a server that supports these features, choose a Windows VPS with Windows Server 2025 and confirm UEFI, Secure Boot, and virtualization features with the provider.

Conclusion

Windows Server 2025 Hotpatch with Azure Arc can cut the number of restarts. To use it, you need the right edition, UEFI with Secure Boot, running VBS, and a live Azure Arc link.

Check these first, connect the server to Arc, turn on hotpatch, and confirm it in Azure Update Manager. Keep your reboot windows and snapshots ready. Then, you get a steady patch routine with fewer restarts.

No. Baseline months, non-security updates, .NET, drivers, and unplanned baselines still need restarts.

Yes, for Standard and Datacenter outside Azure. The server must stay connected.

Not through Arc. The Arc path in this guide is for Windows Server 2025 only.

Not automatically. You must remove the update, install the last good baseline, and restart.