[GUIDE] [DISCUSSION] Windows Editions Reconstructions

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

  1. Low Level Perform

    Low Level Perform MDL Novice

    Jul 21, 2024
    34
    20
    0
    Microsoft-Windows-EditionSpecific-EnterpriseS-Package disappear from uupdump
     
  2. liliactr

    liliactr MDL Addicted

    Sep 3, 2009
    530
    188
    30
    Which build number?
     
  3. Low Level Perform

    Low Level Perform MDL Novice

    Jul 21, 2024
    34
    20
    0
    all builds.
    A year ago I could still take it freely.
    maybe you have used another method?

    Code:
    34f76a5b1708260506e3390095cc4912d0838e71 *Microsoft-Windows-EditionSpecific-Core-Package.ESD
    0b5262ba614d03f6bbba20afeb01049a7d92be80 *Microsoft-Windows-EditionSpecific-Core-Package.cab
    b41f998f49ea0afe5b2eb56ed02d5f02b7f76e65 *Microsoft-Windows-EditionSpecific-CoreCountrySpecific-Package.ESD
    12828c6572c88cc78a91464163dc0bcb78f78de1 *Microsoft-Windows-EditionSpecific-CoreCountrySpecific-Package.cab
    8a45be128043173f9464e1503a59243fc433a33b *Microsoft-Windows-EditionSpecific-CoreN-Package.ESD
    c74ad8415ff3f1f6cba34bcd80ca9187dca14645 *Microsoft-Windows-EditionSpecific-CoreN-Package.cab
    3d4eeb09e44ee6febe1d951a2632fdb81a28a275 *Microsoft-Windows-EditionSpecific-EnterpriseEval-Package.ESD
    cc6f4c4a3b96e778d624c703306b77f664727b2f *Microsoft-Windows-EditionSpecific-EnterpriseEval-Package.cab
    0ce59cb8993cef7c4f4757f4258c2919414a0019 *Microsoft-Windows-EditionSpecific-EnterpriseG-Package.ESD
    a8da084952a77f757e79d56c3bcd9a5738f8dfb9 *Microsoft-Windows-EditionSpecific-EnterpriseG-Package.cab
    b65fcf7eac999fd3e6ee7fbd595f770259161067 *Microsoft-Windows-EditionSpecific-EnterpriseGN-Package.ESD
    48c7795192d3d78ccbecc43686cccfade415c66e *Microsoft-Windows-EditionSpecific-EnterpriseGN-Package.cab
    2ceea6c473a84c86d616a4223c18a5aef1b2c332 *Microsoft-Windows-EditionSpecific-EnterpriseNEval-Package.ESD
    cfe682764c33b8fc0b92ff303adc5698848e81b0 *Microsoft-Windows-EditionSpecific-EnterpriseNEval-Package.cab
    2ca0e3be317543da9b310fe6fd35570fe18bab0c *Microsoft-Windows-EditionSpecific-PPIPro-Package.ESD
    6460e0d488501d9c02dc40beb20ba985279a8856 *Microsoft-Windows-EditionSpecific-PPIPro-Package.cab
    2cb220d675d402ce284ed21c9da53c1fd0e47a54 *Microsoft-Windows-EditionSpecific-PPIPro-WOW64-Package.ESD
    0a0e7cfd833f3ecb1654f7c706bb3bfce1f78337 *Microsoft-Windows-EditionSpecific-PPIPro-WOW64-Package.cab
    5a3c87eca6b214ff71a802527acb6a3312ca6e38 *Microsoft-Windows-EditionSpecific-Professional-Package.ESD
    7cd73695b4aad41baab5a45d69394d0bc91b8319 *Microsoft-Windows-EditionSpecific-Professional-Package.cab
    395bf68bd3edc63d4bf4f4898ef8ca9bdf2c5814 *Microsoft-Windows-EditionSpecific-Professional-WOW64-Package.ESD
    237d9dbafc1eb888f1e0cb6b74474aa4edd3be66 *Microsoft-Windows-EditionSpecific-Professional-WOW64-Package.cab
    bda2de4f8e050adda294e533a8c9aa7a5260bc80 *Microsoft-Windows-EditionSpecific-ProfessionalN-Package.ESD
    c3f75e91128a68bdcee7d16dbaa1e305a89441e6 *Microsoft-Windows-EditionSpecific-ProfessionalN-Package.cab
     
  4. liliactr

    liliactr MDL Addicted

    Sep 3, 2009
    530
    188
    30
    I forgot enterprises never publised at uupdump. It is normal. You mixed in mind with EnterpriseG i think.
     
  5. pp03

    pp03 MDL Addicted

    Apr 12, 2014
    566
    94
    30
    #685 pp03, Oct 24, 2024
    Last edited: Oct 24, 2024
    i've checked that sizes of on-demand packages from 26100 lof.iso and uupdump are the same, so i'll try 26100 pro to entsneval script with language pack (bigger size) from mentioned iso
     
  6. pp03

    pp03 MDL Addicted

    Apr 12, 2014
    566
    94
    30
    #686 pp03, Oct 24, 2024
    Last edited: Oct 25, 2024
    unfortunately still the same: explorer, searching and right-click context menu are not working, menu start button is not visible.

    where is the problem? keep looking for...
     
  7. TesterMachineOS

    TesterMachineOS MDL Addicted

    Apr 20, 2021
    567
    264
    30
    What version of 26100 are you building under?

    26100.1?
     
  8. pp03

    pp03 MDL Addicted

    Apr 12, 2014
    566
    94
    30
    #688 pp03, Oct 24, 2024
    Last edited: Oct 25, 2024
    yes

    ps. two errors in event viewer: Microsoft.Internal.FrameworkUdk.dll (explorer.exe) and searchhost.exe (combase.dll)
     
  9. TesterMachineOS

    TesterMachineOS MDL Addicted

    Apr 20, 2021
    567
    264
    30
    Later I will check the script, maybe there is some error that may not have been intentional, everyone makes mistakes.
     
  10. pp03

    pp03 MDL Addicted

    Apr 12, 2014
    566
    94
    30
    #690 pp03, Oct 25, 2024
    Last edited: Oct 25, 2024
    searchhost.exe is in systemapps\MicrosoftWindows.Client.CBS_cw5n1h2txyewy,

    Microsoft.Internal.FrameworkUdk.dll is in systemapps\Microsoft.WindowsAppRuntime.CBS_8wekyb3d8bbwe

    ps.
    with official ltsc n eval en-us iso in Microsoft.WindowsAppRuntime.CBS_8wekyb3d8bbwe there is en-us folder. i've checked that for example in en-gb iso there is corresponding folder.

    i don't remember if there is pl-pl folder after using script - i'll check that
     
  11. pp03

    pp03 MDL Addicted

    Apr 12, 2014
    566
    94
    30
    #691 pp03, Oct 25, 2024
    Last edited: Oct 25, 2024
    i'm starting to suspect something.
    probably there will be same situation as 19041 ltsc n eval.
    with this specific sku in 19041 version there was problem with taskbar icons, because shellexperiencehost package was missing (fileexplorer package also was missing in comparison to ltsc eval, but not required).
    in 26100 ltsc eval shellexperiencehost and fileexplorer packages are in systemapps unlike 26100 ltsc n eval.
    i'll check if solution will be to add shellexperiencehost only, fileexplorer only or both
     
  12. pp03

    pp03 MDL Addicted

    Apr 12, 2014
    566
    94
    30
    fileexplorer only - still the same
     
  13. pp03

    pp03 MDL Addicted

    Apr 12, 2014
    566
    94
    30
    #693 pp03, Oct 25, 2024
    Last edited: Oct 25, 2024
    shellexperiencehost only - still the same (at least action center is working - forgot to mention that it was broken too)

    trying both
     
  14. pp03

    pp03 MDL Addicted

    Apr 12, 2014
    566
    94
    30
    unfortunately still the same
     
  15. pp03

    pp03 MDL Addicted

    Apr 12, 2014
    566
    94
    30
    #695 pp03, Oct 25, 2024
    Last edited: Oct 25, 2024
    in official 26100.1742 polish ltsc n non-eval iso there is lkg package in systemapps with another searchhost.exe in lkg.search folder
     
  16. pp03

    pp03 MDL Addicted

    Apr 12, 2014
    566
    94
    30
    unfortunately still the same
     
  17. pp03

    pp03 MDL Addicted

    Apr 12, 2014
    566
    94
    30
    #697 pp03, Oct 26, 2024
    Last edited: Oct 26, 2024
  18. pp03

    pp03 MDL Addicted

    Apr 12, 2014
    566
    94
    30
    looks like it's not necessary to mount image and create panther folder with unattend.xml. it's enough to have unattend.xml in root of the bootable usb
     
  19. pp03

    pp03 MDL Addicted

    Apr 12, 2014
    566
    94
    30
    #699 pp03, Oct 27, 2024
    Last edited: Oct 27, 2024
    2021 version - one official ltsc eval iso
    2024 version - two official ltsc eval isos
     
  20. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,674
    14,412
    340
    #700 xinso, Oct 27, 2024
    Last edited: Oct 27, 2024
    Microsoft does not want end user to use "EnterpriseSNEval" Edition.

    This is why Microsoft always make it "Incomplete" in official releases, and CUs.

    If you want to use it, fine, just add the missing packages which should be defined in "Microsoft-Windows-EnterpriseSNEvalEdition~31bf3856ad364e35~amd64~~10.0.26100.X.mum". In both 26100.1 image and each CU. And, of course, install customized CU "Offline" only.

    e.g.

    Official Microsoft-Windows-EnterpriseSNEdition~31bf3856ad364e35~amd64~~10.0.26100.1.mum is with these three packages.
    Code:
        <update name="Microsoft-Windows-Media-Placeholder-Package">
          <package contained="false" integrate="hidden">
            <assemblyIdentity name="Microsoft-Windows-Media-Placeholder-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          </package>
        </update>
        <update name="Microsoft-Windows-Required-ShellExperiences-Desktop-Package">
          <package contained="false" integrate="hidden">
            <assemblyIdentity name="Microsoft-Windows-Required-ShellExperiences-Desktop-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          </package>
        </update>
        <update name="Microsoft-Windows-Required-ShellExperiences-Desktop-WOW64-Package">
          <package contained="false" integrate="hidden">
            <assemblyIdentity name="Microsoft-Windows-Required-ShellExperiences-Desktop-WOW64-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          </package>
        </update>
      </package>
    </assembly>
    
    Official Microsoft-Windows-EnterpriseSNEvalEdition~31bf3856ad364e35~amd64~~10.0.26100.1.mum is lacking aforementioned three packages.
    Code:
    Missing
    
    ---> Solution: Add these three packages back.
    Code:
        <update name="Microsoft-Windows-Media-Placeholder-Package">
          <package contained="false" integrate="hidden">
            <assemblyIdentity name="Microsoft-Windows-Media-Placeholder-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          </package>
        </update>
        <update name="Microsoft-Windows-Required-ShellExperiences-Desktop-Package">
          <package contained="false" integrate="hidden">
            <assemblyIdentity name="Microsoft-Windows-Required-ShellExperiences-Desktop-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          </package>
        </update>
        <update name="Microsoft-Windows-Required-ShellExperiences-Desktop-WOW64-Package">
          <package contained="false" integrate="hidden">
            <assemblyIdentity name="Microsoft-Windows-Required-ShellExperiences-Desktop-WOW64-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          </package>
        </update>
      </package>
    </assembly>
    
    So? You have to modify three mums in:

    3-1:
    26100.1 Image.

    3-2:
    26100.1742 Baseline CU. e.g. Windows11.0-KB5043080-x64-1742-Patched.esd.

    3-3:
    26100.XXXX Patchline CU. e.g Windows11.0-KB5044284-x64-2033-for-1742-Patched.esd.

    PS:
    Same for 19041.1. But, "USELESS", because the CUs from 19041.1200 forward do not support its old "KEY". i.e. After "rearm" in 270 days, activation will fail.
    (This issue happens on 19041 only.)