> For the complete documentation index, see [llms.txt](https://docs.adaptiva.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adaptiva.com/patch/scenarios/feature-updates.md). # Apply Windows Feature Updates OneSite Patch allows you to apply annual Windows feature updates. With OneSite Patch you have the ability to update your Windows version (i.e., version 24H2, 25H2, or 26H2) with Windows feature updates. Windows feature updates are provided by Microsoft as significant upgrades to the Windows operating system. They provide major versions, such as Windows 11 25H2, that roll up security updates and bug fixes along with feature updates and performance enhancements. Feature updates also include Windows 10 to Windows 11 update options. You activate which version you want by using an enablement package. The enablement package reduces the need for multiple installations and reboots for the various feature updates. Instead, you have a single package install with a single reboot. However, because a reboot is involved, you should verify your reboot schedules per Business Unit. Windows 11 is the current major release of Microsoft's workstation operating system. The oldest operating system that can be upgraded is Windows 10 2004 (10.0.19041). {% hint style="warning" %} Please note that you will need a OneSite Patch license that includes Windows Operating System patching. Please contact your Adaptiva representative for more information. {% endhint %} ### Install Windows 11 feature update #### Prerequisites All devices to be upgraded must meet the [Windows 11 System Requirements](https://www.microsoft.com/en-us/windows/windows-11-specifications). Additional prerequisites depend on the Windows 11 version you want to install. Each device must meet one of the supported starting configurations for that target version. | Target version | Supported starting configuration | | ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Windows 11 23H2** | **Windows 10, version 2004**, with the September 2021 cumulative update or a later update installed (**OS build 19041.1415 or later**); **or Windows 11, version 22H2**, with the October preview update or a later update installed (**OS build 22621.2506 or later**). | | **Windows 11 24H2** | **Windows 11, version 23H2 or 22H2**, with the May 2024 preview update or a later update installed (**OS build 22631.3672 or later** for 23H2, or **22621.3672 or later** for 22H2). | | **Windows 11 25H2** | **Windows 11, version 24H2**, with the August 2025 preview update or a later update installed (**OS build 26100.5074 or later**). | | **Windows 11 26H2** | **Windows 11, version 25H2 or 24H2**, with the September 2026 preview update or a later update installed (**OS build 26200.9550 or later** for 25H2, or **26100.9550 or later** for 24H2). | {% hint style="info" %} The minimum OS builds listed above include the Update Build Revision (UBR), which is the final number in the build. The Business Unit filters in the following section identify the Windows version but do not verify that the required cumulative update is installed. {% endhint %} #### (Optional) Create a target Business Unit Creating a target Business Unit is optional because patches are installed only on applicable devices. However, Business Units can help you deploy updates in waves and track devices that may need manual intervention. To group Windows 11 devices by version, create child Business Units under: **Operating System > Operating System – Windows > Operating System – Windows 11** A Windows 10 Business Unit already exists. For each Windows 11 child Business Unit, use the **OperatingSystemCrossPlatform** sensor with the following condition: | Business Unit | Condition | | ------------- | --------------------------- | | 22H2 Devices | Version Equals `10.0.22621` | | 23H2 Devices | Version Equals `10.0.22631` | | 24H2 Devices | Version Equals `10.0.26100` | | 25H2 Devices | Version Equals `10.0.26200` | | 26H2 Devices | Version Equals `10.0.26300` | {% hint style="info" %} The sensor does not capture the Update Build Revision (UBR) by default. Enter the values exactly as shown, without appending the final revision number. For example, use `10.0.26100`, not `10.0.26100.5074`. {% endhint %} ![Business Unit Filter](https://2503798551-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7VJNM00p5XQ4pMWqCu8y%2Fuploads%2Fgit-blob-825e9c2121f41abc8ca7c040cd8b0c0927bbd0ac%2Fbusiness-unit-filters.png?alt=media) #### Unblock Windows feature updates {% hint style="info" %} Before you unblock the Blocked Patch you should review ALL Strategies. If any Strategy has **Include All Products** enabled, you should add *Windows 11 OS Upgrade* (for 24H2) and *Windows 11 Enablement Packages* (for 23H2, 25H2, and 26H2) to the list of **Excluded Products** to ensure it does not get deployed by that Strategy. {% endhint %} The OneSite Patch metadata team will automatically block all Windows 11 feature updates so you can decide which devices receive the update and when. In order to add these patches to a strategy you will need to start by unblocking a single Windows OS Upgrade (24H2) or Enablement Package (23H2, 25H2, or 26H2). For more information about blocklisting see [Flex Controls - Blocklisting](/patch/patch-operations/flex-controls/flex-controls-blocklisting.md). {% hint style="info" %} You can enable blocklist notifications to receive automatic notifications when Adaptiva adds blocked patches. {% endhint %} ![Blocklist for Windows 11](https://2503798551-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7VJNM00p5XQ4pMWqCu8y%2Fuploads%2Fgit-blob-d290c3e96cc5fa478b1ab772d0cccf622efbb423%2Fblocklist.png?alt=media) 1. Select **Advanced Settings > Flex Controls > Blocklisting > Blocked Patches**. * You can also view blocked patches from the [Home Dashboard](/patch/get-started/dashboards.md#home) by selecting the **Blocked Patches (System)** link in the **Patching Overrides** widget. ![Patching overrides](https://2503798551-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7VJNM00p5XQ4pMWqCu8y%2Fuploads%2Fgit-blob-18308d4b1bb739d8646a23586ea96020c2ebf4af%2Fpatching-overrides-widget.png?alt=media) 2. Search for the feature update version you wish to install, for example **Windows 11 26H2**. ![Curate blocked patches](https://2503798551-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7VJNM00p5XQ4pMWqCu8y%2Fuploads%2Fgit-blob-67451841abb214f0933b267d2afa23a9882f416b%2Fcurate-blocked-patches.png?alt=media) 3. Click the ellipses (**...**) next to the patch name and select **Unblock**. * Unblock only one feature update or enablement package at a time. Windows feature updates do not follow supersedence rules, and unblocking multiple versions can result in installation failures. ![Unblock button](https://2503798551-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7VJNM00p5XQ4pMWqCu8y%2Fuploads%2Fgit-blob-d8af4864f1b371733f8927202ef3fda2f3360131%2Funblock-button.png?alt=media) ### Create a Strategy to Deploy 1. Select **Strategies** from the left side navigation 2. Click **New Strategy**. #### Overview 1. Add a unique **Name** and **Description**, e.g. Windows feature update 24H2. 2. Toggle **ON** **Enable Strategy**. #### What to Patch 1. Click Browse next to Include Products and select the Windows 11 OS Upgrade (for 24H2) or Windows 11 Enablement Packages (for 23H2, 25H2, and 26H2). ![What to patch](https://2503798551-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7VJNM00p5XQ4pMWqCu8y%2Fuploads%2Fgit-blob-fa2c6b96e798330467fedfc7339b37ff8cb1d610%2Fwhat-to-patch-windows11-upgrade.png?alt=media) 2. Click **Next** #### When to Patch 1. Click **Browse** next to **Schedule** and select a time you wish for this patch strategy to run. 2. Click **Next**. #### How to Patch 1. Click **+ Add Transition > Approval Transition**. 2. Click **Browse** next to **Approver Roles** and select which roles you would like to have notified when this strategy runs. 3. Set the **Reminder Interval** to a desired time. 4. Click **+ Add Deployment Ring**. 5. Click **Browse** and select the Business Unit(s) you'd like to be targeted. 6. Click **Save and Deploy**. Your strategy will now run on your specified schedule and only update devices where the Windows feature update is applicable. ### Monitor deployment and installation Once the [Approval Request](/patch/patch-operations/approval-requests.md) has been approved, you can monitor the progress with [Flex Control Cycles](/patch/patch-operations/flex-controls/flex-controls-cycle-operations.md). After the installation is completed on the device, the Adaptiva client will capture the restart requirement and display a toast notification based on the User Interaction Settings applied to the device. We recommend that users restart as soon as possible. If you normally allow a long delay before restart, you should apply a shorter User Interaction Setting to the Business Unit(s) that were created. Soon after the device is upgraded, the **Windows 11 OS Upgrade** product is no longer applicable, and the device will be removed from the Patch Status dashboard. The image below shows the patch status prior to installation. For the 7-Zip MSI x64 this reports the **Installed** status, however, the Windows 11 24H2 Upgrade will be removed after installation since it is now the installed OS and the device will report its OS status rather than this as an installed patch. ![Patch status](https://2503798551-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7VJNM00p5XQ4pMWqCu8y%2Fuploads%2Fgit-blob-c82693b8c448fbaebf9c8530f277cb79eb0abb2a%2Fpatch-status.png?alt=media) However, you can see the progress of the installation from the [Device Dashboard - Device Activity widget](/patch/get-started/dashboards.md#devices). 1. Select **Asset Management > Devices** from the left side navigation. 2. Click on the device **Name** from the **Device Status** widget at the bottom of the dashboard. This will open up the individual device's dashboard. 3. Under **Device Activity**, you can view the timeline of events including the installation of the Windows Update Feature. ![Device activity](https://2503798551-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7VJNM00p5XQ4pMWqCu8y%2Fuploads%2Fgit-blob-b41774b4f28ea84a996e798acb8dd8bcde2a272a%2Fdevice-activity.png?alt=media) ### Troubleshooting #### Issue - 25H2 Not Applicable on Device Windows 11 25H2 requires the device to be running Windows 11 24H2 with the August 2025 preview update or a later update installed (OS build 26100.5074 or later). **Solution** To install Windows 11 25H2, the device must be running Windows 11 24H2 with the August 2025 preview update or a later update installed (**OS build 26100.5074 or later**). 1. Open the **Run** dialog, type `winver`, and press **Enter**. 2. Verify that the device is running **Windows 11 24H2**. 3. Verify that the OS build is **26100.5074 or later**. The Update Build Revision (UBR) is the final number in the OS build. For Windows 11 24H2, the UBR must be **5074 or higher** to meet this prerequisite. ![Winver](https://2503798551-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7VJNM00p5XQ4pMWqCu8y%2Fuploads%2Fgit-blob-224af34dfdb5c338063c66d61107b9247ff2b6ea%2Fwindows-version.png?alt=media) #### Issue - device does not show **Windows 11 OS Upgrade** in Installed Products In `%programfiles%\Adaptiva\AdaptivaClient\logs\componentlogs`, review the `PatchingAdmin.log` and look for a line like the following: ``` INFO - Products :: Scanned status [NOT INSTALLED] for [1000006900] ``` **Solution** 1. Check for the existence of the following registry key: `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\CompatMarkers\` 2. Review the version subkey: * Version 24H2 — **GE24H2** * Version 25H2 — **GE25H2** * Version 26H2 — **GE26H2** 3. If there are any items starting with **Blocked** with a value of **1**, the device cannot be upgraded. 4. Remediate any issues and re-scan. {% hint style="info" %} You may need to select Reset Data -- which requires the scanning of All Software. {% endhint %} If the registry key does not exist, open a Command Prompt as Administrator and manually run the following command. This will evaluate the device and create the registry key. ```cmd %windir%\System32\CompatTelRunner.exe -m:appraiser.dll -f:DoScheduledTelemetryRun ``` This command should be scheduled to run automatically. Review the following if changes have been made to the default Task Scheduler Library. 1. Open Task Scheduler. 2. Expand the **Task Scheduler Library | Microsoft | Windows** and select **Application Experience**. 3. In the details pane, select the **Microsoft Compatibility Appraiser** task. 4. Review the **Last Run Time** and **Last Run Result**. If you need help executing this across your estate, please contact Adaptiva Support. **Issue**: The device is targeted but did not upgrade. One possible issue is the lack of disk space. The feature update process will not run unless there is 50GB of free disk space. In `%programfiles%\Adaptiva\AdaptivaClient\logs\componentlogs`, review the `ContentCache.log` and look for a line like the following: ``` INFO - Drive [C] is having actualFreeSpace Including Progress [###] ``` The `###` needs to be larger than **52428800000** bytes. ### Support If you have any questions, please contact support via the [Adaptiva Support Portal](https://support.adaptiva.com) or email