I'm referring to what Microsoft made available via MSDN. Usually they make available an official ISO for en-gb, but I've seen no mention of it this time.
The 'RTM' term & concept is no more in Windows releasing schematic. MSFT (unofficially) abandoned that RTM term & concept years ago, from the very earlier stage of revamping Windows As a Service since the inception & development of Windows 10. Can anyone actually remember when did the last time MSFT 'officially' used that 'RTM' term anywhere? Any of there written statement /blogpost?
uh yeah ok so what is a Windows 10 Enterprise Windows Driver Kit then ? how does it differ from the waaaaaaay smaller wdk ?
ISO by svf = original MVS and contains more SKUs, can be verified by checksums ESD>ISO is always homebrew because it's a local conversion and will always be different For 19041.208 there is no ESD available atm.
true there is no ESD or ISO when you see a ISO for English x64 it be called Win10_2004_English_x64.iso
Added to the OP: Official 19041.208 MVS ISOs (SVF) by @GezoeSloog https://forums.mydigitallife.net/threads/windows-10-svf-repository.63324/page-202#post-1596213
If you look at that post, it says it contains x86, amd64 and arm64 WDK's. That is why the ISO is so large.
Added to the OP: SmartVersion | Tools + Scripts + Tutorials by @LostED https://forums.mydigitallife.net/threads/smartversion-tools-scripts.79415/
And finally, a half-baked built 208 was released as the official MSDN 20H1 ISO, with that horrible Disk Cleaning (NOT) bug still presented while the fix (build 264) already released. Why TF didn't they at least release build 264 as the official 20H1 ISO? I don't understand what's on their minds. Beyond stupidity if you ask me. I'm staying with 2019 LTSC.
The bugs are not real showstoppers but probably there is some more needed, now the isos are released to devs, maybe they now can fix it?
For people who don't read and learn all efforts to help will be useless and confusing. Maybe this is more helpful: https://forums.mydigitallife.net/threads/smartversion-tools-scripts.79415/page-4#post-1524751