It doesn't matter if MS releases a dozen of CU before/after the Windows 10 v1903 GA, 18362.1 is the RTM image as long as the Language Pack version stands at 18362.1
Then 17133.1 still was the rtm but msft pulled it totally, that can happen with every new build and that new build will have to go thru all the hoops, didn't happen with 1903. The MVS iso's are distributed to devs (mostly devs from the OEM's), previously just called RTM. History, known to me: 10586 first got pulled and re-released, even the ESD's were already online. 17133.1 got pulled and fully replaced by a newly compiled build, 17134.1 17763.1 had a show stopper bug for some users, they re-released a refresh iso instead, calling it the re-release of 1809. 18362.1 is out on the retail release ring, mvs iso's are out and updates are being created/released for it. And for the xxxx time, 18362.1 is original first release, the .xxx is by CU, just like with a refresh iso. This time they will pre-integrate it, instead of releasing the CU separately so it seems. And because 2019 is a messy year for msft (iirc because of the move to the azure team/department). They forgot to stop the release of the MCT (still not working but was available), the xDK KITS (now blocked) and the EVAL iso's (now blocked).
I tried everything - it does not help. I made an OS image of 18362.86 and install Windows with data saves.
Possibly the new block they introduced if USB drives are plugged in. I assume this would also apply if your install media was on a flash drive, which sounds a little daft.
ReservedStorage I installed clean with build1903 iso from MSDN. no modefied ISO. ShippedWithReserves was, of course,1. Set this back to 0 by Regedit I did Windows-Update soon. In the midst of several updates, this registry is reflected, The Reserve area has been deleted. But There is no change unless you use WindowsUpdate.
Kudos to bonesz. After removing the SD card and copying setup files from USB drive to the “C” drive and then removing USB drive I was able to upgrade the laptop to version 18362.86 with no warning messages and no negative consequences. Gee, I just love the smell of a fresh OS upgrade in the morning. Smells like... Victory!
Does anyone know more details of the battleye anti cheat not working with the build,is it the fault of windows or battleyes or graphics drivers?Any fix for it?
This has been covered over and over again, by MS and on this forum. It's Battleye that needs to be updated, some games have done it (Fortnite) and some seem to be lagging behind (Pubg? unless the complaining players aren't getting updates properly perhaps/)