Maybe this is why his VM activated? http://answers.microsoft.com/en-us/w...0ffe9dd?auth=1
EDIT: Reports are, that agent got it wrong, it has not been extended. I can't post a link to my source, its a private site.
Last edited by alphanumeric; 01 Aug 2016 at 05:07.
That timing seemed odd to me. From what I've seen reported on the Yammer network, those that do the free upgrade now, have to then wait another 30 days to do the Anniversary upgrade. Because of the 30 day roolback feature. The Anniversary update will wipe out (replace) the Windows .old folder. No going back to your original OS you upgraded from. The current (free upgrade ) build will not auto update to the Anniversary update until at least 30 days have passed from the date you upgraded on. That's the theory anyway. Unconfirmed at this point, as far as I'm concerned.
Reports are, that agent got it wrong, it has not been extended. I can't post a link to my source, its a private site. I added an EDIT to my original post.
Plenty of reports on other forums if you upgrade using MCT, and use an old 7/8 key to activate it, it still works. Have not tested it myself. Run out of keys/pcs to upgrade - LOL
I'm almost in the same position. I'm not out of keys but all my PC's already have digital entitlements, and some have Home and Pro entitlements. I'm also running Enterprise and Education. For now, I'm just going to wait it out and let those installs that are eligible, update via Windows update. Then do some of my own testing with clean installs. I expect my Enterprise install will not update. I want to see if first hand though so I can stop saying "I think" and "as far as I know" etc.
You can (of course) have a home and pro digital licence (new name) on same pc, but interestingly you only see latest install as a device on MS Account. It is not yet clear if RS1 allows linking of both digital licences to your MS account if you can only see one device i.e does it only detect the latest one?
My pc is dual boot home and pro with both having digital licences. To ensure I can see both "devices", I have linked one via one MS account, and the second via another just to be on safe side.
That will not help. You would need new hardware or a new VM to be sure.
If you have a digital entitlement you are stuck with it (I think - at least I seem to be). I've tried removing a VM from my MS account and it still activates if I clean install without entering the key.
I don't have any more keys to try on a new VM but it certainly worked a couple of weeks ago.
I'm not dual booting so that device is only listed once anyway. It's not running the Insider preview either so I haven't officially linked it at all. It currently running Enterprise and activated with a MSDN MAK key (no digital entitlement). It was originally upgraded from 8.1 Pro to 10 Pro. It has a Windows 8.0 Core OEM key in the BIOS. On a clean install that key was read and 10 Home installed and auto activated with a Digital Entitlement. The double entitlement wasn't planned, it just happened as a result of the Windows 10 install media reading my OEM key. I don't ever run Home on it except by accident. And not for very long. I did a quick change key and upgrade to Pro the first time it happened. Now I just use a PID.txt file to install Pro and override the auto detection of the OEM key.
Quote