WindowsUpdateBox.exe is the installer, they can fix it if it's the issue they can also apply CU to the deployed OS before initiating installation
I hope they (MS) will not release new build. Again new build with new bugs and after esd file people will ask for ISO. And new thread here for this.
So if I clean install from the 1809 ISO I will be fine? No errors? Because I read somewhere that I shouldn't download 1809 manually and install. Thank you.
LOL, yes obviously, but I was just wondering if it deletes files after the install, like does it have a bug where it deletes files after awhile.
Afaik not. Still i must admit; all those who store personal files on their Windows partition or allow the OS to manage them are doomed anyway.
Well, a new build number won't restore them too, so I don't understand that point. Yes, I'm serious. If a new build still on 17763.xx comes out with it's own media to replace mct ones (MSDN, etc) and corrects that particular problem, new upgrades from previous 1803 won't suffer from the current user files deletion. In the same time, PCs already running with 17763.1 would only receive a CU that aligns it with that upgraded media instead of having to perform another full upgrade. But unfortunately, even if the new media is still a 17763.xx, I doubt MS will release a CU for .1. IIRC, that dead end scenario already happened with RS3.
With RS3 there was a different reason — the 16300+ range of builds had been already reserved for RS4, so they had to bump up the delta. The re-release of RS4 was IIRC because 17133 had broken .NET framework — these bugs cannot be fixed by a CU, as they impede servicing. This is a bug in the user profile service, which is not used when offline servicing, so it can be fixed in an update.
Remember April ? 17133.1 was released as RTM, then got CU before it got pulled and we got 17134.1 as RTM