mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-11 04:47:23 +00:00
Merge pull request #10770 from MicrosoftDocs/main
[AutoPublish] main to live - 04/11 10:29 PDT | 04/11 22:59 IST
This commit is contained in:
Ruchika Mittal
GitHub
commit
c6b1a35bff
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Unbranded Boot
|
||||
description: Learn about Unbranded Boot, a feature that suppresses Windows elements that appear when Windows starts. Unbranded Boot can also suppress the crash screen when Windows encounters an error that it can't recover from.
|
||||
ms.date: 04/09/2025
|
||||
ms.date: 04/11/2025
|
||||
ms.topic: how-to
|
||||
---
|
||||
|
||||
@ -46,6 +46,9 @@ To enable Unbranded Boot using PowerShell, follow these steps:
|
||||
|
||||
The following instructions provide details about how to configure your devices. Select the option that best suits your needs.
|
||||
|
||||
> [!NOTE]
|
||||
> If Windows is already installed, you can't apply a provisioning package to configure Unbranded Boot. Instead, you must use the command prompt to configure Unbranded Boot.
|
||||
|
||||
#### [:::image type="icon" source="../images/icons/cmd.svg"::: **Command prompt**](#tab/cmd)
|
||||
|
||||
You can use the `bcdedit.exe` command to configure Unbranded Boot settings at runtime.
|
||||
@ -72,7 +75,7 @@ You can use the `bcdedit.exe` command to configure Unbranded Boot settings at ru
|
||||
bcdedit.exe -set {globalsettings} bootuxdisabled on
|
||||
```
|
||||
|
||||
1. Run the following command to suppress any error screens that are displayed during boot. If **noerrordisplay** is on and the boot manager hits a *WinLoad Error* or *Bad Disk Error*, the system displays a black screen
|
||||
1. Run the following command to suppress any error screens that are displayed during boot. If `noerrordisplay` is set to `on` and the boot manager hits a *WinLoad Error* or *Bad Disk Error*, the system displays a black screen
|
||||
|
||||
```cmd
|
||||
bcdedit.exe -set {bootmgr} noerrordisplay on
|
||||
@ -80,7 +83,7 @@ You can use the `bcdedit.exe` command to configure Unbranded Boot settings at ru
|
||||
|
||||
#### [:::image type="icon" source="../images/icons/xml.svg"::: **Unattend**](#tab/unattend)
|
||||
|
||||
You can configure the Unattend settings in the `Microsoft-Windows-Embedded-BootExp` component to add Unbranded Boot features to your image during the design or imaging phase. You can manually create an Unattend answer file or use Windows System Image Manager (Windows SIM) to add the appropriate settings to your answer file. For more information about the Unbranded Boot settings and XML examples, see the settings in [Microsoft-Windows-Embedded-BootExp](/windows-hardware/customize/desktop/unattend/microsoft-windows-embedded-bootexp).
|
||||
You can configure the Unattend settings in the `Microsoft-Windows-Embedded-BootExp` component to add Unbranded Boot features to your image during the design or imaging phase. You can manually create an Unattend answer file or use Windows System Image Manager (Windows SIM) to add the appropriate settings to your answer file.
|
||||
|
||||
### Unbranded Boot settings
|
||||
|
||||
@ -95,14 +98,14 @@ The following table lists Unbranded Boot settings and their values.
|
||||
| `HideBootStatusIndicator` | Contains an integer that suppresses the status indicator that displays during the OS loading phase. | - Set to `1` to suppress the status indicator<br>- The default value is `0`|
|
||||
| `HideBootStatusMessage` | Contains an integer that suppresses the startup status text that displays during the OS loading phase. | - Set to `1` to suppress the startup status text<br>- The default value is `0`|
|
||||
|
||||
For more information about the Unbranded Boot settings and XML examples, see the settings in [Microsoft-Windows-Embedded-BootExp](/windows-hardware/customize/desktop/unattend/microsoft-windows-embedded-bootexp).
|
||||
|
||||
#### [:::image type="icon" source="../images/icons/provisioning-package.svg"::: **PPKG**](#tab/ppkg)
|
||||
|
||||
Customize the boot screen using Windows Configuration Designer and Deployment Image Servicing and Management (DISM).
|
||||
|
||||
You must enable Unbranded Boot on the installation media with DISM before you can apply settings for Unbranded Boot using either Windows Configuration Designer or applying a provisioning package during setup.
|
||||
|
||||
If Windows is already installed, you can't apply a provisioning package to configure Unbranded Boot. You must use the command prompt to configure Unbranded Boot if Windows is installed.
|
||||
|
||||
[!INCLUDE [provisioning-package-1](../../../includes/configure/provisioning-package-1.md)]
|
||||
|
||||
|Path|Value|
|
||||
@ -115,38 +118,33 @@ If Windows is already installed, you can't apply a provisioning package to confi
|
||||
> [!TIP]
|
||||
> For more information, see [SMISettings](/windows/configuration/wcd/wcd-smisettings) in the Windows Configuration Designer reference.
|
||||
|
||||
1. Once you have finished configuring the settings and building the package or image, you use DISM to apply the settings.
|
||||
1. Open a command prompt with administrator privileges.
|
||||
1. Copy install.wim to a temporary folder on hard drive (in the following steps, it assumes it's called c:\\wim).
|
||||
1. Create a new directory.
|
||||
Once you finish to configure the settings and building the package or image, use DISM to apply the settings:
|
||||
|
||||
```cmd
|
||||
md c:\wim
|
||||
```
|
||||
1. Open a command prompt with administrator privileges
|
||||
1. Copy `install.wim` to a temporary folder on the hard drive (for example, `c:\wim`)
|
||||
1. Create a new directory to mount the image:
|
||||
|
||||
1. Mount the image.
|
||||
|
||||
```cmd
|
||||
dism /mount-wim /wimfile:c:\bootmedia\sources\install.wim /index:1 /MountDir:c:\wim
|
||||
```
|
||||
|
||||
1. Enable the feature.
|
||||
|
||||
```cmd
|
||||
dism /image:c:\wim /enable-feature /featureName:Client-EmbeddedBootExp
|
||||
```
|
||||
|
||||
1. Commit the change.
|
||||
|
||||
```cmd
|
||||
dism /unmount-wim /MountDir:c:\wim /Commit
|
||||
```
|
||||
```cmd
|
||||
md c:\wim
|
||||
```
|
||||
1. Mount the image:
|
||||
```cmd
|
||||
dism /mount-wim /wimfile:c:\bootmedia\sources\install.wim /index:1 /MountDir:c:\wim
|
||||
```
|
||||
1. Enable the feature:
|
||||
```cmd
|
||||
dism /image:c:\wim /enable-feature /featureName:Client-EmbeddedBootExp
|
||||
```
|
||||
1. Commit the change:
|
||||
```cmd
|
||||
dism /unmount-wim /MountDir:c:\wim /Commit
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
In the following image:
|
||||
|
||||
1. `BootLogo` is outlined in green, the
|
||||
1. `BootLogo` is outlined in green
|
||||
1. `BootStatusIndicator` is outlined in red
|
||||
1. `BootStatusMessage` is outlined in blue
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Hotpatch updates
|
||||
description: Use Hotpatch updates to receive security updates without restarting your device
|
||||
ms.date: 04/04/2025
|
||||
ms.date: 04/11/2025
|
||||
ms.service: windows-client
|
||||
ms.subservice: autopatch
|
||||
ms.topic: how-to
|
||||
@ -21,25 +21,20 @@ Hotpatch updates are designed to reduce downtime and disruptions. Hotpatch updat
|
||||
|
||||
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
|
||||
|
||||
- Hotpatch updates streamline the installation process and enhance compliance efficiency.
|
||||
- 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.
|
||||
|
||||
## Release cycles
|
||||
## Prerequisites
|
||||
|
||||
For more information about the release calendar for Hotpatch updates, see [Release notes for Hotpatch](https://support.microsoft.com/topic/release-notes-for-hotpatch-public-preview-on-windows-11-version-24h2-enterprise-clients-c117ee02-fd35-4612-8ea9-949c5d0ba6d1).
|
||||
To benefit from Hotpatch updates, devices must meet the following prerequisites:
|
||||
|
||||
| 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 |
|
||||
- For licensing requirements, see [Prerequisites](../prepare/windows-autopatch-prerequisites.md)
|
||||
- Windows 11 Enterprise version 24H2 or later
|
||||
- Devices must be on the latest baseline release version to qualify for Hotpatch updates. Microsoft releases Baseline updates quarterly as standard cumulative updates. For more information on the latest schedule for these releases, 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).
|
||||
- Microsoft Intune to manage hotpatch update deployment with the [Windows quality update policy with hotpatch turned on](#enroll-devices-to-receive-hotpatch-updates).
|
||||
|
||||
## Operating system configuration prerequisites
|
||||
|
||||
@ -49,28 +44,30 @@ To prepare a device to receive Hotpatch updates, configure the following operati
|
||||
|
||||
VBS must be turned on for a device to be offered Hotpatch updates. For information on how to set and detect if VBS is enabled, see [Virtualization-based Security (VBS)](/windows/security/hardware-security/enable-virtualization-based-protection-of-code-integrity?tabs=security).
|
||||
|
||||
### Arm 64 devices must disable compiled hybrid PE usage (CHPE) (Arm 64 CPU Only) (Public preview)
|
||||
> [!NOTE]
|
||||
> Devices might be temporarily ineligible because they don’t have VBS enabled or aren’t currently on the latest baseline release. To ensure that all your Windows devices are configured properly to be eligible for hotpatch updates, see [Troubleshoot hotpatch updates](#troubleshoot-hotpatch-updates).
|
||||
|
||||
### Arm 64 devices must disable compiled hybrid PE usage (CHPE) (Arm 64 CPU Only)
|
||||
|
||||
> [!IMPORTANT]
|
||||
> **Arm 64 devices are 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.
|
||||
|
||||
This requirement only applies to Arm 64 CPU devices when using Hotpatch updates. Hotpatch updates aren't compatible with servicing CHPE OS binaries located in the `%SystemRoot%\SyChpe32` folder. To ensure all the Hotpatch updates are applied, you must set the CHPE disable flag and restart the device to disable CHPE usage. You only need to set this flag one time. The registry setting remains applied through updates. To disable CHPE, create and/or set the following DWORD registry key:
|
||||
Path: `HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management`
|
||||
DWORD key value: HotPatchRestrictions=1
|
||||
This requirement only applies to Arm 64 CPU devices when using Hotpatch updates. Hotpatch updates aren't compatible with servicing CHPE OS binaries located in the `%SystemRoot%\SyChpe32` folder.
|
||||
|
||||
To ensure all the Hotpatch updates are applied, you must set the CHPE disable flag and restart the device to disable CHPE usage. You only need to set this flag one time. The registry setting remains applied through updates.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> This setting is required because it forces the operating system to use the emulation x86-only binaries instead of CHPE binaries on Arm 64 devices. CHPE binaries include native Arm 64 code to improve performance, excluding the CHPE binaries might affect performance or compatibility. Be sure to test application compatibility and performance before rolling out Hotpatch updates widely on Arm 64 CPU based devices.
|
||||
|
||||
To disable CHPE, create and/or set the following DWORD registry key:
|
||||
Path: `HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management`
|
||||
DWORD key value: HotPatchRestrictions=1
|
||||
|
||||
> [!NOTE]
|
||||
> There are no plans to support hotpatch updates on Arm64 devices with CHPE enabled. Disabling CHPE is required only for Arm64 devices. AMD and Intel CPUs don’t have CHPE.
|
||||
|
||||
If you choose to no longer use Hotpatch updates, clear the CHPE disable flag (`HotPatchRestrictions=0`) then restart the device to turn on CHPE usage.
|
||||
|
||||
## Eligible devices
|
||||
|
||||
To benefit from Hotpatch updates, devices must meet the following prerequisites:
|
||||
|
||||
- Operating System: Devices must be running Windows 11 24H2 or later.
|
||||
- VBS (Virtualization-based security): VBS must be enabled to ensure secure installation of Hotpatch updates.
|
||||
- Latest Baseline Release: Devices must be on the latest baseline release version to qualify for Hotpatch updates. Microsoft releases Baseline updates quarterly as standard cumulative updates. For more information on the latest schedule for these releases, 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).
|
||||
|
||||
## Ineligible devices
|
||||
|
||||
Devices that don't meet one or more prerequisites automatically receive the Latest Cumulative Update (LCU) instead. Latest Cumulative Update (LCU) contains monthly updates that supersede the previous month's updates containing both security and nonsecurity releases.
|
||||
@ -80,6 +77,32 @@ 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-public-preview-on-windows-11-version-24h2-enterprise-clients-c117ee02-fd35-4612-8ea9-949c5d0ba6d1).
|
||||
|
||||
- Baseline: Includes the latest security fixes, cumulative new features, and enhancements. Restart required.
|
||||
- Hotpatch: Includes security updates. No restarted required.
|
||||
|
||||
| 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 |
|
||||
|
||||
## Hotpatch on Windows 11 Enterprise or Windows Server 2025
|
||||
|
||||
> [!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).
|
||||
|
||||
Hotpatch updates are similar between Windows 11 and Windows Server 2025.
|
||||
|
||||
- Windows Autopatch manages Windows 11 updates
|
||||
- Azure Update Manager and optional Azure Arc subscription for Windows 2025 Datacenter/Standard Editions (on-premises) manages Windows Server 2025 Datacenter Azure Edition. For more information, on Windows Server and Windows 365, see [Hotpatch for Windows Server Azure Edition](/windows-server/get-started/enable-hotpatch-azure-edition).
|
||||
|
||||
The calendar dates, eight hotpatch months, and four baseline months, planned each year are the same for all the hotpatch-supported operating systems (OS). It’s possible for additional baseline months for one OS (for example, Windows Server 2022), while there are hotpatch months for another OS, such as Server 2025 or Windows 11, version 24H2. Review the release notes from [Windows release health](/windows/release-health/) to keep up to date.
|
||||
|
||||
## Enroll devices to receive Hotpatch updates
|
||||
|
||||
> [!NOTE]
|
||||
@ -94,11 +117,11 @@ LCUs requires you to restart the device, but the LCU ensures that the device rem
|
||||
1. Select **Create**, and select **Windows quality update policy**.
|
||||
1. Under the **Basics** section, enter a name for your new policy and select Next.
|
||||
1. Under the **Settings** section, set **"When available, apply without restarting the device ("Hotpatch")** to **Allow**. Then, select **Next**.
|
||||
1. Select the appropriate Scope tags or leave as Default and select **Next**.
|
||||
1. Select the appropriate Scope tags or leave as Default. Then, select **Next**.
|
||||
1. Assign the devices to the policy and select **Next**.
|
||||
1. Review the policy and select **Create**.
|
||||
|
||||
These steps ensure that targeted devices, which are [eligible](#eligible-devices) to receive Hotpatch updates, are configured properly. [Ineligible devices](#ineligible-devices) are offered the latest cumulative updates (LCU).
|
||||
These steps ensure that targeted devices, which are [eligible](#prerequisites) to receive Hotpatch updates, are configured properly. [Ineligible devices](#ineligible-devices) are offered the latest cumulative updates (LCU).
|
||||
|
||||
> [!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.
|
||||
@ -106,3 +129,48 @@ These steps ensure that targeted devices, which are [eligible](#eligible-devices
|
||||
## 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.
|
||||
|
||||
## Troubleshoot hotpatch updates
|
||||
|
||||
### Step 1: Verify the device is eligible for hotpatch updates and on a hotpatch baseline before the hotpatch update is installed
|
||||
|
||||
Hotpatching follows the hotpatch release cycle. Review the prerequisites to ensure the device is [eligible](#prerequisites) for hotpatch updates. For information on devices that don’t meet the prerequisites, see [Ineligible devices](#ineligible-devices).
|
||||
|
||||
For the latest release schedule, see the [hotpatch release notes](https://support.microsoft.com/topic/release-notes-for-hotpatch-public-preview-on-windows-11-version-24h2-enterprise-clients-c117ee02-fd35-4612-8ea9-949c5d0ba6d1). For information on Windows update history, see [Windows 11, version 24H2 update history](https://support.microsoft.com/topic/windows-11-version-24h2-update-history-0929c747-1815-4543-8461-0160d16f15e5).
|
||||
|
||||
### Step 2: Verify the device has Virtualization-based security (VBS) turned on
|
||||
|
||||
1. Select **Start**, and enter `System information` in the Search.
|
||||
1. Select **System information** from the results.
|
||||
1. Under **System summary**, under the **Item column**, find **Virtualization-based security**.
|
||||
1. Under the **Value column**, ensure it states **Running**.
|
||||
|
||||
### Step 3: Verify the device is properly configured to turn on hotpatch updates
|
||||
|
||||
1. In Intune, review your configured policies within Autopatch to see which groups of devices are targeted with a hotpatch policy by going to the **Windows Update** > **Quality Updates** page.
|
||||
1. Ensure the hotpatch update policy is set to **Allow**.
|
||||
1. On the device, select **Start** > **Settings** > **Windows Update** > **Advanced options** > **Configured update policies** > find **Enable hotpatching when available**. This setting indicates that the device is enrolled in hotpatch updates as configured by Autopatch.
|
||||
|
||||
### Step 4: Disable compiled hybrid PE usage (CHPE) (Arm64 CPU only)
|
||||
|
||||
For more information, see [Arm 64 devices must disable compiled hybrid PE usage (CHPE) (Arm 64 CPU Only)](#arm-64-devices-must-disable-compiled-hybrid-pe-usage-chpe-arm-64-cpu-only).
|
||||
|
||||
### Step 5: Use Event viewer to verify the device has hotpatch updates turned on
|
||||
|
||||
1. Right-click on the **Start** menu, and select **Event viewer**.
|
||||
1. Search for **AllowRebootlessUpdates** in the filter. If AllowRebootlessUpdates is set to `1`, the device is enrolled in the Autopatch update policy and has hotpatch updates turned on:
|
||||
|
||||
``
|
||||
"data": {
|
||||
"payload": "{\"Orchestrator\":{\"UpdatePolicy\":{\"Update/AllowRebootlessUpdates\":true}}}",
|
||||
"isEnrolled": 1,
|
||||
"isCached": 1,
|
||||
"vbsState": 2,
|
||||
``
|
||||
|
||||
### Step 6: Check Windows Logs for any hotpatch errors
|
||||
|
||||
Hotpatch updates provide an inbox monitor service that checks for the health of the updates installed on the device. If the monitor service detects an error, the service logs an event in the Windows Application Logs. If there's a critical error, the device installs the standard (LCU) update to ensure the device is fully secure.
|
||||
|
||||
1. Right-click on the **Start** menu, and select **Event viewer**.
|
||||
1. Search for **hotpatch** in the filter to view the logs.
|
||||
|
||||
@ -4,7 +4,7 @@ metadata:
|
||||
description: Answers to frequently asked questions about Windows Autopatch.
|
||||
ms.service: windows-client
|
||||
ms.topic: faq
|
||||
ms.date: 03/31/2025
|
||||
ms.date: 04/11/2025
|
||||
audience: itpro
|
||||
ms.localizationpriority: medium
|
||||
manager: aaroncz
|
||||
@ -97,6 +97,59 @@ sections:
|
||||
- question: Can I configure when to move to the next ring or is it controlled by Windows Autopatch?
|
||||
answer: |
|
||||
You're in full control over when updates are deployed to their devices. Autopatch groups will recommend a set of intelligent defaults but those are fully customizable so that you can achieve your desired rollout.
|
||||
- name: Hotpatch updates
|
||||
questions:
|
||||
- question: What are the licensing requirements for hotpatch updates?
|
||||
answer: |
|
||||
Windows 11 Enterprise E3 or E5, Windows 11 Enterprise F3 or F5, Windows 11 Education A3 or A5, or a Windows 365 Enterprise license. For more information, see [Prerequisites](../prepare/windows-autopatch-prerequisites.md).
|
||||
- question: Can I still restart devices as often as I want?
|
||||
answer: |
|
||||
Yes, devices that install hotpatch updates are protected the moment the update is installed. However, if a user or your IT Admin wishes to restart the PC you can do it anytime. The device restarts and runs the hotpatch updates.
|
||||
- question: Can I use hotpatch updates on Arm64 devices?
|
||||
answer: |
|
||||
Yes, hotpatch updates are available for Arm64 devices. For more information, see [Arm 64 devices must disable compiled hybrid PE usage (CHPE) (Arm 64 CPU Only)](../manage/windows-autopatch-hotpatch-updates.md#arm-64-devices-must-disable-compiled-hybrid-pe-usage-chpe-arm-64-cpu-only)).
|
||||
- question: What is the default hotpatch behavior on Windows Home or Pro devices?
|
||||
answer: |
|
||||
Hotpatch updates aren't available to Home or Pro devices. Hotpatching requires domain admin or group policy. It's available only via Windows Autopatch update policy, which includes Windows 365 Enterprise, E3/E5, F3 and A3/A5 licenses.
|
||||
- question: How do I enroll devices to receive hotpatch updates?
|
||||
answer: |
|
||||
For more information, see [Enroll devices to receive hotpatch updates](../manage/windows-autopatch-hotpatch-updates.md#enroll-devices-to-receive-hotpatch-updates).
|
||||
- question: What if some devices in my hotpatch policy aren't eligible for hotpatch updates?
|
||||
answer: |
|
||||
For more information on eligibility, see [Prerequisites](../prepare/windows-autopatch-prerequisites.md) and [ineligible devices](../manage/windows-autopatch-hotpatch-updates.md#ineligible-devices).
|
||||
- question: How is hotpatching different for Windows 11 Enterprise and Windows Server 2025?
|
||||
answer: |
|
||||
For more information, see [Hotpatch on Windows 11 Enterprise or Windows Server 2025](../manage/windows-autopatch-hotpatch-updates.md#hotpatch-on-windows-11-enterprise-or-windows-server-2025).
|
||||
- question: How can I tell which of my devices installed a hotpatch update?
|
||||
answer: |
|
||||
Devices receiving the hotpatch update have a different KB number tracking the release and a different OS version than devices receiving the standard update that requires a restart. The monthly KB release articles indicate if the KB installed is hotpatch capable and the corresponding OS version. The following Windows Update message appears “Great news! The latest security update was installed without a restart.”
|
||||
- question: What if I restart a device after receiving a hotpatch update?
|
||||
answer: |
|
||||
The device stays on the hotpatch update KB/OS version after a restart. It won't receive any new features as part of the regular servicing track until the next quarterly cumulative baseline update.
|
||||
- question: Do hotpatch updates only update common system binaries loaded in third-party processes or only Microsoft processes?
|
||||
answer: |
|
||||
Hotpatch updates aren't limited to Microsoft processes. Hotpatch updates are only created for OS binaries. Any process loading OS binaries that have hotpatch updates installed are updated before the application or operating system uses the binaries. This includes common system dynamic link libraries (DLLs) like ntdll.dll.
|
||||
- question: How can I find out if a hotpatch update was applied to the specific DLL?
|
||||
answer: |
|
||||
You can see the hotpatch modules in the memory dump. Symbols for hotpatched DLLs depend on the function that receives the update. Some code that is hotpatch-updated could be public (symbols), while other functions could be private (no symbols).
|
||||
- question: Are there kernel-mode hotpatch updates?
|
||||
answer: |
|
||||
Yes, there are kernel-mode hotpatch updates.
|
||||
- question: What does a failure to apply a hotpatch update look like?
|
||||
answer: |
|
||||
Hotpatch failures are the same as CBS failures when installing other KBs (not enough disk space or download errors for example). In addition, hotpatch update errors are recorded in the event logs. Search the system log for the keyword “hotpatch” to see if your system encountered any errors.
|
||||
- question: Can you switch from hotpatch update to the Standard Windows monthly updates?
|
||||
answer: |
|
||||
Yes, you can. You can manually download the standard Windows monthly update from the Microsoft Update Catalog. In this case, the device stops receiving hotpatch updates and receives standard Windows updates until the month after the next baseline update. Since the device is still enrolled in hotpatching, the device automatically rejoins the hotpatch cadence of updates after the update is released on the baseline month.
|
||||
- question: How do hotpatch update events show up in audit logs?
|
||||
answer: |
|
||||
Process explorer shows it loaded in memory OS ``<binary name>_hotpatch`` loaded in memory. The hotpatch update KB includes a link to the CSV file listing the update payload.
|
||||
- question: Can I get security alerts through Event Tracing for Windows (ETW) about hotpatch updates?
|
||||
answer: |
|
||||
Hotpatch events are captured in the audit log. Search for “hotpatch” in the audit log to find related errors if any were captured.
|
||||
- question: Do I need to test hotpatch updates if I already test monthly updates?
|
||||
answer: |
|
||||
You should test hotpatch updates when released 8 times a year (according to plan) and the regular monthly updates 12 times a year. There are no hotpatch updates for you to test in January (1B), April (4B), July (7B), or October (10B).
|
||||
- name: Support
|
||||
questions:
|
||||
- question: Does Windows Autopatch Support Dual Scan for Windows Update?
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: What's new 2025
|
||||
description: This article lists the 2025 feature releases and any corresponding Message center post numbers.
|
||||
ms.date: 03/31/2025
|
||||
ms.date: 04/11/2025
|
||||
ms.service: windows-client
|
||||
ms.subservice: autopatch
|
||||
ms.topic: whats-new
|
||||
@ -21,6 +21,15 @@ This article lists new and updated feature releases, and service releases, with
|
||||
|
||||
Minor corrections such as typos, style, or formatting issues aren't listed.
|
||||
|
||||
## April 2025
|
||||
|
||||
### April feature releases or updates
|
||||
|
||||
| Article | Description |
|
||||
| ----- | ----- |
|
||||
| [Hotpatch updates](../manage/windows-autopatch-hotpatch-updates.md) | Added [troubleshooting](../manage/windows-autopatch-hotpatch-updates.md#troubleshoot-hotpatch-updates) section |
|
||||
| [FAQ](../overview/windows-autopatch-faq.yml) | Added [hotpatch updates](../overview/windows-autopatch-faq.yml#hotpatch-updates) section to the FAQ. |
|
||||
|
||||
## March 2025
|
||||
|
||||
### March feature releases or updates
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user