You have to think that Microsoft is going to launch a different version of the existing 17134.1 .. to vary the story of never ending ..... and then come with the same reports of mini-bugs etc etc ... (the same as in previous editions of windows 10)
Don't use MCT and tell the UUP/ESD to ISO converter by @abbodi1406 to create ISO with install.wim ... Task completed .
What's not official here? The ESDs that also get downloaded by MCT (even after GA) or the UUPs that are used by Windows Update itself to upgrade the users systems all over the world???
Like the MDL solutions even MCT uses the Windows own Dism API to create ISO from ESDs. Since one knows the files are directly from MS Servers where's the probölem? The 'homebrew' problem is only related to the fact the created ISOs will always show a different hash which isn't compareable. Doesn't disqualify them from being completely legit.
It's not official until it's served openly by Microsoft, accepting CUs through WU and with full removal of "managed by Insider". Look, we understand it's gonna be the same build. We know that. It doesn't diminish the work put by people to make ESD to ISO converters and so on. It's just that people want a proper Windows 10 that doesn't require registry hacks to turn off settings and can install updates the normal way, not through powershell.
And the 17134.1 aka 1803 iso will still be the same as the 17134.1 UUP and the 17134.1 ESD, so a proper windows 10 will only exist when the first CU is perfect and resolves all existing bugs, it wasn't and it will never happen
Why do people join this forum then? Isnt it like, they shouldnt care about MDL at all when they want it the normal way anyways and get their news from the official blog/news sites about updates? There will be another CU anyways to get rid of the "insider stuff" (Which is only shown on privacy, feedback?). But another question: Was that the case on any build in history? That MS released 2 different builds which are the same? So for this example, we would get 2x 17134.1 (One "leaked" and one from MCT), what would be the difference? Or would you say that build 17134.1 from MCT wont have the "Insider stuff" in the privacy settings?
They can't, because a different version wouldn't have had the same testing as the build Insiders have had.
But the version they serve up Monday will be identical to the one people here have been using. The registry hacks etc you refer to have nothing to do with the version installed. The version produced from ESD files will still receive Windows Updates in the normal way, once MS make them publically available. If MS released a different build Monday, it would mean it was UNTESTED.
That's impossible to answer accurately for everyone, but I can answer for myself. If you take a look you'll see I've joined somewhat "early", in 2009. The forum was "emergent" back then, but still arguably the best Windows activation website. Thing is, Windows activation is something you do quite rarely. So you'd look for the latest Daz activator, and be done for months. Years later, I had a Lenovo laptop that I was afraid to reflash (for the SLIC Windows 7 trick), and yet again, I found help here, for which I am grateful. Windows 10 activation is well, no longer something tricky like a BIOS mod, you're attaching a licence to an account and you're done. So I'd say all of this is constitute a very good reason to be a member here. Might not be one with hundreds of post and contributions, but hey, that's not required to post or see the topics, which is another reason this forum is great. People have different reasons to do stuff. By the way, I have 17134 on a USB for days now. Still on 17133 which is stable for me. I KNOW that it's gonna be what Microsoft will make available later today, 99.9%. Now I'll just wait and see what happens when people install it and if a CU will be available for it to remove the Insider stuff. Not in a hurry, but still mildly excited, not because this Windows version offers anything interesting, but because it's something "new". I see no reasons to jump on 17134 if 17133 is stable, other than the insider stuff being gone and WU working normally.
WU already works as intended. In RTM process CUs are always released to active insiders first, to assure the process is working. With GA the CUs get released to the official channel.
The ESD and WIM are the same file just in a different form. Its like saying that a PNG converted into a BMP is no longer the official picture.