amd64_microsoft-updatetargeting-clientos_31bf3856ad364e35_10.0.26100.500_none_ce722d7256461845 Code: <?xml version="1.0" encoding="utf-8" standalone="yes"?> <assembly xmlns="urn:schemas-microsoft-com:asm.v3" manifestVersion="1.0" copyright="Copyright (c) Microsoft Corporation. All Rights Reserved."> <assemblyIdentity name="Microsoft-UpdateTargeting-ClientOS" version="10.0.26100.500" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS" /> <registryKeys> <registryKey keyName="HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Update\TargetingInfo\Installed\Client.OS.rs2.amd64"> <registryValue name="Version" valueType="REG_SZ" value="10.0.26100.500" /> <registryValue name="Branch" valueType="REG_SZ" value="ge_release_svc_hotpatch_prod1" /> <registryValue name="PrimaryOSProduct" valueType="REG_SZ" value="1" /> <registryValue name="Repairable" valueType="REG_SZ" value="1" /> </registryKey> </registryKeys> <trustInfo> <security> <accessControl> <securityDescriptorDefinitions> <securityDescriptorDefinition name="WRP_REGKEY_DEFAULT_SDDL" sddl="O:S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464G:S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464D:P(A;CI;GA;;;S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464)(A;CI;GR;;;SY)(A;CI;GR;;;BA)(A;CI;GR;;;BU)(A;CI;GR;;;S-1-15-2-1)(A;CI;GR;;;S-1-15-3-1024-1065365936-1281604716-3511738428-1654721687-432734479-3232135806-4053264122-3456934681)" operationHint="replace" /> </securityDescriptorDefinitions> </accessControl> </security> </trustInfo> </assembly> and regedit settings after installing Windows11.0-KB5037970-Hotpatch-x64.cab Code: [HKEY_LOCAL_MACHINE\SOFTHIVE\Microsoft\Windows NT\CurrentVersion\Update\TargetingInfo\Installed\Client.OS.rs2.amd64] "Branch"="ge_release_svc_hotpatch_prod1" "PrimaryOSProduct"="1" "Repairable"="1" "Version"="10.0.26100.500" Hotpatch will install "Version"="10.0.26100.500" update with the help of Wrapper for 26100.1 and Shared.mum deployment.manifest because name="Microsoft-UpdateTargeting-ClientOS" version="10.0.26100.500" setting are in them as well.
Code: "ARCHotpatchAttached_State": { "HKey": "HKEY_LOCAL_MACHINE", "FullPath": "SOFTWARE\\Microsoft\\Azure Connected Machine Agent\\Windows\\Licenses\\Features\\Hotpatch", "ValueName": "Subscription", "RegValueType": "REG_DWORD" }, (HotPatchEKB = 20349) Code: "HotPatchEKBInstalled": { "HKey": "HKEY_LOCAL_MACHINE", "FullPath": "SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Update\\TargetingInfo\\DynamicInstalled\\Hotpatch.amd64", "IfExists": true }, For the first one, I don't know on which versions it can enable Hotpatch. The second one is only valid for 20348.
1. Yes. It is 19041.1 activated with 17763.1 License and Key. 2. Last night, I tested remove "19044.1288" License packages, and installed 17763.1 ones. After installation, it activated with a "New Key - different to 17763" automatically. PS: 1. CU and Key will fail if it is been "updated" by all means. 2. 19044.1288 default Key is inherited from 17763.1. i.e. Microsoft does not renew it. Well, 19044.1288 failed now. And I cannot remember how exactly (the sequences) did I make it.
so how to make 19041.1 ltsc eval? i've tried to do that with abbodi enterprise s build 19041.1 script by replacing cat and mum files, but some manifest files are missing (if i'll get them from .1288 and rename to .1 it'll be hash mismatch i guess) or alternatively how to remove .1288 license packages and install 17763.1 ones?
Thanks for ideas, can you give some comments - How to make Windows Update on Windows 11 24H2 see only Hotpatch channel updates, similar to WS2025? With the above keys server 2025 does see only hotpatch channel updates, but Client still checks broad channel updates/
I don't know. As far as I know, MS has not officially released any Hotpatch for Client yet. Although they are available on UUP, they must be fetched by sending information that means 'The current version is already the specified Hotpatch version' to the server.
@zwl29107 That's not the problem, as seen in the picture, instead of writing 25398.1085, it says 25398.1 as if it has not been updated.