New
#170
I don't think Microsoft is that stupid, you might be able to activate one or two, but I'm sure the servers would see the same key pop up eventually and deactivate the surplus ones.
If you had one computer and it broke down and you built another that would be a different story as long a the other one became deactivated.
Again, this is just my opinion and I could be wrong.
And I'm not sure if it will work with 10240.
OK, this is how and what I tested now:
- Clean install Windows 10 Pro Build 10565 on a machine which had never before had any version of Windows. When setup asked for a product key, I gave a never before used Windows 8.1 Pro retail product key. Key was accepted and activation successful.
- As I had no more "virgin" hardware, I created a new Hyper-V virtual machine, clean installed Windows 10 Pro Build 10565, entered the same Windows 8.1 Pro retail product key as above in #1. Key was again accepted and activation successful.
- One more new vm, clean installed Windows 10 Pro Build 10565, entered a Windows 8.1 Pro retail product key which has been used multiple times, last time on this very PC I am using at the moment for a clean install which was then immediately upgraded to Windows 10 Pro. This key was now accepted on the new vm for a clean install of Windows 10 Pro and activation was successful.
- Third new vm, this time clean installing Windows 10 Pro RTM Build 10240, trying to use any Windows 7 or 8.1 retail keys I have, used or unused, the key was not accepted and Windows could not be activated.
Conclusion, only based on this very simple set of test installs:
- Build 10565 can be activated with a valid Windows 8.1 (and most probably 7 & 8) product key, also when clean installing on a new machine.
- The RTM build, and most probably all builds prior to build 10565 need to be activated with a valid Windows 10 key, product keys from qualifying old operating systems will not work.
Kari
Exactly as I suspected, it was clear to me but this has confirmed it. It will probably be implemented at next full build.
Very good report Kari! Now made me really wonder what MS is trying to do or test?
Geeks please remember, this was just one set of test installs by a single user during past few hours and should not be taken as conclusive facts.
Anyway, that's how it worked for me. Absolutely none whatsoever issues to perform a clean install of build 10565 on virgin hardware using a retail product key from a qualifying older Windows, be the key used or new.
Mike, if MS really decide to do this, I'll go and search low price retail 7, 8,8.1 pro keys! Retail 10 pro key are way too expensive now!
aye, remember - these are all insider builds..
the RTM will be a slightly different beast..
10565 is working very nicely for me so far. Much better than that 10547 chaos build that kept dieing all the time! Loving 10565 so far...