[ARCHIVED] Windows Editions Reconstruction Project

Discussion in 'Windows 10' started by whatever127, Jan 10, 2020.

Thread Status:
Not open for further replies.
  1. gailium119

    gailium119 MDL Addicted

    Oct 12, 2021
    790
    510
    30
    Try using process monitor to check which file setup failed to load
     
  2. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,711
    14,436
    340
    #7662 xinso, Apr 26, 2022
    Last edited: Apr 26, 2022
    Thanks.
     
  3. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,711
    14,436
    340
    #7663 xinso, Apr 26, 2022
    Last edited: Apr 26, 2022
    Now, FOD and Store...

    Q: How to make Windows Setup install them?
    A: Mountain won't turn; you turn.
     
  4. example12345678912345678

    Dec 29, 2019
    569
    322
    30
    @xinso
    I'm trying to stage Windows 10 from 20348.1 UUP packages. I'm not sure about what is missing.
    I used files from 19100.1051 with replacing all 19100.1051 references into 20348.1.
    And I don't see any mistake in XML file.
     

    Attached Files:

    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. gailium119

    gailium119 MDL Addicted

    Oct 12, 2021
    790
    510
    30
    WHAT? You're trying to use Client Edition and SERVER langpack?
     
  6. dorfd1

    dorfd1 MDL Senior Member

    Sep 10, 2015
    276
    98
    10
  7. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    49,679
    103,542
    450
    The use of the online KMS server is set by the script you used to recreate the ISO.
     
  8. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,711
    14,436
    340
  9. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,711
    14,436
    340
  10. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,711
    14,436
    340
  11. Nack11

    Nack11 MDL Member

    Oct 30, 2021
    152
    21
    10
    22000.1 only have upload_2022-4-27_14-42-44.png
     
  12. Nack11

    Nack11 MDL Member

    Oct 30, 2021
    152
    21
    10
    i tried to find in the iso, but there is no files
     
  13. Nack11

    Nack11 MDL Member

    Oct 30, 2021
    152
    21
    10
    and in editionspecific
    upload_2022-4-27_14-45-11.png
     
  14. Nack11

    Nack11 MDL Member

    Oct 30, 2021
    152
    21
    10
    they are named Microsoft-Windows-EnterpriseGEdition~31bf3856ad364e35~amd64~~10.0.22000.1
     
  15. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,711
    14,436
    340
    #7676 xinso, Apr 27, 2022
    Last edited: Apr 27, 2022
    It is all 22000.1 with different update builds. You must use 22000.1, not 22000.9 in LCU.

    Download 19041.1 EnterpriseG from OP, then replace 19041.1 with 22000.1.

    Microsoft-Windows-EnterpriseGEdition~31bf3856ad364e35~amd64~~22000.1.mum
    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-EnterpriseGEdition" version="22000.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <package identifier="Windows EnterpriseG Edition" releaseType="Product">
        <update name="Microsoft-Windows-Foundation-Package">
          <package contained="false" integrate="visible">
            <assemblyIdentity name="Microsoft-Windows-Foundation-Package" version="22000.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          </package>
        </update>
        <update name="Microsoft-Windows-EditionSpecific-EnterpriseG-Package">
          <package contained="false" integrate="hidden">
            <assemblyIdentity name="Microsoft-Windows-EditionSpecific-EnterpriseG-Package" version="22000.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          </package>
        </update>
        <update name="Microsoft-Windows-Client-Desktop-Required-Package">
          <package contained="false" integrate="hidden">
            <assemblyIdentity name="Microsoft-Windows-Client-Desktop-Required-Package" version="22000.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          </package>
        </update>
        <update name="Microsoft-Windows-Client-Desktop-Required-WOW64-Package">
          <package contained="false" integrate="hidden">
            <assemblyIdentity name="Microsoft-Windows-Client-Desktop-Required-WOW64-Package" version="22000.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          </package>
        </update>
        <update name="Microsoft-Windows-Client-Features-Package">
          <package contained="false" integrate="hidden">
            <assemblyIdentity name="Microsoft-Windows-Client-Features-Package" version="22000.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          </package>
        </update>
        <update name="Microsoft-Windows-Client-Features-WOW64-Package">
          <package contained="false" integrate="hidden">
            <assemblyIdentity name="Microsoft-Windows-Client-Features-WOW64-Package" version="22000.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          </package>
        </update>
        <update name="Microsoft-Windows-EditionPack-Professional-Package">
          <package contained="false" integrate="hidden">
            <assemblyIdentity name="Microsoft-Windows-EditionPack-Professional-Package" version="22000.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          </package>
        </update>
        <update name="Microsoft-Windows-EditionPack-Professional-WOW64-Package">
          <package contained="false" integrate="hidden">
            <assemblyIdentity name="Microsoft-Windows-EditionPack-Professional-WOW64-Package" version="22000.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          </package>
        </update>
        <update name="Microsoft-Windows-RegulatedPackages-Package">
          <package contained="false" integrate="hidden">
            <assemblyIdentity name="Microsoft-Windows-RegulatedPackages-Package" version="22000.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          </package>
        </update>
        <update name="Microsoft-Windows-RegulatedPackages-WOW64-Package">
          <package contained="false" integrate="hidden">
            <assemblyIdentity name="Microsoft-Windows-RegulatedPackages-WOW64-Package" version="22000.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="22000.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="22000.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          </package>
        </update>
      </package>
    </assembly>
    
    PS:
    19041, 20348, and 22000 etc. are in same edition structure.
     
  16. Nack11

    Nack11 MDL Member

    Oct 30, 2021
    152
    21
    10
    i meant files for base are named Microsoft-Windows-EnterpriseGEdition~31bf3856ad364e35~amd64~~10.0.22000.1, not Microsoft-Windows-EnterpriseGEdition~31bf3856ad364e35~amd64~~10.0.22000.9. how whatever got the files for base (19041 (and he left MDL as of Whatever's status and activity))
     
  17. Nack11

    Nack11 MDL Member

    Oct 30, 2021
    152
    21
    10
    i will test in 22000.9 wim, and files for 22000.9, as of uup files lcu
     
  18. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,711
    14,436
    340
    #7679 xinso, Apr 27, 2022
    Last edited: Apr 27, 2022
    Reconstruction needs "INITIAL" build, i.e. 22000.1, not 22000.9 nor other UBR.

    18363.2212 --> 18362.1 + 18362.2212 LCU + 18363 Enablement
    19044.1682 --> 19041.1 + 19041.1682 LCU + 19044 Enablement
    22000.9 --> 22000.1 + 22000.9 LCU

    [initial builds - BBR]
    10240.16384
    10586.0
    14393.0
    15063.0
    16299.15
    17134.1
    17763.1
    18362.1 (including 18363)
    19041.1 (including 19042\19043\19044)
    20348.1
    22000.1
     
  19. Nack11

    Nack11 MDL Member

    Oct 30, 2021
    152
    21
    10
    i said files for the (initial) base build.