New
#51
This is the way to do it.
When I did early Insiders on a laptop, many times (but not every time) a new build came out, my system was listed again in my account so it looked like I had 5 Insider systems, but they were given different names. I deleted them all except the current install (and switched out of Insider), so I only have one now listed in my devices.
I wonder, since you have on record with MS that your system is listed twice in your account with the same name, if you deleted both of them, if that would make any difference. Because, like I said, mine were given different names, based on the build that was installed. Just a thought.
UPDATE: (As suggested earlier by NavyLCDR in post 46) I put an old (activated) image of 7 on a spare SSD and verified that it stayed activated through several reboots, and then did the 10 upgrade. BINGO! We are activated! And after a quick login to my MS account, I am again activated with a digital license linked to my MS account. Now the fun of reinstalling all my junk! Fortunately so much stuff is cloud-based, so profiles, preferences, etc. transfer much easier than in the past.
Ironically, MS called to follow up on my case, which I informed the tech that I got it going again, and "Oh by the way can you reactivate my Office 2013?", which he did. So slowly I am getting back in the saddle.
Still no idea as to what got messed up. And a huge THANKS to all who offered their wisdom and assistance!!!
So now I see this in my MS account, and the other entries have disappeared:
CHD-RVE-PC
All Series
Last time your device status changed: 05/12/2017 09:10:47 +00:00
Your device is up to date
Last check for updates: 05/12/2017 05:00:37
OS Version: 1703
Moral to the story - for me, I will stay away from the Insider Builds, it was fun - but not worth the headaches.
Last edited by red454; 12 May 2017 at 07:35.
When I dual boot, I prefer to use a virtual hard drive rather than creating a separate partition.
Unfortunately, this is not suitable for Insider versions as you cannot do a build upgrade on a vhd but you can do a build upgrade when vhd is in a virtual machine. You can faff around loading vhd in a vm and upgrading that way but more effort than it is worth.