Microsoft fixed the VMware booting issue in this and the previous build. So,18362.1/30 x64 installs fine on VMware.
Hello There is an ISO (or ESD) of the 1903 expected this week (still Insider I believe) ? I had downloaded an ESD from the 18362.1 available on the 1st post, I believe but I can not find anymore Thanks
At this moment there are not yet ESD files available for 18362.1. UUP only, and no-one knows when the ISO's will be available, given the fact 18362 will still be tested in RP ring first.
Clean Installed 18362.1 on my Surface Laptop using an ISO generated from UUP (through adguard's UUP website), and everything went perfectly without issues. sfc /scannnow also shows no errors. All works perfectly, except a little bug I had installing a secondary Language Pack (with its extra text and voice packs giving errors during install, after download). The only way to workaround this periodic error/notification was to remove the secondary Language Pack altogether and deleting all folders in Software Distribution folder. Maybe not all LPs are ready to install via WU? Other than this, this build seems rock solid already.
Ah yes, its was UUP But I can not find the UUP download, a batch that downloaded and converted to ISO alone (with all the files, aria2, etc ... to do it) EDIT: it's good, I re found it
Clean-installed 18362.30 on two machines now and no issues so far. Even the developer mode package installed fine (I didn't get any error when I enabled developer mode in Settings, so I assume it's there). It's only weird that the 7 GB of reserved storage are active, despite the registry key in question was set in the offline image before deployment.
It is stupid, what they are basically saying is, with the new version of Windows, if your AMD / ATI / nVidia GPU plays up, its not Microsofts fault, the GPU companies have to adapt their drivers to work on the new version of Windows, hence wait for a new driver. same for Sound cards, etc etc.
That was the same when upgrading from xp to vista, etcetc... The info clearly shows that as soon as the driver/service update is available, the upgrade can continue. Considering 18362 aka 1903 still is in the insider preview rings, atm in slow and fast, it can take some time for both, msft and the manufacturer, to get it all straightened out.