[ARCHIVED] Windows Editions Reconstruction Project

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

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

    Divu MDL Novice

    Jun 29, 2018
    45
    4
    0
  2. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,672
    14,410
    340
    #282 xinso, Jun 15, 2020
    Last edited: Jun 15, 2020
    Deleted
     
  3. Divu

    Divu MDL Novice

    Jun 29, 2018
    45
    4
    0

    xinso MDL Guru
    "I'll test the new one with es-ES. If no problem I'll upload again"

    Waiting. Thanks
     
  4. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,672
    14,410
    340
    #284 xinso, Jun 15, 2020
    Last edited: Jun 15, 2020
    Deleted
     
  5. Divu

    Divu MDL Novice

    Jun 29, 2018
    45
    4
    0
  6. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,672
    14,410
    340
  7. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,672
    14,410
    340
    #288 xinso, Jun 15, 2020
    Last edited: Jun 15, 2020
    If you don't need Brand infomation, remove "call brand.cmd || exit /b 1" from full_build.cmd.
     
  8. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,672
    14,410
    340
    The complete wim infomation should be like this:

    <NAME>Windows 10 Enterprise G</NAME>
    <DESCRIPTION>Windows 10 Enterprise G</DESCRIPTION>
    <FLAGS>EnterpriseG</FLAGS>
    <DISPLAYNAME>Windows 10 Enterprise G</DISPLAYNAME>
    <DISPLAYDESCRIPTION>Windows 10 Enterprise G</DISPLAYDESCRIPTION>
     
  9. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,672
    14,410
    340
    #290 xinso, Jun 15, 2020
    Last edited: Jun 15, 2020
    Yes, I noticed that too.

    wimlib-imagex info install.wim 1 "Windows 10 Enterprise G" "Windows 10 Enterprise G"

    <NAME>Windows 10 Enterprise G</NAME>
    <DESCRIPTION>Windows 10 Enterprise G</DESCRIPTION>


    <FLAGS>Professional</FLAGS>
    <DISPLAYNAME>Windows 10 Pro</DISPLAYNAME>
    <DISPLAYDESCRIPTION>Windows 10 Pro</DISPLAYDESCRIPTION>
     
  10. asaltekan

    asaltekan MDL Novice

    May 24, 2016
    38
    22
    0
    @xinso
    Thanks xinso. your tips is more simple.

    Don't now, after succesfully convert install.wim to EntG, when i check install.wim with dism (get-wiminfo) still display Pro, not EnterpriseG.
    May i miss someting, as far i remember, in whole process there is no error notif displayed. Maybe i need try it again to make sure.
     
  11. Divu

    Divu MDL Novice

    Jun 29, 2018
    45
    4
    0
    #292 Divu, Jun 15, 2020
    Last edited: Jun 15, 2020
    ltsc_..png
    I make all work that member "xinso" indicate. But unfortunately the result is:windows LTSC...!!!!
    The activation [klm_vs_all] its only for 180 days.
     
  12. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,672
    14,410
    340
    #293 xinso, Jun 15, 2020
    Last edited: Jun 16, 2020
    The result is as expected.
     
  13. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,672
    14,410
    340
    #294 xinso, Jun 16, 2020
    Last edited: Jun 16, 2020
    No, you don't need to waste time trying it again to make sure. The script needs polishing up to solve this problem.
     
  14. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,672
    14,410
    340
  15. d5aqoëp

    d5aqoëp MDL Addicted

    Jan 19, 2017
    825
    614
    30
    Can anyone help me to create EnterpriseS ? I want to create from 2004 version.
     
  16. Divu

    Divu MDL Novice

    Jun 29, 2018
    45
    4
    0
    #297 Divu, Jun 16, 2020
    Last edited: Jun 16, 2020
    No EnterpriseS ? No activation like that EnterpriseG ? (Like : Enthousiast, post nr.10)
    I wanted for one edition bloatware free, no cortana, no edge, no telemetry...
    For LTSC is not necesary that work. We can download directly....I'm confuse !
     
  17. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,672
    14,410
    340
    #298 xinso, Jun 16, 2020
    Last edited: Jun 16, 2020
    No telemetry? EnterpriseG without Store. But EnterpriseG is avalable in en-US and\or zh-CN only.
     
  18. Ace2

    Ace2 MDL Expert

    Oct 10, 2014
    1,857
    1,520
    60
    #299 Ace2, Jun 16, 2020
    Last edited: Jun 16, 2020
    Too many fixes needed.:(

    Update
    Setup failed, black screen off death.

    My results
    Code:
    Microsoft Windows [Version 10.0.19041.264]
    (c) 2020 Microsoft Corporation. All rights reserved.
    
    C:\Users\User\Desktop\Tools\PowerRun>dism /image:C:\mount /apply-unattend:C:\EnterpriseS\1.xml
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.1
    
    Image Version: 10.0.19041.1
    
    [==========================100.0%==========================]
    The operation completed successfully.
    
    C:\Users\User\Desktop\Tools\PowerRun>dism /image:C:\mount /apply-unattend:C:\EnterpriseS\2.xml
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.1
    
    Image Version: 10.0.19041.1
    
    Removing package Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.19041.1
    Removing package Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.19041.1
    [==========================100.0%==========================]
    
    The operation completed successfully.
    
    C:\Users\User\Desktop\Tools\PowerRun>dism /image:C:\mount /apply-unattend:C:\EnterpriseS\3.xml
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.1
    
    Image Version: 10.0.19041.1
    
    [==========================100.0%==========================]
    The operation completed successfully.
    
    C:\Users\User\Desktop\Tools\PowerRun>del C:\mount\Windows\Professional.xml
    
    C:\Users\User\Desktop\Tools\PowerRun>del C:\mount\Windows\servicing\Editions\EnterpriseSEdition.xml
    
    C:\Users\User\Desktop\Tools\PowerRun>copy /y C:\EnterpriseS\EnterpriseSEdition.xml C:\mount\Windows\servicing\Editions\EnterpriseSEdition.xml
            1 file(s) copied.
    
    C:\Users\User\Desktop\Tools\PowerRun>dism /image:C:\mount /set-edition:EnterpriseS
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.1
    
    Image Version: 10.0.19041.1
    
    Starting to update components...
    Starting to install product key...
    Finished installing product key.
    
    Starting to apply edition-specific settings...
    Finished applying edition-specific settings.
    
    The operation completed successfully.
    
    C:\Users\User\Desktop\Tools\PowerRun>dism /image:C:\mount /get-currentedition
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.1
    
    Image Version: 10.0.19041.1
    
    Current edition is:
    
    Current Edition : EnterpriseS
    
    The operation completed successfully.
    
    C:\Users\User\Desktop\Tools\PowerRun>del C:\mount\Windows\servicing\Editions\EnterpriseSEdition.xml
    
    C:\Users\User\Desktop\Tools\PowerRun>copy /y C:\EnterpriseS\sxs\amd64_microsoft-windows-editions-client_31bf3856ad364e35_10.0.17763.1_none_50d477fcc05015c9\EnterpriseSEdition.xml C:\mount\Windows\servicing\Editions\EnterpriseSEdition.xml
            1 file(s) copied.
    
    C:\Users\User\Desktop\Tools\PowerRun>dism /image:C:\mount /cleanup-image /startcomponentcleanup
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.1
    
    Image Version: 10.0.19041.1
    
    [==========================100.0%==========================]
    The operation completed successfully.
    
    C:\Users\User\Desktop\Tools\PowerRun>sfc /scannow /offbootdir=C:\mount /offwindir=C:\mount\windows
    
    Beginning system scan.  This process will take some time.
    
    
    Windows Resource Protection did not find any integrity violations.
    
    C:\Users\User\Desktop\Tools\PowerRun>
    
    
    NOTES:
    1.
    Fixed dism /image:C:\mount /set-edition:EnterpriseS command.
    
    By replacing EnterpriseS.xml settings.
    <component name="Microsoft-Windows-Power-Policy-Definitions" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">
    
    With Professional.xml settings.
    <component name="Microsoft-Windows-Power-Policy-Definitions" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">
    
    2.
    Will not be able to update Windows 10 2004 EnterpriseS, because there are no EnterpriseS settings in Windows 10 2004 update cab.
     
  19. xinso

    xinso MDL Guru

    Mar 5, 2009
    13,672
    14,410
    340
    #300 xinso, Jun 16, 2020
    Last edited: Jun 17, 2020