Another advantage with huynhlam2's "EnterpriseS_x64_19041.1_en-US" For those that do not want (Legacy and Chrome) Edge installed with the CU, just install 21H1 EP (not 21H2)
Lol No! With yours explain very clearly .Everyone who are interesting can easy reslove that missing package. (Apply for EnterpriseG also)
@xinso the problem of locking online accounts has appeared in version 19044.1348 entg. That's too bad.
Base on your resloved. I have an idea for fix that missing package by modify 1.2.3.xml: 1.xml <?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <servicing> <package action="stage"> <assemblyIdentity name="Microsoft-Windows-ProfessionalEdition" version="10.0.19041.1" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" /> </package> <package action="install"> <assemblyIdentity name="Microsoft-Windows-EnterpriseSEdition" version="10.0.19041.1" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" /> <source location="Microsoft-Windows-EnterpriseSEdition-Package-amd64-10.0.19041.1.cab" /> </package> </servicing> </unattend> 2.xml <?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <servicing> <package action="remove"> <assemblyIdentity name="Microsoft-Windows-ProfessionalEdition" version="10.0.19041.1" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" /> </package> <package action="remove"> <assemblyIdentity name="Microsoft-Windows-EnterpriseSEdition" version="10.0.19041.1" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" /> </package> </servicing> </unattend> 3.xml <?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <servicing> <package action="stage"> <assemblyIdentity name="Microsoft-Windows-EnterpriseSEdition" version="10.0.19041.21" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" /> </package> <package action="install"> <assemblyIdentity name="Microsoft-Windows-EnterpriseSEdition" version="10.0.19041.1" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" /> <source location="1\Microsoft-Windows-EnterpriseSEdition~31bf3856ad364e35~amd64~~10.0.19041.1.mum" /> </package> </servicing> </unattend>
That is a good idea for maybe other reasons, but using W10UI to update from LTSC 19041.1 to LTSC 19044.1381 20H2 EP I don't have Chrome Edge. Sometimes problems can be something you don't expect, like pre-integrating Net3.5 or resetting base. What I do have sitting on my taskbar is "Meet Now" WTF! I'm looking into how to turn that off (I'm sure it's simple). Spoiler: W10UI.inii Code: [W10UI-Configuration] Target =%~dp0_Target-folder\install.wim Repo =%~dp0_Updates DismRoot =dism.exe Net35 =0 Net35Source = Cleanup =1 ResetBase =0 LCUwinre =0 WinRE =1 SkipEdge =1 _CabDir =C:\W10UI\W10UItemp MountDir =C:\W10UI\W10UImount WinreMount =C:\W10UI\W10UImountre wim2esd =0 wim2swm =0 ISO =0 ISODir = Delete_Source =0 AutoStart =0
I made a script based your ReadMe and using the code style of whatever127's OP script. The script incorporates @Ace2's 4.xml and works perfectly. Later on today, I'll try out the script using your suggested 1,2,3 xml's. I'm happy to pm you a working script if you want to release it or I can post it here. Whatever you prefer. Thanks for your super solution!
I just right click on that icon and select "Hide". Or you can try from Xinso's Script: https://forums.mydigitallife.net/th...struction-project.80939/page-265#post-1701333
Or you can simple need fix only the 1.xml & 3.xml (revert remove&install to install&remove ) 1.xml: Code: <?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <servicing> <package action="install"> <assemblyIdentity name="Microsoft-Windows-EnterpriseSEdition" version="10.0.19041.1" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" /> <source location="Microsoft-Windows-EnterpriseSEdition-Package-amd64-10.0.19041.1.cab" /> </package> <package action="remove"> <assemblyIdentity name="Microsoft-Windows-ProfessionalEdition" version="10.0.19041.1" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" /> </package> </servicing> </unattend> 3.xml: Code: <?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <servicing> <package action="stage"> <assemblyIdentity name="Microsoft-Windows-EnterpriseSEdition" version="10.0.19041.21" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" /> </package> <package action="install"> <assemblyIdentity name="Microsoft-Windows-EnterpriseSEdition" version="10.0.19041.1" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" /> <source location="1\Microsoft-Windows-EnterpriseSEdition~31bf3856ad364e35~amd64~~10.0.19041.1.mum" /> </package> </servicing> </unattend>
I have to do some other things now, but I will test out your improvements and post my script here later today!
If you make a 19041.1 IOT LTSC 2021 install.wim using a Windows 10 Pro install.wim, does it have all the apps included with Windows Pro? If it does, it negates the point of a clean Windows install from the stripped-down LTSC.
For 19041.1 LTSC I remove all ProvisionedAppxPackages https://forums.mydigitallife.net/th...struction-project.80939/page-271#post-1703539
Fact1: Some System App needs Microsoft.VCLibs.140.00_14.0.27323.0_xXX__8wekyb3d8bbwe. Fact:2: Official image has not such dependency.
Hi Guys This is great work. Now we can finally make the image, the way we want it. Nice Just used huynhlam2, The Completely EnterpriseS 19041.1 Works like a charm But is possible to build it with another language from scratch ? Just made it from scratch, with my own language Nice Now MSMG toolkit, can do it's magic