Windows Server hotpatch
Microsoft's edit ·
Microsoft's commit message in MicrosoftDocs/windowsserverdocs · commit ff8bb91 · +10 −11 lines · also on GitHub
⋯ 2 unchanged lines
33
description: 'Learn how Hotpatch for Windows Server works and how to enable it'
44
author: robinharwood
55
ms.topic: conceptual
6
−ms.date: 11/19/2024
6
+ms.date: 02/27/2025
77
ms.author: roharwoo
88
---
99
⋯ 17 unchanged lines
2727
2828
>[!NOTE]
2929
>Windows Server container base images, custom images, or any other combination of publisher, offer, and SKU aren't supported.
30
−>
31
−>Not all regions currently support Windows Server 2025: Azure Edition images. If you try to use this feature in a region that doesn't currently support Windows Server 2025: Azure Edition, you might see an HTTP 400 client error. To work around this issue, use a different region that does currently support this feature, such as UK South, East Asia, or West Central US.
3230
31
+
3332
| Publisher | OS Offer | SKU |
3433
|-------------------------|---------------|--------------------|
3534
| MicrosoftWindowsServer | WindowsServer | 2022-Datacenter-Azure-Edition-Core |
⋯ 5 unchanged lines
4140
| MicrosoftWindowsServer | WindowsServer | 2025-Datacenter-Azure-Edition-Core |
4241
| MicrosoftWindowsServer | WindowsServer | 2025-Datacenter-Azure-Edition-Core-smalldisk |
4342
44
−For more information about the available images, see [Windows Server](https://aka.ms/hotpatchondesktopnewimage) on the Azure Marketplace.
43
+For more information about the available images, see [Windows Server](https://aka.ms/hotpatchondesktopnewimage) on Azure Marketplace.
4544
4645
### Azure Arc-connected machines (preview)
4746
⋯ 16 unchanged lines
6463
6564
- **Planned baselines** are released on a regular cadence, with Hotpatch releases in between. Planned baselines include all the updates in a comparable Latest Cumulative Update for that month and require you to restart your machine.
6665
67
− - For example, a planned one year release period may include four planned baseline releases in a calendar year and eight Hotpatch releases.
66
+ - For example, a planned one year release period might include four planned baseline releases in a calendar year and eight Hotpatch releases.
6867
6968
- **Unplanned baselines** are released during an unplanned important update, such as a zero-day fix, when that particular update can't be released as a Hotpatch. When unplanned baselines release, a Hotpatch release is replaced with an unplanned baseline for that month. Unplanned baselines also include all the updates in a comparable Latest Cumulative Update for that month, and therefore require you to restart your machine.
7069
⋯ 5 unchanged lines
7675
7776
Hotpatch covers Windows Security updates and maintains parity with the content of security updates issued to in the regular non-Hotpatch Windows update channel.
7877
79
−There are a few important things you need to consider when enabling Hotpatch on a supported version of Windows Server. You still need to restart your machine to install updates that aren't included in the Hotpatch program. You also need to periodically restart after installing a new baseline. Restarting keeps your VM in sync with non-security patches included in the latest cumulative updates.
78
+There are a few important things you need to consider when enabling Hotpatch on a supported version of Windows Server. You still need to restart your machine to install updates that aren't included in the Hotpatch program. You also need to periodically restart after installing a new baseline. Restarting keeps your VM in sync with nonsecurity patches included in the latest cumulative updates.
8079
8180
The following patches currently aren't included in the Hotpatch program and require you to update your machine during Hotpatch release months:
8281
83
−- Non-security updates for Windows
82
+- Nonsecurity updates for Windows
8483
8584
- .NET updates
8685
⋯ 17 unchanged lines
104103
- Azure monitors VM health through platform health signals to detect patching failures.
105104
106105
> [!NOTE]
107
−> You can't create VM scale sets (VMSS) with Uniform orchestration on Azure Edition images with Hotpatch. To learn more about which features are supported by Uniform orchestration for scale sets, see [A comparison of Flexible, Uniform, and availability sets](/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-orchestration-modes).
106
+> You can't create Azure Virtual Machine Scale Sets with Uniform orchestration on Azure Edition images with Hotpatch. To learn more about which features are supported by Uniform orchestration for scale sets, see [A comparison of Flexible, Uniform, and availability sets](/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-orchestration-modes).
108107
109108
### Azure Local
110109
⋯ 3 unchanged lines
114113
115114
- SCONFIG configures Windows Update client settings for Server Core.
116115
117
−- Third-party patch management solutions.
116
+- Non-Microsoft patch management solutions.
118117
119118
### Azure Arc-connected machines
120119
⋯ 5 unchanged lines
126125
127126
- SCONFIG configures Windows Update client settings for Server Core.
128127
129
−- Third-party patch management solutions.
128
+- Non-Microsoft patch management solutions.
130129
131130
For more information about which tools Hotpatch uses, check out our [Azure Update Manager](https://aka.ms/HotpatchAUM) documentation.
132131
⋯ 21 unchanged lines
154153
155154
- [Azure Update Management](/azure/automation/update-management/overview)
156155
157
−- [How to preview Azure Arc-connected Hotpatching for WIndows Server 2025](https://techcommunity.microsoft.com/t5/windows-server-news-and-best/how-to-preview-azure-arc-connected-hotpatching-for-windows/ba-p/4246895)
156
+- [How to preview Azure Arc-connected Hotpatching for Windows Server 2025](https://techcommunity.microsoft.com/t5/windows-server-news-and-best/how-to-preview-azure-arc-connected-hotpatching-for-windows/ba-p/4246895)
Microsoft's Markdown source from MicrosoftDocs/windowsserverdocs, © Microsoft Corporation, under CC BY 4.0. Changed lines with up to 3 unchanged lines around each; ChangeIntel kept this copy 10 Oct 00:39 UTC. The commit date is when the source changed, which can be hours or days before Learn published it.