If the ISO is official then the install.XXX file is official no matter how it is packaged as long as it is not modified. If you have an official MS issues ISO with an install.ESD file you can convert it into a install.WIM file (several different ways) and have exactly what you are asking for.
Yeah, but if you install this build now and you're not in the Insider rings, will you get the CU that was released normally? Or you would have to use powershell? When I installed 17133.73 through powershell for example, i didn't get an entry for it in Apps&Features or even Update History. That's annoying. But hey. All of this is pretty irrelevant now, cause I very soon the ISOs will be publicly available.
guys, you are missing the point here. i love this forum and the efforts by some users on the tools, etc. the thing is, like i said, "I" just want the official iso with the install.win. just that. tomorrow ill grab the iso and start installing it everywhere (my clients, etc). simple, right? why all the fuss about it?
So far GA didn't happen hence the CU is insider only. Will change after GA as with every RTM before. Updates that are manually installed only show up under the 'Uninstall Updates' option in WU Settings. What's annoying here ?
What's annoying is behavior that is different than the "normal" Windows, for a build that was advertised by every tech site as RTM. How can this be so hard to understand? People that install an RTM don't want to install updates through powershell nor do they want them in the old Windows 7 menu only, they want standard behavior that one expects from Windows 10 retail. Yet again, there are DIFFERENT people with different motivations. One might get a kick from having the latest Windows in VMs testing the new features. Another wants the RTM when it comes out and expects normal Windows behavior, not "managed by Insider program". It's obvious you feel one type as inferior or not belonging here. It's some sort of pointless elitism over a stupid piece of software. Really puzzling that it's so hard to accept and move on that other people would use Windows differently.
Yes, installing this build you will still get WU as normal, you HAVE to, because it's identical to the one being made available on Monday. If they changed the build in ANY way, they would be releasing an untested build on Monday. The only reason you don't see updates yet is because the updates aren't public yet.
What's so difficult to understand here? Updates won't be installed using Powershell once MS actually release them publically. Users on here just happen to know how to get hold of the updates and install them manually. You don't HAVE to do that - you can just install the build, and wait till MS make updates available, just like normal Monthly updates. The 'non-standard' behaviour your refer to only happens when someone installs an update manually. Believe me, the RTM build will behave in a perfecty normal way for everyone who simply installs it and lets MS take care of the rest.
Sorry if this has been posted before, Microsoft creation tool, Windows 10 April 2018 Update will be available on Monday at 10AM Pacific Time. 30 April 2018.
Ha its probably going to be released on Microsoft/Seattle time. Also, when performing an in place upgrade and retaining apps, settings & personal files, windows creates another recovery partition about 850mb in size while leaving the original 500mb recovery partition. I've explored the original 500mb partition with partition wizard only to find log files. The WinRE image is now located in the new 850mb recovery partition which appears after the current active C:\windows partition. My question is, if I were to then perform another in place upgrade would it create yet another recovery partition? Rather annoying since the initial 500mb cannot be moved and reacquired in the main C:\windows partition as there is the System/EFI partition immediately after the original 500mb partition. E.g. Recovery (500mb) -- System/EFI (100mb) -- C:\Windows (158.9gb) -- Partition 5 (New Recovery 850mb).
No need to get too serious . 16299.15 also had a similiar (but no so visible) bug with exactly that setting where it was always reverted to the default. That also was patched with a later CU. Only difference in not being that visible. People normally install it when it's publicily released via the usual channels. In that case it will all work perfectly with the same files like now. Early adopters never have an easy life .
You can add command line parameter /ResizeRecoveryPartition Disable to either MediaCreationTool.exe or Setup.exe and you won't get that bug, if there's no space Windows will place winre.wim in C:\Recovery
i got the 17134.1 from the media creation tool yesterday??? and everything is working perfectly as normal including updates. created both x64 and x86 iso. i was actually surprised when i went to use the usb stick i made that it was in fact 17134.1 i would have thought it downloaded the older version. edit: one issue i forgot about is my actual screen brightness no longer works. it shows its going up and down on the slider but nothing actually happens. been trying to figure it out. even did a clean windows install didnt work. reverting back to fall creator fixes it. otherwise perfect.