Thanks! I don't really understand yet, how and what exactly do you plan to change, but appreciate you agree to try helping me!
Sorry for the delay in responding, I need the file "starter_15063.0_x64.7z" so I can rebuild the starter edition for Windows 10 LTSB (14393.0) Unless you have a script for that saved there.
Q: How to integrate App to 26100.1 install.wim? 26100.1... Microsoft.VCLibs.140.00_14.0.33519.0_x64__8wekyb3d8bbwe.Appx Microsoft.UI.Xaml.2.8_8.2310.30001.0_x64__8wekyb3d8bbwe.Appx Microsoft.SecHealthUI_8wekyb3d8bbwe.x64.appx Useless is Useless. Who is to do Mission:Impossible POSSIBLE? This time, I give you the chance. Very generous. pm67310? zhanglin?
Master, has 26100 changed something? I haven't tried that, but previous versions allowed using dism /Add-ProvisionedAppxPackage - with /skiplicense parameter?
OK Do you mean that update problem would appear in image, reconstructed with tampered license? Even in your reconstructions?
Official CU recognizes "Genuine", i.e. CU won't accept it. Unless the CU can be modified to skip its update, or zwl29107 would make new CU.
Clear. Problem is with localized G images, where license is tampered? With en-US there might be no problems updating?
Master, I am not attacking, I am studying only. I meant that if en-US is installed language, no problems with updates, but if we tamper license and add (or even don't add) other LPs, only custom CUs would go?