With manual install you mean clean install from boot? If yes: The rollback is probably because of a driver issue, as posted on the blog, when clean installing there is no driver present, when upgrading the driver is present, maybe that's the cause.
No I updated mount the image and upgrade from inside the OS I tell strange bug hopefully will be fixed soon.
My WU update went smooth up to the restart after install then I got the attached error. After pressing the button waiting & pressing it again I went to the Start menu/"Update & restart" choice, that worked & the update completed in 10 minutes. My update install was on a (x2) partitioned Samsung 850 SSD EVO drive.
It should successfully clean install, as I have been having issues with the last few builds not upgrading successfully and rolling back to the previous build. It's either the same bug with the storage driver issue in this build or similar bug relating to storage drivers or whatever, I am too using an Samsung 970 NVMe SSD too. However, I only started having the storage driver type of bugs with the last few builds as I upgraded my PC to an ASUS Maximus XI Extreme Motherboard and an Intel i9 9900K, as well as 64GB of RAM etc. So I thought that the issues with builds not upgrading and rolling back to the previous builds was due to possible defective components or whatever, as I had no issues with my previous PC builds. Luckily Amazon replaced all of the components for me, and the builds would upgrade successfully without rolling back every time, but it could have been due to a clean install of the latest build available via UPPDL) with the new components etc. and I've not had any problems with the last couple of builds until now of course So long story short, I am confidant that a clean install of build 18936 would install successfully, but I'm not 100% confidant, but I can attempt it tomorrow when I get another Samsung 970 Pro NVMe SSD.
No, this bug is different the previous issues with upgrading. I also had issues upgrading via windows update for last few builds but manually updating using an ISO always worked. I also have an asus rog mb , there are few things that I tried , like disabling secure boot, disabling rapid storage, changing pcie to sata . I think I will also try clean install
It does clean install very well. I also have the Samsung 970 Pro NVMe SSD. One thing I do do is integrate all my drivers to the install.wim before installation.
I did the same as you, however using an ISO didn't work for me either. I also have the ROG RYUJIN 360 AIO Cooler so just now thinking about it, maybe the storage drive on it for the LiveDash OLED Display could be causing some issues on top of the other issue(s) that seems to be effecting NVMe SSDs? I've not actually tried it on a standard SSD actually either to see if I had the same results. All I tried was all four NVMe slots, as well as my ASUS Hyper M.2 X16 Card but had the same issue each time, haha. It is quite annoying though when a build fails to upgrade and rolls back, as sometimes it just hangs after the boot screen when I'm usually not near the PC and then I get family members moaning at me because my Plex Media Server is down, haha.
I am doing a clean install (full format and install). It booted and working fine, installed samsung nvme driver and it works great so far. Update: Once I tried to install intel rapid storage I got GSOD . So I guess Intel Rapid Storage is the problem, maybe removing it and trying upgrade will work
I will give that a try. I just also remembered that I'm not using AHCI either for the storage controller for standard SSDs so that I don't lose any of the 6 sata ports as have four NVMe SSDs as well lol. jnlpl[=n 5
Tried it, but computer said no! Will just have to wait for Microsoft to get a fix sorted for the compatibility bug for the storage driver that is effecting the upgrading to this build, or wait for the next build. Whichever is soonest, but to be honest, those who cannot upgrade to this build aren't missing much!!
Hi there, Wow, I've been hit by this bug and its a real killer... and in my case, I cant even rollback / install previous 18932 without loosing all my apps & settings...
I have had to do a clean install a few hours ago as Windows Update installed the 18936 build even though I had updates paused. When I restarted my PC I accidentally pressed update and restart instead of restart so it began to update from 18932 to 18936 and I knew it would fail so just had to wait for it to rollback but then I got a GSOD, so I restarted then got a BSOD, then I wasn't able to boot, just kept getting the damn GSOD, so had no choice but to clean install.