Your post prompted me to take my investigation into another direction, and I think I found what the problem is, so thank you for that. It's a classic case of "it's not a bug, it's a feature". When Microsoft introduced the new "moderm" apps in Windows 8 and 10, it looks like they also introduced a new association mechanism, while keeping the old one in parallel for legacy apps. However, it looks like in the last few builds, they decided to thin out some legacy code, and redirect default associations for legacy apps transparently to the new mechanism. So if a file extension is not present in the default list of extensions in Settings, or if it is present but the app you're trying to associate it with is not offered in the list of alternate apps in Settings, then you simply cannot change the association through file explorer as well. In short: If it can't be done in Settings, it can't be done at all. The only solution is to play with registry keys (for example, I've copied the shell->open key of the "TIFImage.Document" type to the "jpegfile" type to allow associating .jpg and .jpeg files with PhotoViewer), but there is no single solution to restore previous functionnality. It is a case-by-case problem for each individual file extension. But at least workarounds ARE possible, so maybe I won't have to skip this build after all.
I also tried something else and it worked as well: For testing, I changed a .txt file's extension to .ABC, for example. .ABC is not associated with something, you know. I opened the .ABC file and associated it to Notepad and checked "Always use this app to open .abc files" check box. It failed the first time, but Windows remembered it the second time I've tried. So it seams we have to do this 2 times actually. I have to try other extensions/apps, but seams it works after all.
Not officially, but there is nothing stopping you from decrypting an downloaded ESD file to fully working ISO at the moment.
i'm using the "media creation tool rs5 batch file" took here... and the ISO is downloading... am I getting the 1809 Final RTM ISO right?
Thanks, but is there any substantial difference in decrypting an ESD to ISO compared to this method? I mean it's still 17763.1 in the end right?
Of course it will be 17763.1, that's what we are after, aren't we? Manually downloading the desired ESD('s) and manually convert them to ISO (using ESD>ISOv39 by @abbodi1406), his script has more options but both will result in a 1809/17763.1 ISO.
Thanks, I created an Enterprise only ISO earlier which I thought was clever instead of having all editions that is included in Business. Enterprise is the only edition I care for anyway.
The more you know, thanks for sharing! No my name is strictly related to Metallica. (Sorry for the off-topic posts)