EnterpriseS is the Enterprise LTSB 2015/2016/ LTSC 2019 EnterpriseSN is the Enterprise N LTSB 2015/2016/ LTSC 2019 LTSB ISO did contained EI.cfg with Edtion as EnterpriseS / EnterpriseSN
The VLSC en-US LTSC iso doesn't contain both, Non N and N like the MVS LTSC iso does. ei.cfg of the VLSC ISO (not containing N): Code: [EditionID] EnterpriseS [Channel] volume [VL] 1 ei.cfg of the MVS iso (containing both, non N and N): Code: [Channel] volume [VL] 1 The old 2016 LTSB has separate iso's for N and non N.
Even these: 37 languages in MVS for Consumer/Business and LTSC in two architectures sums up to ~210 ISOs to download first (not to mention the dozen Server ISOs), then create and upload the SVFs.
ms need to find solution for this each lang making new iso, just make it same how modeler puting in same folder the lang pack in the iso and change the display ui lang
It's time for you to learn that SHA-1 match doesn't absolutely mean you got two identical files any more.
It still is good for ISO's of this size and content, they only managed to this with a 150kb file, windows ISO will take many, many, many years to crack.
I did my best to try creating a refreshed LTSC image in en-gb language via SVF2ISO, but I keep hitting the roadblocks, and sadly I am bit tired for now after trying many times (either that or I am too new to the SVF thing). Probably try again when I have more energy, unless someone beats me to it. I think it currently requires specialist tools and a lot of patience to find a SHA-1 collision. Unless one is very very very lucky, the chance of forged signature is 0.000000000001% ! (lots of zeroes for emphasis)
You can't fake multiple checksums so if the SHA-1, SHA-256 and MD5 are all correct then it's basically 100% legit
You don't have to have any knowledge of the svf functioning, select the iso you desire and it will do all for you, automated.