Well after the failure of 16215 and 16226 to upgrade, if the next one fails I'm gonna lose interest in being an insider. I don't like the idea of clean install (h'mm could even be for every new build ) and anyway why should I have to, as surely MS has enough experience to know all about upgrades over the years.
A beta tester who can't deal with bugs.... If you choose to use it as your main OS, that's your own choice, MS advise against it, there are going to be bugs, including the installation
Part of testing is being prepared to clean install too But yes, the official method is upgrade I agree, they should at least have that working
This happened to me using WU from 16215 > 16226 w/ the 'S' sku, every time (4x) I tried it went thru the whole update process but ended w/ 16215 again. I finally was successful by just downloading the .iso, burning it to a DVD & installing that way. You might try another installation too.
Upgrade from 16215 to 16226 x64 on Vmware Workstation 12.5.7 was successful, but only after uninstalling 12.5.6/12.5.7 and installing 12.5.7. Note: Previously attempts to upgrade from 12215 to 16226 failed on 12.5.6. Last night I performed an upgrade to 12.5.7 and tried the Windows upgrade again, but I had a couple of freezing events (freezing is reported by others on forums with no solution suggested). So I uninstalled 12.5.7 and performed a fresh 12.5.7 installation. I also had a slow (lagging) mouse/touch-pad responses on 12.5.5, 12.5.6 and 12.5.7, so I uninstalled the VMware Tools and reinstalled it again, this was done before the successful upgrade. My touch-pad is now responsive and I have not met any freezing event; so far!!.
That is the most unwelcoming thing about this Build. Microsoft should have sorted out the upgrade process before even releasing it. It's a disaster - regarding the number of people who couldn't upgrade till now due to this single error.
Microsoft's attitude is this: if we give you updates that are no longer compatible, then get a new pc
I don't think this is a compatibility issue. This is an issue with the update failing along the line of downloading the necessary files needed for upgrade. It is more or less a server - Update Delivery Optimization problem, I guess.
Easier method is hold down "Shift" key then click on "Restart" from start menu. Then Windows comes up with different start options including safe mode