> 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 update Windows operating system versions using Windows Feature Updates. With OneSite Patch you have the ability to update your Windows version (i.e. version 24H2 or 25H2) 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 24H2, 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. 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 license that includes Windows Operating System patching. Please contact your Adaptiva representative for more information. {% endhint %} ### Install Windows 11 Feature Update #### Prerequisites Windows Feature updates with OneSite Patch require the following: * Version 23H2 needs to be updated to 24H2 prior to updating to 25H2, while this is not required for all versions, it is still best practice in general. * All systems to be upgraded must meet the [Windows 11 System Requirements](https://www.microsoft.com/en-us/windows/windows-11-specifications?msockid=35eb35f3b4d96bef1bb823a7b5ae6a7c\&r=1). #### (Optional) Create a target Business Unit This step is optional since patches will only be installed on applicable devices. You may wish to create Business Units in order to split up the deployment into multiple waves. The additional benefit of creating a Business Unit is it can be used to easily track which devices may need manual intervention. A sensor can be used to filter by the current Operating System. | Sensor | Field | | ------------------------------------- | ------- | | Operating System (WMI) | Build | | OperatingSystemCrossPlatform (static) | Version | For example, ![Business Unit Filter](https://2503798551-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7VJNM00p5XQ4pMWqCu8y%2Fuploads%2Fgit-blob-8308d057f95ce1e232f04a3f16338b26db6f3ba4%2Fbusiness-unit-filter.png?alt=media) #### Unblock Windows Feature updates 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 Feature Upgrade (24H2) or Enablement Package (23H2 or 25H2). If you are upgrading to Windows 11 24H2, make sure to unblock the Windows 11 24H2 Data Files package as well. For more information about blocklisting see [Flex Controls - Blocklisting](/patch/patching-fundamentals/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-63a9960e16c9a8141ab3ddbf1db1b6308365f863%2Fblocklist.png?alt=media) 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 25H2 and 23H2) to the list of **Excluded Products** to ensure it does not get deployed by that Strategy. 1. Select **Advanced Settings > Flex Controls > Blocklisting > Blocked Patches**. * In version 10.0.971+, 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. ![](https://2503798551-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7VJNM00p5XQ4pMWqCu8y%2Fuploads%2Fgit-blob-7b746e5275d17638f8ad32a2970557a0384cc99d%2Fpatching-overrides-widget.png?alt=media) 2. In the View Blocked Patches pane, search for **windows** to view the available feature updates. ![](https://2503798551-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7VJNM00p5XQ4pMWqCu8y%2Fuploads%2Fgit-blob-ca269360c9b24ecff11f46f34688c17950e15658%2Fview-blocked-patches-windows.png?alt=media) 3. Search for the Feature Update version you wish to install, for example **Windows 11 25H2**. ![](https://2503798551-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7VJNM00p5XQ4pMWqCu8y%2Fuploads%2Fgit-blob-fc0b96a626890a39aa158c8cea1822b32e30e0b4%2Fcurate-blocked-patches.png?alt=media) 4. Click the ellipses (**...**) next to the patch name and select **Unblock**. * You should only unblock a single feature update/enablement package at a time. With Windows Feature Updates it does not adhere to supersedence a can potentially fail during installation. ![](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 25H2 and 23H2). ![](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 **Preview Targeted Patches** to verify which patches will be installed. 3. 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/patching-fundamentals/approval-requests.md) has been approved, you can monitor the progress with [Flex Control Cycles](/patch/patching-fundamentals/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. ![](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. ![](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 The requirement for Feature Update 25H2 is that the device needs to be at 24H2 and have at least applied the 2025-09 Monthly Cumulative Update ([KB5063878](https://support.microsoft.com/en-US/servicing/os/windows-11/2025/09/september-9-2025-kb5065426-os-build-26100-6584)). **Solution** The UBR value should be 5074 or higher. The UBR (Update Build Revision) is the final part of a Windows version number that indicates the latest cumulative update installed on the system. In the run line, type **WinVer** and press **Enter**. The last number of the build version is the UBR. Ensure that this number is build 5074 or higher. ![Winver](https://2503798551-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7VJNM00p5XQ4pMWqCu8y%2Fuploads%2Fgit-blob-69ae06a16ed29a05f647b1bd2c1c6b714629029d%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 or 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** 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