[GUIDE] [DISCUSSION] Windows Editions Reconstructions

You need to login to view this posts content.

 

Indeed, I see manifest of Microsoft-Windows-Hotpatch-Targeting-Gated-Package-amd64-10.0.26100.1 in HCI, but it can't be installed without Microsoft-Windows-Hotpatch-Targeting-Package
Actually I don't need it for Server Standard - it works nice without, I need Targeting to port to Client.
So please if you succeed exporting it, show me how please

 

I just created it if you have the manifest you can try that

<?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-Windows-Hotpatch-Targeting-Gated-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
<package identifier="Microsoft-Windows-Hotpatch-Targeting-Gated" releaseType="Feature Pack">
<update name="Microsoft-Windows-Hotpatch-Targeting-Gated-Package">
<component>
<assemblyIdentity name="Microsoft-Windows-Hotpatch-Targeting-Gated-Deployment" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS" />
</component>
</update>
</package>
</assembly>

Microsoft-Windows-Hotpatch-Targeting-Gated-Package~31bf3856ad364e35~amd64~~10.0.26100.1.mum

 

Does it need .cat? Where to find it?

 

You need to login to view this posts content.

 

Thanks, but that i

Well, that doesn't install unfortunately.
We need to port all the Hotpatch packages to client to make targeting work.
Without targeting we can manually install Hotpatch LCU with no reboot, but only real targeting package (not an empty one) would prevent Win11 to get updates from broad channel and reboot.

 

here is what we have available hotpatch.txt 7z

 

Dism /online /add-Package /PackagePath:C:\hotpatch.esd

hotpatch.txt esd

 

Thanks.
This one does install Utility and Payload - the packages, I was able to get via SxSv1.
But there is no Targeting files inside.
There must be some resource file (manifest?) installed by MUM below (file is from the old thread):

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-Windows-HotpatchTargeting-ServerOS" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS" />
  <registryKeys>
    <registryKey keyName="HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Update\TargetingInfo\DynamicInstalled\Hotpatch.amd64">
      <registryValue name="Version" valueType="REG_SZ" value="10.0.26100.1" />
      <registryValue name="Name" valueType="REG_SZ" value="Hotpatch Product" />
      <securityDescriptor name="WRP_REGKEY_DYNAMIC_INSTALLED_SDDL" />
    </registryKey>
  </registryKeys>
  <trustInfo>
    <security>
      <accessControl>
        <securityDescriptorDefinitions>
          <securityDescriptorDefinition name="WRP_REGKEY_DYNAMIC_INSTALLED_SDDL" sddl="O:SYG:SYD:P(A;CI;KA;;;S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464)(A;CI;KRKWSD;;;SY)(A;CI;KRKWSD;;;BA)(A;CI;KR;;;BU)(A;CI;KR;;;S-1-15-2-1)" operationHint="replace" />
        </securityDescriptorDefinitions>
      </accessControl>
    </security>
  </trustInfo>
</assembly>

But I can't get how to make it install
What is the name for assemblyIdentity name="Microsoft-Windows-HotpatchTargeting-ServerOS"?
How is it installed, and where the "ServerOS" is controlled

 

I found now, that if I delete the HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Update\TargetingInfo\Installed\Client.OS.rs2.amd64 key and import the HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Update\TargetingInfo\Installed\Server.OS.amd64 into Windows 11 26100.1, I now receive server-targeted updates:

Screenshot is made on client OS. I see updates for server OS (that's good), but I see the latest, not the Hotpatch one.
That once again brings us to the missing Hotpatch-Targeted package.
There might be some place in registry that does the magic
Ideas?
Can it be in binary keys TargetingAttributes and TargetingAttributesVerified in HKLM\SOFTWARE\Microsoft\WindowsSelfHost\OneSettings\ ?

 

Can you share add script to create windows 11 25398 pro sku in english

And add instruction ( last version of windows 11 without sse 4.2 , limited to pro sku and english only for supported update )

If others edition or language => only choice are windows 11 23h2 Enterprise ( for longuer update )

 

Do you need script or ISO?
PM me, would send links

 

kibkalo

did you install the lang pack after the hotpatch

 

I have exported Utility and Payload packages with SxSv1 from server - with language packages for them.
Thy are not in client langpack, so installation of full langpack is useless (and server langpack won't install)

 

Windows 11 26100.1150, VBS and Hotpatch are enabled, 6 packages are installed, registry modified to use server-targeting
In WU I see the latest LCU available for Server (for Client there is a newer one), nut it is not a Hotpatch update.
Need a Hotpatch-Targeting package, as said before. (

 

I share the hotpatch.zip again with 3 redone packages

Microsoft-Windows-Hotpatch-Payload-Package.esd
Microsoft-Windows-Hotpatch-Payload-WOW64-Package.esd
Microsoft-Windows-Hotpatch-Utility-Package.esd

delete the HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Update\TargetingInfo\Installed\Client.OS.rs2.amd64 key and import the HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Update\TargetingInfo\Installed\Server.OS.amd64 into Windows 11 26100.1, I now receive server-targeted updates:

 

No much change

No hotpatch targeting
As I said before:

So the question is not server-targeting, but hotpatch-targeting

 

I took the opportunity to install the iot ltsc

 

Nice. But have you tried to hotpatch it?
I mean from WU, - not installing MSUs.