In my case, I do see 26100.1656 offered - and it does install without reboot. But same moment, KB503894 (2024-07 .net update) is offered - and it does require reboot. What is a way to prevent installation of non-Hotpatch updates?
The answer was - .NET 2024-07 is a prerequisite, same as LCU 1150. If it is installed, next .NET updates are not offered on hotpatch channel What about Client 24H2? What if we repeat same steps on 26100 Windows 11? I would recommend to add to Code: [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Update\TargetingInfo\DynamicInstalled\Hotpatch.amd64] "Source"="Hotpatch Product" "Version"="10.0.26100.1"
Hm, not sure about that. I'd think that regular .NET updates will be available through WU, and hotpatching documentation mentions that installing these can require a reboot: aka.ms/hotpatchdocs
True. Starting with 2024-08 .NET updates don't appear if hotpatch channel is selected. So 2024-07 might be manually added, or it would install and reboot. Starting 2024-08 it won't autoinstall
No, this way only applies to 2025, because it includes hotpatching in regular editions. On 2022 hotpatching is only available in "Azure edition" and has the additional prerequisite of running in Azure or Azure Stack HCI: learn.microsoft.com/en-us/windows-server/get-started/enable-hotpatch-azure-edition
My point was that if you don't install KB5039894 before making system hot-patchable, it would install and reboot. All later .NET updates (usually requiring reboots) won't display if hotpatch is enabled. Update Found that 26100.1150 is not a prerequisite, 26100.268 is. Installing it and enabling VBS and hotpatching does the trick Hotpatch LCUs KB5037970 (26100.500) and KB5039329 (26100.793) - both include "quarterly base" KB5036908 (26100.268). If I have 26100.268+, enable VBS and AllowRebootlessUpdates, hotpatch channel is only on Windows update. And .1150 was "quarterly update", similar to .268. You could install .500 and .793 with no reboots, but .1386 includes .1150 inside, which is not "hot", and if wasn't installed previously requires a reboot. I expect new hotpatch LCU in late september and late october. And a new quartely base early november. Late november hotpatch would include it and would require a reboot. Two next updates won't. Nice strategy!
It is not a part of it Microsoft-Windows-Hotpatch-Payload-Package and Microsoft-Windows-Hotpatch-Utility-Package are, but not Microsoft-Windows-Hotpatch-Targeting-Package or Microsoft-Windows-Hotpatch-Targeting-Gated-Package
Well, we haven't moved much there. I have done export of Payload and Utility packages before that. And I didn't find a way to reconstruct Hotpatch Targeting package. Have made client use server targeting - get updates from server channel, but yet not from the hotpatch channel, need one more step.