@zwl29107 I haven't seen you for a long time. I was wondering if you created the new lcu files for 25398?
There is two different EnterpriseG builds. One is reconstructed build that users share here can be example=enterpriseg_19041_x64.7z or something else. You take it and build your EnterpriseG from any build. The other is original CMGE V2020-L (V2022-L.1345) iso. At first i took original CMGE V2020-L (V2022-L.1345) build edited productpolicy and changed EnterpriseG-ppdlic.xrm-ms with the one inside reconstrcution pack users shared here (maybe i have not changed the file i do not remember but i remember i did not edited it). I do not know if the user that prepared reconstruction pack edited the EnterpriseG-ppdlic.xrm-ms file or not but i have not edited it. If the repacker change the xrms file manifest file and file hash will not mismatch, it will give hash mismatch error when adding package. So i did not think the xrms file edited. So i concluded CMGE V2020-L (V2022-L.1345) can be different! and editing only productpolicy can be enough. Thats all.
You prefer to disable sppsvc. Whatever written in there will not be your problem because windows licensing service will not work and check them. Do not bother
You can combine with custom gpo to mimic features ... Copilot apps are only custom link to open webs apps... supermium with custom link same experience on windows Xp as windows 11 with official copilot , for remote desktop use wrapper Specific product policy are light
For now I'm downloading 19041.1 en-US amd64 to test EnterpriseG Meanwhile, I have my doubts, in Windows 11 21H2 (22000.1) sessions.xml I see that there is StarterEdtion, does anyone have any idea how to rebuild it? Using Starter Packages from 15063.0? Spoiler: sessions.xml Code: <?xml version="1.0" encoding="utf-8" ?> <Sessions> <Session version="8.0" id="3088_275046" client="Cbss" options="0" currentPhase="1" lastSuccessfulState="Complete" pendingFollower="false" retry="false" operationCovered="1025" correlationVector="wC7ko0RmKk6iGMI7.0" Queued="2021/06/05/12:01:26" Started="2021/06/05/12:01:26" Complete="2021/06/05/12:14:17" status="0x0"> <Tasks> <Phase seq="1"> <package id="Microsoft-Windows-StarterEdition~31bf3856ad364e35~amd64~~10.0.22000.1" name="Windows Starter Edition" targetState="Installed" options="0"/> <package id="Microsoft-Windows-CoreEdition~31bf3856ad364e35~amd64~~10.0.22000.1" name="Windows Core Edition" targetState="Staged" options="9"/> <package id="Microsoft-Windows-CoreCountrySpecificEdition~31bf3856ad364e35~amd64~~10.0.22000.1" name="Windows CoreCountrySpecific Edition" targetState="Staged" options="9"/> <package id="Microsoft-Windows-EnterpriseEvalEdition~31bf3856ad364e35~amd64~~10.0.22000.1" name="Windows EnterpriseEval Edition" targetState="Staged" options="9"/> <package id="Microsoft-Windows-EnterpriseSEdition~31bf3856ad364e35~amd64~~10.0.22000.1" name="Windows EnterpriseS Edition" targetState="Staged" options="9"/> <package id="Microsoft-Windows-EnterpriseSEvalEdition~31bf3856ad364e35~amd64~~10.0.22000.1" name="Windows EnterpriseSEval Edition" targetState="Staged" options="9"/> <package id="Microsoft-Windows-PPIProEdition~31bf3856ad364e35~amd64~~10.0.22000.1" name="Windows PPIPro Edition" targetState="Staged" options="9"/> <package id="Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.22000.1" name="Windows Professional Edition" targetState="Staged" options="9"/> <package id="Microsoft-Windows-EnterpriseGEdition~31bf3856ad364e35~amd64~~10.0.22000.1" name="Windows EnterpriseG Edition" targetState="Staged" options="9"/> </Phase> </Tasks> <Actions>
EnterpriseG are useless... use regular enterprise.... and copy admx + adml to policy definitions folder and after use restore gpo with lgpo .... similar as enterpriseG without stupid language restriction Nb for windows 11 use iot enterprise 24h2 as base to bypass stupid requirement without modification
Maybe balanadi post page-3 #43 can help with activation. Have a look in 15063.0_Core-to-Starter_amd64_Activated_Updatable.zip\files\mum\ to understand activation crack that is in there
I guess it should be SPP, right? then I should edit Microsoft-Windows-EditionSpecific-Starter-Package~31bf3856ad364e35~amd64~~10.0.15063.0.mum again and add the SPP of 15063.0 core to starter.. I'll try it in a while, thanks for the tip Ace2
Interesting, indeed! What about 26100.1? What is a main difficulty - reconstructed Starter image doesn't boot, or installed OS doesn't activate?