mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 05:17:22 +00:00
Updates to hotpatch content
This commit is contained in:
parent
9d3bf0fdb7
commit
91177ed304
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Hotpatch updates
|
||||
description: Use Hotpatch updates to receive security updates without restarting your device
|
||||
ms.date: 11/19/2024
|
||||
ms.date: 02/03/2025
|
||||
ms.service: windows-client
|
||||
ms.subservice: autopatch
|
||||
ms.topic: how-to
|
||||
@ -22,7 +22,12 @@ ms.collection:
|
||||
> [!IMPORTANT]
|
||||
> This feature is in public preview. It's being actively developed and might not be complete. They're made available on a "Preview" basis. You can test and use these features in production environments and scenarios and provide feedback.
|
||||
|
||||
Hotpatch updates are [Monthly B release security updates](/windows/deployment/update/release-cycle#monthly-security-update-release) that can be installed without requiring you to restart the device. Hotpatch updates are designed to reduce downtime and disruptions. By minimizing the need to restart, these updates help ensure faster compliance, making it easier for organizations to maintain security while keeping workflows uninterrupted.
|
||||
Hotpatch updates are designed to reduce downtime and disruptions. Hotpatch updates are [Monthly B release security updates](/windows/deployment/update/release-cycle#monthly-security-update-release) that install and take effect without requiring you to restart the device. By minimizing the need to restart, these updates help ensure faster compliance, making it easier for organizations to maintain security while keeping workflows uninterrupted.
|
||||
|
||||
Hotpatch is an extension of Windows Update and requires Autopatch to create and deploy hotpatches to devices enrolled in the Autopatch quality update policy.
|
||||
|
||||
> [!NOTE]
|
||||
> Hotpatch is also available on Windows Server and Windows 365. For more information, see [Hotpatch for Windows Server Azure Edition](/windows-server/get-started/enable-hotpatch-azure-edition).
|
||||
|
||||
## Key benefits
|
||||
|
||||
@ -30,7 +35,18 @@ Hotpatch updates are [Monthly B release security updates](/windows/deployment/up
|
||||
- No changes are required to your existing update ring configurations. Your existing ring configurations are honored alongside Hotpatch policies.
|
||||
- The [Hotpatch quality update report](../monitor/windows-autopatch-hotpatch-quality-update-report.md) provides a per policy level view of the current update statuses for all devices that receive Hotpatch updates.
|
||||
|
||||
## Operating system configuration prerequisites
|
||||
## Release cycles
|
||||
|
||||
For more information about the release calendar for Hotpatch updates, see [Release notes for Hotpatch](https://support.microsoft.com/topic/release-notes-for-hotpatch-in-azure-automanage-for-windows-server-2022-4e234525-5bd5-4171-9886-b475dabe0ce8?preview=true).
|
||||
|
||||
| Quarter | Baseline updates (requires restart) | Hotpatch (no restart required) |
|
||||
| ----- | ----- | ----- |
|
||||
| 1 | January | February and March |
|
||||
| 2 | April | May and June |
|
||||
| 3 | July | August and September |
|
||||
| 4 | October | November and December |
|
||||
|
||||
## Operating system configuration prerequisites
|
||||
|
||||
To prepare a device to receive Hotpatch updates, configure the following operating system settings on the device. You must configure these settings for the device to be offered the Hotpatch update and to apply all Hotpatch updates.
|
||||
|
||||
@ -66,13 +82,6 @@ LCUs requires you to restart the device, but the LCU ensures that the device rem
|
||||
> [!NOTE]
|
||||
> If devices aren't eligible for Hotpatch updates, these devices are offered the LCU. The LCU keeps your configured Update ring settings, it doesn't change the settings.
|
||||
|
||||
## Release cycles
|
||||
|
||||
For more information about the release calendar for Hotpatch updates, see [Release notes for Hotpatch](https://support.microsoft.com/topic/release-notes-for-hotpatch-in-azure-automanage-for-windows-server-2022-4e234525-5bd5-4171-9886-b475dabe0ce8?preview=true).
|
||||
|
||||
- Baseline Release Months: January, April, July, October
|
||||
- Hotpatch Release Months: February, March, May, June, August, September, November, December
|
||||
|
||||
## Enroll devices to receive Hotpatch updates
|
||||
|
||||
> [!NOTE]
|
||||
@ -95,3 +104,7 @@ These steps ensure that targeted devices, which are [eligible](#eligible-devices
|
||||
|
||||
> [!NOTE]
|
||||
> Turning on Hotpatch updates doesn't change the existing deadline-driven or scheduled install configurations on your managed devices. Deferral and active hour settings still apply.
|
||||
|
||||
## Roll back a hotpatch update
|
||||
|
||||
Automatic rollback of a Hotpatch update isn’t supported but you can uninstall them. If you experience an unexpected issue with hotpatch updates, you can investigate by uninstalling the hotpatch update and installing the latest standard cumulative update (LCU) and restart. Uninstalling a hotpatch update is quick, however, it does require a device restart.
|
||||
|
Loading…
x
Reference in New Issue
Block a user