I guess im one of the lucky one's , I updated windows 10 pro 64 bit and everything works no loss of data YA ME about time , usually I get bit in the butt with all kinds of problems so far all is well ! maybe its because it a 6 year old AMD computer .
Incorrect info or not, I'm tired of this bulls*** They got to stop releasing all these half-a**** releases to the public, it's been said many times but two major releases per year isn't good in the long run for any one. First you have to make sure that all your software and hardware is compatible with the new release, then you have to beta test the release pro bono. Why not take the time and work on the OS for a longer period of time, make sure it's somewhat stable at release. One major release every 2 years is enough, just like LTSB/LTSC.
Not from MS POV . LTSB 2016 was irregular to adress issues in the 2015 version, so counting from 2015 gives 3 years. As @abbodi1406 already pointed out they use 2019 to match the overall naming.
Maybe for you, but many would feel very different about it! 2 years with no upgrade? I want my money back...
I think @abbodi1406 said early on this thread that the released version 10.0.17763.1 was about 90% ready, but none of us listened to that, me included. At least I can't identify any lost files during the upgrade.
I upgraded in place using the early ESD converted to ISO and did not experience any issue. I used some switches while installing, switches which I normally use primarily to avoid creating the recovery partition during the install. You might be right to guess that the issue only affect those updating from Windows Update using WindowsUpdateBox.exe. In the mean time, the upgrade/update files were expired from WSUS in addition to the other already mentioned update channels.
I used the UUP files (only 2GB) to build an ISO, and so far I've experienced zero problems. My in-place upgrade went smoothly and things are definitely more zippy
It has nothing to do with the used files, all are the same, UUP, ESD and ISO, it's the scenario on which people upgraded and i not once seen it published.
You missed the point: I'm agreeing with those who say it appears to be linked to upgrades done via WU - and not local media
As this went to GA many people will be running it fine already, thats a much bigger reason than with 1803 for MS to fix this some other way, otherwise they all get another full upgrade in the space of weeks which isnt much fun for business users especially those sporting celeron W7 era machines.