[GUIDE] [DISCUSSION] Windows Editions Reconstructions

Discussion in 'Windows 10' started by TesterMachineOS, Sep 3, 2024.

  1. winosr25

    winosr25 MDL Member

    May 14, 2024
    106
    51
    10
    yes but without result, windows restarted after each msu
     
  2. winosr25

    winosr25 MDL Member

    May 14, 2024
    106
    51
    10
  3. kibkalo

    kibkalo MDL Expert

    Sep 8, 2009
    1,025
    362
    60
    In my case, if I had .1150 preinstalled, VBS and Hotpatch turned on, I installed Hotpatch LCU (KB5041570) without reboot - manual MSU install:
    upload_2024-9-24_19-12-39.png
    upload_2024-9-24_19-12-47.png
    upload_2024-9-24_19-12-56.png
    No reboot.
    But if I check WU. I see regular updates that require reboot:
    upload_2024-9-24_19-13-31.png
    Even if I modify TargetingInfo to Server.OS.amd64 I still see WS2025 LCU (non Hotpatch)
    So WU Hotpatch targeting doesn't work, but Hotpatch installation (manual) does work without reboots.
    Again, we need Hotpatch-Targeting :)
     
  4. TesterMachineOS

    TesterMachineOS MDL Addicted

    Apr 20, 2021
    567
    264
    30
    #265 TesterMachineOS, Sep 24, 2024
    Last edited: Sep 24, 2024
    (OP)
    Can anyone pass me the EnterpriseSEdition.mum and cat file for Windows 11 24h2 26100.1?
    I just want to take its structure to make it look official and reconstruct it to see how it looks.

    I plan to use the files(Specific-Edition-EnterpriseS) from @liliactr and @kibkalo to make two different constructions and see their results.

    I like to do this kind of reconstructions more because it is more customizable and modifiable, applying your own style. :)
     
  5. liliactr

    liliactr MDL Addicted

    Sep 3, 2009
    530
    188
    30
    I shared cab files. They are already in there. You can open with winrar and extract them. You mean enterprises i think, not enterprise?

    I also do not know how this kind of cabs work. I have not backed up wow64 packages but built cab may contain them or not i am not sure. Also i am not sure if it installs wow64 mums if they have it or not but original esds looks same as i prepared. That's why i wrote test
     
  6. TesterMachineOS

    TesterMachineOS MDL Addicted

    Apr 20, 2021
    567
    264
    30
    Sorry, the translator put "Enterprise" instead of "EnterpriseS"
     
  7. TesterMachineOS

    TesterMachineOS MDL Addicted

    Apr 20, 2021
    567
    264
    30
    Don't worry, I'll check for any problems and report back here :) thanks for sharing
     
  8. kibkalo

    kibkalo MDL Expert

    Sep 8, 2009
    1,025
    362
    60
  9. winosr25

    winosr25 MDL Member

    May 14, 2024
    106
    51
    10
  10. Ace2

    Ace2 MDL Expert

    Oct 10, 2014
    1,857
    1,520
    60
    #272 Ace2, Sep 25, 2024
    Last edited: Sep 25, 2024
    for client we will need::
    Code:
    amd64_microsoft-windows-h..argeting-deployment
    amd64_microsoft-windows-h..htargeting-clientos
    as you can see in winosr25 post there is an update
    Code:
    amd64_microsoft-updatetargeting-clientos_31bf3856ad364e35_10.0.26100.793_none_ce13e2d0568c5a11.manifest
    looks like regedit settings should look some thing like this:
    Code:
    Windows Registry Editor Version 5.00
    
    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Hotpatch\Environment]
    "AllowRebootlessUpdates"=dword:00000001
    
    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Update\TargetingInfo\DynamicInstalled\Hotpatch.amd64]
    "Source"="UpdateOrchestrator"
    "Version"="10.0.26100.1"
    
    [HKEY_LOCAL_MACHINE\SOFTWARE\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.1"

    can't use this setting for 26100.1 as you will be offered a lower server version.
    Code:
    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Update\TargetingInfo\DynamicInstalled\Hotpatch.amd64]
    "Source"="UpdateOrchestrator"
    "Version"="0.0.0.0"

    as you can also see in Windows11.0-KB5036908-x64.msu [Windows 11, version 24H2 (26100.268) amd64] there is:
    Code:
    amd64_microsoft-updatetargeting-clientos_31bf3856ad364e35_10.0.26100.268_none_ce394a88566f932e.manifest
     
  11. winosr25

    winosr25 MDL Member

    May 14, 2024
    106
    51
    10
    iso creation with uup dump and hot patch
     

    Attached Files:

  12. kibkalo

    kibkalo MDL Expert

    Sep 8, 2009
    1,025
    362
    60
    There is no aim to add package.
    Hotpatch update can be installed without reboot without any prerequisites (just same LCU, VBS and Hotpatch enablement in registry, as on server).
    But still after installing .1386 (Hot, no reboot) if I check WU, I get broad channel updates, and a reboot on install.
    upload_2024-9-25_18-21-56.png
    Have you tested your ISO?
    You succeeded in creating installation that doesn't detect other LCUs??
     
  13. winosr25

    winosr25 MDL Member

    May 14, 2024
    106
    51
    10
    Microsoft-UpdateTargeting-ServerOS" version="10.0.26100.1

    decompressed.manifest
    and
    original.zip
     

    Attached Files:

  14. kibkalo

    kibkalo MDL Expert

    Sep 8, 2009
    1,025
    362
    60
    No, that is a package, shared in old thread by master xinso
     
  15. TesterMachineOS

    TesterMachineOS MDL Addicted

    Apr 20, 2021
    567
    264
    30
    Sorry for the inconvenience again. Do you know if this package was captured or rebuilt?

    So far it can be applied without problem in dism and I don't see any rebuilding problems, I just want to try to get the rebuild of W11 24H2 EnterpriseS to be completely official.

    because well, if it is a kind of custom rebuild, it is likely that the updates will not work.