Hotpatch dates - Time?

Question

Hotpatch dates - Time?

Edvin Suljic 5

Hi!

I am wondering if there is any specific time for when the restarts of VM:s will occur when the hotpatch restart is done? Currently we only see the the month for when the restart will be made.

Is it possible to see when the restart will be done, in time and date? One example is 2025.4B, more details? :)

Nikhil Duserla 6,865 Reputation points Microsoft External Staff

2025-03-20T12:19:06.95+00:00

Hi @Edvin Suljic,

Azure does not provide exact times and dates for hotpatch restarts of virtual machines (VMs). Instead, Azure usually specifies the month in which the hotpatching will take place, such as 2025.4B, indicating that the updates are planned for April 2025.

Hotpatch first establishes a baseline with the current Cumulative Update for Windows Server. Every three months, the baseline periodically refreshes with the latest Cumulative Update. You then receive Hotpatch releases for the next two months after the Cumulative Update.

For example, if January is a Cumulative Update, February and March would have Hotpatch releases. For more information about the Hotpatch release schedule, see Release notes for Hotpatch in Azure Automanage for Windows Server 2022.

Customers will be able to manage updates using the Azure portal or Azure Command Line Interface, with enhanced patch orchestration using Azure Update Management.

If you have any further queries, do let us know.
Nikhil Duserla 6,865 Reputation points Microsoft External Staff

2025-03-24T09:34:57.8833333+00:00

Hi @Edvin Suljic,

I will be waiting for your response to see if the answer helped or if you require more assistance. I am happy to help you.

Thank You!
Edvin Suljic 5 Reputation points

2025-03-25T07:24:32.71+00:00

Hi,

thank you for your answer.

is there a possibility to prevent the upcoming restart after the hotpatch? So that it can be handled manually.
Edvin Suljic 5 Reputation points

2025-03-31T09:04:42.6433333+00:00

@Nikhil Duserla Do you have any answers on my question above? :)
Nikhil Duserla 6,865 Reputation points Microsoft External Staff

2025-03-31T11:02:54.5433333+00:00

Hello @Edvin Suljic,

I had provided a detailed answer when you initially asked on this forum. Kindly refer to the information below. For your convenience, I am posting it again here to ensure clarity.

Hotpatch updates are intended to minimize downtime and disruptions. These updates install and take effect without the need to restart the device. Typically, hotpatching is used for specific updates, such as security fixes or critical patches, that can be applied without compromising the overall stability of the operating system.

To prevent automatic restarts after hotpatching in Windows, you can leverage Group Policy Editor to configure settings that delay or prevent automatic restarts, especially during active hours or when a user is logged in.

Navigate>> Win+R>> gpedit.msc>>Computer Configuration > Administrative Templates > Windows Components > Windows Update>>legacy policies>>

Enable this policy to prevent automatic restarts when a user is logged in during scheduled updates.

Enable this policy and set the start and end times for active hours, preventing restarts during those times.

After configuring the policies, open a Command Prompt as administrator and run gpupdate /force to apply the changes.

Note: However, hotpatch updates are designed to apply patches without requiring a restart, so these settings primarily affect standard Windows updates.

If you have any further queries, do let us know.
Edvin Suljic 5 Reputation points

2025-03-31T12:48:16.8033333+00:00

@Alex Burlachenko

Example: Assign a maintenance configuration to a VM

$vm = Get-AzVM -Name "YourVM" -ResourceGroupName "YourRG"

$config = Get-AzMaintenanceConfiguration -ResourceGroupName "YourRG" -Name "WeekendPatches"

Update-AzVM -VM $vm -ResourceGroupName "YourRG" -MaintenanceConfigurationId $config.Id

I see in my other post that you posted this suggestion for controlling the actual restart.

Does this mean i can handle a maintanance configuration that handles the restart and then keep the hotpatch to install neccesary updates without restart? Does the maintconfiguration make sure that the restart is never done by the hotpatch itself?
Alex Burlachenko 4,310 Reputation points

2025-03-31T13:35:01.8533333+00:00
Edvin Suljic No, a maintenance configuration cannot prevent Hotpatch from performing required restarts it only controls when those restarts occur within Azure's operational constraints.

Your Best Options

For Least Disruptive Patching:

Keep Hotpatch enabled

Set maintenance windows to 48h+ intervals (Azure needs at least one window per month)

Accept occasional unscheduled restarts for critical updates

For Maximum Control (But Less Security):

# Disable Hotpatch entirely Set-AzVmPatchAssessment -EnableHotpatching $false -VMName "YourVM" -ResourceGroupName "YourRG" # Use manual patching on your schedule New-AzMaintenanceConfiguration -Name "FullControlPatches" -ResourceGroupName "YourRG" -MaintenanceScope "InGuestPatch" -Location "eastus" -Duration "04:00" -TimeZone "UTC"

This leaves you responsible for all updates.

rgds,

Alex
Edvin Suljic 5 Reputation points

2025-03-31T14:46:10.1333333+00:00

@Alex Burlachenko

The "Set-AzVmPatchAssessment" is not available as a Az-compute, command. Am I missing something?
Edvin Suljic 5 Reputation points

2025-03-31T14:52:20.51+00:00

I assume the hotpatch is disabled when I disabled it through the GUI portal
Alex Burlachenko 4,310 Reputation points

2025-04-01T12:07:46.4566667+00:00
Edvin, my misstake! You're absolutely right! Set-AzVmPatchAssessment is not a valid Azure PowerShell cmdlet, and I appreciate you catching that. My previous response contained an inaccuracy. Let me correct this and provide the proper way to manage patching in Azure VMs.

# Disable Automatic VM Guest Patching $vm = Get-AzVM -Name "YourVM" -ResourceGroupName "YourRG" $vm.OSProfile.WindowsConfiguration.EnableAutomaticUpdates = $false $vm.OSProfile.WindowsConfiguration.PatchSettings.EnableHotpatching = $false Update-AzVM -ResourceGroupName "YourRG" -VM $vm

rgds,

Alex

1 answer

Your answer

Nikhil Duserla 6,865 Reputation points Microsoft External Staff

2025-03-20T12:19:06.95+00:00

Hi @Edvin Suljic,

Azure does not provide exact times and dates for hotpatch restarts of virtual machines (VMs). Instead, Azure usually specifies the month in which the hotpatching will take place, such as 2025.4B, indicating that the updates are planned for April 2025.

Hotpatch first establishes a baseline with the current Cumulative Update for Windows Server. Every three months, the baseline periodically refreshes with the latest Cumulative Update. You then receive Hotpatch releases for the next two months after the Cumulative Update.

For example, if January is a Cumulative Update, February and March would have Hotpatch releases. For more information about the Hotpatch release schedule, see Release notes for Hotpatch in Azure Automanage for Windows Server 2022.

Customers will be able to manage updates using the Azure portal or Azure Command Line Interface, with enhanced patch orchestration using Azure Update Management.

If you have any further queries, do let us know.
Nikhil Duserla 6,865 Reputation points Microsoft External Staff

2025-03-24T09:34:57.8833333+00:00

Hi @Edvin Suljic,

I will be waiting for your response to see if the answer helped or if you require more assistance. I am happy to help you.

Thank You!
Edvin Suljic 5 Reputation points

2025-03-25T07:24:32.71+00:00

Hi,

thank you for your answer.

is there a possibility to prevent the upcoming restart after the hotpatch? So that it can be handled manually.
Edvin Suljic 5 Reputation points

2025-03-31T09:04:42.6433333+00:00

@Nikhil Duserla Do you have any answers on my question above? :)
Nikhil Duserla 6,865 Reputation points Microsoft External Staff

2025-03-31T11:02:54.5433333+00:00

Hello @Edvin Suljic,

I had provided a detailed answer when you initially asked on this forum. Kindly refer to the information below. For your convenience, I am posting it again here to ensure clarity.

Hotpatch updates are intended to minimize downtime and disruptions. These updates install and take effect without the need to restart the device. Typically, hotpatching is used for specific updates, such as security fixes or critical patches, that can be applied without compromising the overall stability of the operating system.

To prevent automatic restarts after hotpatching in Windows, you can leverage Group Policy Editor to configure settings that delay or prevent automatic restarts, especially during active hours or when a user is logged in.

Navigate>> Win+R>> gpedit.msc>>Computer Configuration > Administrative Templates > Windows Components > Windows Update>>legacy policies>>

Enable this policy to prevent automatic restarts when a user is logged in during scheduled updates.

Enable this policy and set the start and end times for active hours, preventing restarts during those times.

After configuring the policies, open a Command Prompt as administrator and run gpupdate /force to apply the changes.

Note: However, hotpatch updates are designed to apply patches without requiring a restart, so these settings primarily affect standard Windows updates.

If you have any further queries, do let us know.
Edvin Suljic 5 Reputation points

2025-03-31T12:48:16.8033333+00:00

@Alex Burlachenko

Example: Assign a maintenance configuration to a VM

$vm = Get-AzVM -Name "YourVM" -ResourceGroupName "YourRG"

$config = Get-AzMaintenanceConfiguration -ResourceGroupName "YourRG" -Name "WeekendPatches"

Update-AzVM -VM $vm -ResourceGroupName "YourRG" -MaintenanceConfigurationId $config.Id

I see in my other post that you posted this suggestion for controlling the actual restart.

Does this mean i can handle a maintanance configuration that handles the restart and then keep the hotpatch to install neccesary updates without restart? Does the maintconfiguration make sure that the restart is never done by the hotpatch itself?
Alex Burlachenko 4,310 Reputation points

2025-03-31T13:35:01.8533333+00:00

Edvin Suljic No, a maintenance configuration cannot prevent Hotpatch from performing required restarts it only controls when those restarts occur within Azure's operational constraints.

Your Best Options

For Least Disruptive Patching:

Keep Hotpatch enabled

Set maintenance windows to 48h+ intervals (Azure needs at least one window per month)

Accept occasional unscheduled restarts for critical updates

For Maximum Control (But Less Security):

# Disable Hotpatch entirely Set-AzVmPatchAssessment -EnableHotpatching $false -VMName "YourVM" -ResourceGroupName "YourRG" # Use manual patching on your schedule New-AzMaintenanceConfiguration -Name "FullControlPatches" -ResourceGroupName "YourRG" -MaintenanceScope "InGuestPatch" -Location "eastus" -Duration "04:00" -TimeZone "UTC"

This leaves you responsible for all updates.

rgds,

Alex
Edvin Suljic 5 Reputation points

2025-03-31T14:46:10.1333333+00:00

@Alex Burlachenko

The "Set-AzVmPatchAssessment" is not available as a Az-compute, command. Am I missing something?
Edvin Suljic 5 Reputation points

2025-03-31T14:52:20.51+00:00

I assume the hotpatch is disabled when I disabled it through the GUI portal
Alex Burlachenko 4,310 Reputation points

2025-04-01T12:07:46.4566667+00:00

Edvin, my misstake! You're absolutely right! Set-AzVmPatchAssessment is not a valid Azure PowerShell cmdlet, and I appreciate you catching that. My previous response contained an inaccuracy. Let me correct this and provide the proper way to manage patching in Azure VMs.

# Disable Automatic VM Guest Patching $vm = Get-AzVM -Name "YourVM" -ResourceGroupName "YourRG" $vm.OSProfile.WindowsConfiguration.EnableAutomaticUpdates = $false $vm.OSProfile.WindowsConfiguration.PatchSettings.EnableHotpatching = $false Update-AzVM -ResourceGroupName "YourRG" -VM $vm

rgds,

Alex

Answer 1

Hello @Edvin Suljic,

Hotpatch updates are intended to minimize downtime and disruptions. These updates install and take effect without the need to restart the device. Typically, hotpatching is used for specific updates, such as security fixes or critical patches, that can be applied without compromising the overall stability of the operating system.

To prevent automatic restarts after hotpatching in Windows, you can leverage Group Policy Editor to configure settings that delay or prevent automatic restarts, especially during active hours or when a user is logged in.

Navigate>> Win+R>> gpedit.msc>>Computer Configuration > Administrative Templates > Windows Components > Windows Update>>legacy policies>> User's image

Enable this policy to prevent automatic restarts when a user is logged in during scheduled updates. User's image

Enable this policy and set the start and end times for active hours, preventing restarts during those times.

After configuring the policies, open a Command Prompt as administrator and run gpupdate /force to apply the changes.

Note: However, hotpatch updates are designed to apply patches without requiring a restart, so these settings primarily affect standard Windows updates.

If you have any further queries, do let us know.

If you found this informative, please consider accepting an answer as a token of appreciation. And don't forget to give it a thumbs up 👍 if it was helpful.

User's image

Share via

Hotpatch dates - Time?

Example: Assign a maintenance configuration to a VM

1 answer

Your answer