[ARCHIVED] Windows Editions Reconstruction Project

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

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

    zhanglin MDL Expert

    Jan 11, 2018
    1,014
    552
    60
    Yes, sir. Use 17763 to modify and make 19041EnterpriseSEdition
     
  2. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,685
    14,419
    340
    #4142 xinso, Aug 7, 2021
    Last edited: Aug 7, 2021
    I think you need a double-check of it: The f\r binaries need extra corresponding registry? (Otherwise I would not have said "not easy" at #4134.)
     
  3. zhanglin

    zhanglin MDL Expert

    Jan 11, 2018
    1,014
    552
    60
    Haven't thought of how to do this?
    I still can't see the essence through the phenomenon, and more is to compare and observe to find out the law.
     
  4. zhanglin

    zhanglin MDL Expert

    Jan 11, 2018
    1,014
    552
    60
    "The f\r binaries need extra corresponding registry", can you give me more hints?
     
  5. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,685
    14,419
    340
    You answer this first:

    These four packages, you use 19041.1 or 17763.1?
    Code:
    Microsoft-Windows-Help-ClientUA-Enterprise-Package~31bf3856ad364e35~amd64~~10.0.17763.1
    Microsoft-Windows-SenseClient-Package~31bf3856ad364e35~amd64~~10.0.17763.1
    Networking-MPSSVC-Rules-EnterpriseEdition-Package~31bf3856ad364e35~amd64~~10.0.17763.1
    Server-Help-Package.ClientEnterprise~31bf3856ad364e35~amd64~~10.0.17763.1
    
     
  6. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,685
    14,419
    340
    #4146 xinso, Aug 7, 2021
    Last edited: Aug 7, 2021
    Normal PSFX LCU without binaries, will detect source and install f\n\r, then registry.
    The baseless, with both f\n\r, and also updated binaries, will install updated binaries, NOT f\n\r. So, there will be NO registry for f\n\r. Then, original LCU fails.

    Therefore, besides f\n\r in WinSxS, you have to
    1. compare registry with original image
    2. export corresponding registry information of f\n\r
    3. apply the registry to reconstructed image.

    You like to play registry, should be no problem.

    Hint:
    If you are lazy, simply copy originnal updated image's C:\Windows\System32\config to reconstructed image.
    1. copy f\n\r to WinSxS folders
    2. copy Config to C:\Windows\System32
     
  7. zhanglin

    zhanglin MDL Expert

    Jan 11, 2018
    1,014
    552
    60
    #4147 zhanglin, Aug 7, 2021
    Last edited: Aug 7, 2021
    Some packages of 19041 use 19041, and those that do not use 17763 are modified to 19041.
     
  8. zhanglin

    zhanglin MDL Expert

    Jan 11, 2018
    1,014
    552
    60
    It should be this location Windows\System32\config\COMPONENTS
     
  9. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,685
    14,419
    340
    #4149 xinso, Aug 7, 2021
    Last edited: Aug 7, 2021
    (Oh, now I know that you have your own Magic Box.)

    Good, try it - not enough, I think.
     
  10. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,685
    14,419
    340
  11. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,685
    14,419
    340
    #4151 xinso, Aug 8, 2021
    Last edited: Aug 8, 2021
    Q: Is 19044 21H2 IoTEnterpriseS fully accomplished?

    This build of 19044 IoTEnterpriseS is NOT the target one. The target one should be with functionalities of EnableSelectabilityForEdition for IoTEnterpriseS.

    e.g.

    Microsoft-Windows-Desktop-Required-ClientOnly-Removable-Package~31bf3856ad364e35~amd64~~10.0.22000.120
    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-Desktop-Required-ClientOnly-Removable-Package" version="10.0.22000.120" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <package identifier="Microsoft-Windows-Desktop-Required-ClientOnly-Removable" releaseType="Feature Pack">
        <update name="Microsoft-OneCore-SystemSettings-UserAccount">
          <selectable disposition="absent">
            <detectNone default="true" />
            <mum2:customInformation xmlns:mum2="urn:schemas-microsoft-com:asm.v3">
              <mum2:EnableSelectabilityForEditions>
                <mum2:EnableSelectabilityForEdition name="Microsoft-Windows-IoTEnterpriseSEdition" />
              </mum2:EnableSelectabilityForEditions>
            </mum2:customInformation>
          </selectable>
          <package contained="false" integrate="hidden">
            <assemblyIdentity name="Microsoft-OneCore-SystemSettings-UserAccount-Package" version="10.0.22000.120" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          </package>
        </update>
        <update name="Microsoft-Windows-MicrosoftEdgeDevToolsClient">
          <selectable disposition="absent">
            <detectNone default="true" />
            <mum2:customInformation xmlns:mum2="urn:schemas-microsoft-com:asm.v3">
              <mum2:EnableSelectabilityForEditions>
                <mum2:EnableSelectabilityForEdition name="Microsoft-Windows-IoTEnterpriseSEdition" />
              </mum2:EnableSelectabilityForEditions>
            </mum2:customInformation>
          </selectable>
          <package contained="false" integrate="hidden">
            <assemblyIdentity name="Microsoft-Windows-MicrosoftEdgeDevToolsClient-Package" version="10.0.22000.120" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          </package>
        </update>
        <update name="Microsoft-Windows-PEAuth-OneCore">
          <selectable disposition="absent">
            <detectNone default="true" />
            <mum2:customInformation xmlns:mum2="urn:schemas-microsoft-com:asm.v3">
              <mum2:EnableSelectabilityForEditions>
                <mum2:EnableSelectabilityForEdition name="Microsoft-Windows-IoTEnterpriseSEdition" />
              </mum2:EnableSelectabilityForEditions>
            </mum2:customInformation>
          </selectable>
          <package contained="false" integrate="hidden">
            <assemblyIdentity name="Microsoft-Windows-PEAuth-OneCore-Package" version="10.0.22000.120" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          </package>
        </update>
      </package>
    </assembly>
    
    Microsoft-Windows-Desktop-Required-SharedWithServer-Removable-Package~31bf3856ad364e35~amd64~~10.0.22000.120
    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-Desktop-Required-SharedWithServer-Removable-Package" version="10.0.22000.120" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <package identifier="Microsoft-Windows-Desktop-Required-SharedWithServer-Removable" releaseType="Feature Pack">
        <update name="Microsoft-Composable-PlatformExtension-AccountsControlExperienceModal">
          <selectable disposition="absent">
            <detectNone default="true" />
            <mum2:customInformation xmlns:mum2="urn:schemas-microsoft-com:asm.v3">
              <mum2:EnableSelectabilityForEditions>
                <mum2:EnableSelectabilityForEdition name="Microsoft-Windows-IoTEnterpriseSEdition" />
              </mum2:EnableSelectabilityForEditions>
            </mum2:customInformation>
          </selectable>
          <package contained="false" integrate="hidden">
            <assemblyIdentity name="Microsoft-Composable-PlatformExtension-AccountsControlExperienceModal-Package" version="10.0.22000.120" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          </package>
        </update>
        <update name="Microsoft-OneCore-SystemSettings-Devices">
          <selectable disposition="absent">
            <detectNone default="true" />
            <mum2:customInformation xmlns:mum2="urn:schemas-microsoft-com:asm.v3">
              <mum2:EnableSelectabilityForEditions>
                <mum2:EnableSelectabilityForEdition name="Microsoft-Windows-IoTEnterpriseSEdition" />
              </mum2:EnableSelectabilityForEditions>
            </mum2:customInformation>
          </selectable>
          <package contained="false" integrate="hidden">
            <assemblyIdentity name="Microsoft-OneCore-SystemSettings-Devices-Package" version="10.0.22000.41" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          </package>
        </update>
        <update name="Microsoft-OneCore-SystemSettings-NetworkMobileHandlers">
          <selectable disposition="absent">
            <detectNone default="true" />
            <mum2:customInformation xmlns:mum2="urn:schemas-microsoft-com:asm.v3">
              <mum2:EnableSelectabilityForEditions>
                <mum2:EnableSelectabilityForEdition name="Microsoft-Windows-IoTEnterpriseSEdition" />
              </mum2:EnableSelectabilityForEditions>
            </mum2:customInformation>
          </selectable>
          <package contained="false" integrate="hidden">
            <assemblyIdentity name="Microsoft-OneCore-SystemSettings-NetworkMobileHandlers-Package" version="10.0.22000.120" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          </package>
        </update>
        <update name="Microsoft-Windows-SensorDataService">
          <selectable disposition="absent">
            <detectNone default="true" />
            <mum2:customInformation xmlns:mum2="urn:schemas-microsoft-com:asm.v3">
              <mum2:EnableSelectabilityForEditions>
                <mum2:EnableSelectabilityForEdition name="Microsoft-Windows-IoTEnterpriseSEdition" />
              </mum2:EnableSelectabilityForEditions>
            </mum2:customInformation>
          </selectable>
          <package contained="false" integrate="hidden">
            <assemblyIdentity name="Microsoft-Windows-SensorDataService-Package" version="10.0.22000.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          </package>
        </update>
        <update name="Microsoft-Windows-UI-Shell-WindowTabManager">
          <selectable disposition="absent">
            <detectNone default="true" />
            <mum2:customInformation xmlns:mum2="urn:schemas-microsoft-com:asm.v3">
              <mum2:EnableSelectabilityForEditions>
                <mum2:EnableSelectabilityForEdition name="Microsoft-Windows-IoTEnterpriseSEdition" />
              </mum2:EnableSelectabilityForEditions>
            </mum2:customInformation>
          </selectable>
          <package contained="false" integrate="hidden">
            <assemblyIdentity name="Microsoft-Windows-UI-Shell-WindowTabManager-Package" version="10.0.22000.51" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          </package>
        </update>
      </package>
    </assembly>
    
     
  12. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,685
    14,419
    340
    #4152 xinso, Aug 8, 2021
    Last edited: Aug 8, 2021
    Q: How to port 19041's own ChromiumEdge to EnterpriseS without installation traces?

    If there is a way, not bad, even if it is not the latest. We want integration method, not Edge.
     
  13. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,685
    14,419
    340
    #4153 xinso, Aug 8, 2021
    Last edited: Aug 8, 2021
    Q: Is it wise to extract a cab+psf file directly into a cab?
    A: Theoretically, it has 2 GB limitation for a single cab. But practically it fails far ahead of reaching 2 GB.
     
  14. Tarsynear

    Tarsynear MDL Senior Member

    Jan 4, 2021
    303
    123
    10
    #4154 Tarsynear, Aug 8, 2021
    Last edited: Jun 12, 2022
    Reserved.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  15. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,685
    14,419
    340
    #4155 xinso, Aug 8, 2021
    Last edited: Aug 8, 2021
    Good for you.

    I'm afarid that, in the future, Windows may go tri-generation way:
    19044 LTSC Client
    20348 LTSC Server
    22000 AC Client
    3xxxx AC Insider Preview
    -->
    20348 LTSC Client
    22000 LTSC Server
    3xxxx AC Client
    4xxxx AC Insider Preview

    OutCome:
    No chance porting packages among different systems.
     
  16. biorpg

    biorpg MDL Novice

    Jul 18, 2010
    33
    14
    0
    Wouldn't there still be some overlap here? Even if we get it a bit late?
     
  17. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,685
    14,419
    340
    #4157 xinso, Aug 8, 2021
    Last edited: Aug 8, 2021
    How could I know?

    All I know is even 20348 for Server, but actually there are 20348 Client images, alike 19041 EnterpriseS.
     
  18. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,685
    14,419
    340
    #4158 xinso, Aug 8, 2021
    Last edited: Aug 8, 2021
    I can't find edge.wim in 22000.1 packages alike Server 2022.
     
  19. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,685
    14,419
    340
    #4159 xinso, Aug 9, 2021
    Last edited: Aug 9, 2021
    Yesterday, I posted my registry solution for EdgeUpdate integration.

    Now that Server 2022 and Windows 11 do not have edge.wim, can we port 19041.1 or 22000.1 Internet Browser package as EdgeUpdate solution?

    PS.
    LTSC, either Client or Server does not have Edge in SKU structure, therefore it is added on manually by Microsoft.


    I think it is Internet Browser package being missing in LTSC builds so that the reconstructed LTSC image won't have ChromiumEdge automatically ported from Pro.

    If I am right, oh... Add Internet Browser package to 19041.1 mum. Solved.

    Wait! The 19041.1 does not have ChromiumEdge! So, after all, my solution is the best ever.
    https://forums.mydigitallife.net/th...struction-project.80939/page-208#post-1680810
     
  20. kibkalo

    kibkalo MDL Expert

    Sep 8, 2009
    1,025
    362
    60
    You were talking about OOBEEULA problem today,
    I have it when do EntS for a dual-language WIM for 1149
    Even using yours SXS package and/or yours Microsoft-Windows-EnterpriseS-SPP-Components-Package_31bf3856ad364e35_amd64__10.0.19041.1149.cab
    regardles of which language I choose on setup.
    I tried applying 1151 before creating VM. It doesn't work with normal cab, but baseless apply perfectly.
    Since same OOBEEULA
    Any hints?