On one of My PCs the only way to get it to see the upgrade was to sign out of the MS account and into a local account, then re-sign in with the MSA and it found the upgrade after I hit refresh
Starting on July 29, we will start rolling out Windows 10 to our Windows Insiders. From there, we will start notifying reserved systems in waves, slowly scaling up after July 29th. Each day of the roll-out, we will listen, learn and update the experience for all Windows 10 users.
I thought I'd "do the right thing" and did a fresh install of 10130, logged in with my MSA, hit WU and nothing more than the drivers and Defender update came in over a 2 hour period and I was trying ALL the suggested "fixes". I finally upgraded 10130 to 10159 vis the esd ISO I had downloaded. This forum is filled with many issues getting the upgrade to be "seen" by a PC and no single method seems to work consistenetly. I hope this gets addressed by Gabe/MS ahead of the availability of RTM.
The issue is because of the improper installation of kb3070677 that update allows you to see newer builds. But for many people including me it never installed correctly no matter what I tried so I did what you did was upgrade from esd.
You know what people ? I find windows 7/ 8 / very stable and also very fast with my laptop as i find with 10 it will only get better with hardware brands sorting out there drivers .. Don''t understand the need for 8.1 because it seems slow as a OS .. it is just like now installing Adobe CS6 Master Collection normal time 30 mins on windows 7 / 8 but when i use 8.1 takes around a hour for some strange reason ..
So now the question is whether this manner of upgrade will be considered valid by MS. Since it wasn't technically upgraded via the esd/WU process but via an ISO created from the esd??