The Autopatch update policy provides a simple one click option to enable/disable offering hotpatch updates and handles the baseline orchestration to only offer to eligible devices. Device eligibility in this context requires precise OS version targeting because the hotpatch updates patch live code in memory for a specific OS version. Autopatch ensures customers get a simple friction free management of updates and baselines. The hotpatch updates will not install on an incorrect baseline but Autopatch means customers can avoid any frustration or extra burden trying to manually keep track of these important details.
One tip to get started: Create a new update policy to see the hotpatch enable/disable option. You can have both Windows 10 and Windows 11 devices in the same policy and Autopatch handles the orchestration to only offer this month's hotpatch to eligible Windows 11, v24H2 devices on (Build 26100.2033). If you have a test device on Windows 24H2 build greater than 26100.2033 you can uninstall the KB update to get back to Build 26100.2033 after which the device is eligible for hotpatch update announced at Ignite as well as next month's hotpatch update planned for December. Alternatively, if you have devices not on Build 26100.2033 in a hotpatch enabled policy and just wait, the next quarterly baseline is January with hotpatch updates planned for February and March.