Oh. It is another technology (different to dism command) splitting an image into multiple sub-packages. I can't find any information from the web.
You are right about that , but if you have the time to show the steps how to make a 19041.1 as a starter structure so i can updated for the future as i did it with the 19041.1 Core to Standalone . I always follow your master skills !!!
The Starter structure is shown in 19041.1 C:\Windows\servicing\Sessions\Sessions.xlm. Which contains only .Net Framework 4.8 (Microsoft-Windows-NetFx4-US-OC-Package) in Microsoft-Windows-EditionPack-Starter-Package Code: <Resolve package="Microsoft-Windows-EditionPack-Starter-Package~31bf3856ad364e35~amd64~~10.0.19041.1" update="a0533726923739b66e429ed866733ab4"/> <Resolve package="Microsoft-Windows-NetFx4-US-OC-Package~31bf3856ad364e35~amd64~~10.0.19041.1" update="NetFx4"/> All other packages are the same as other editions. The difficulty is being that Customized Updates is not easy for you. And I won't be available to provide each and every updates.
It is not the same like the 19041.1_Core_to_Standalone ? I always updated offline , if it is possible of course ...
No. Different. Standalone Core is in full original structure. Core in Starter structure is in reconfigured structure, not supported by original updates.
So to avoid the troubles in the future , it is way more easy to stay with the Lite Standalone Core created with your script , and updated normal way as i did it until now . i thought that being already inside the Sessions.xml we can create a standard Starter edition and updated monthly ... So far i am good with 19041.1_Core_to_Standalone_Lite_amd64 as long as i can updated when something important needs to be update ...
Sorry, but no. Starter is NOT supported by updates. (Microsoft always creates all Client editions based on Starter. And at the end, Mocrosoft deletes Starter and EnterpriseS from the image for SAC.)
The easiest way for EnterpriseS is add EnterpriseS license folder to Core. Thus it can get updated. Like dorfd1 does. https://forums.mydigitallife.net/th...nstruction-project.80939/page-87#post-1645920 It will be in full structure of Core. But activated as EnterpriseS, together with EnterpriseS Product policy.
How to do it exactly , and where .. What about 19042.631.201119-0144.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x64FRE_en-us ..it is the original image downloaded from microsoft , can this one be used ?
Another Master you can ask: zhanglin. He is good at making "dism /online (/image:C:\MOUNT) /get-currentedition" work for such workaround. (Nothing to do with features. Just for peace of mind, or good-looking.) Real EnterpriseS: CompositionEditionID = EnterpriseS EditionID = EnterpriseS Edition-Switch (adding EnterpriseS license and key): CompositionEditionID = Core (Enterprise, etc.) EditionID = EnterpriseS
Q: To 19041.1 EnterpriseS image, which enablement hotfix should be installed for 21H1? A: Both 20H2Enablement (KB4562830) and 21H1Enablement (KB5000736) hotfixes. Q: How to check? A: Install latest update for "Windows Feature Experience Pack" (e.g. KB5000967) and goto Settings --> System --> About --> Windows Specification --> Check whether or not the version of "Windows Feature Experience Pack" is correct. (e.g. 120.2212.3030.0)
Unfortunately my knowledge can’t compare with yours here, I have EntG and EntS 19041.1, they were made by your instructions, but those were deleted and I was stupid enough not to write method down (