New
#11
The thing with OEM product keys and licenses - you can always try the product key to activate Windows. Sometimes it will just work over the internet. Sometimes it will work only via phone activation. Sometimes the product key won't work at all and, now with Windows 10 you have the activation troubleshooter to fall back on. It seems like there are no absolute hard and fast rules regarding what will actually happen when a certain product key/license is tried, regardless of whether or not that particular use of the product key and activation violates the EULA.
Clear as mud, I gave up trying rationalize it all out when my Enterprise installs all got DL's.
In this instance, we need to know how the original hardware was activated in the first place. And if it was in fact an OEM system builders key, and not a Retail key. Then how the hardware was swapped. All at once, or one piece at a time. Was windows reinstalled on the new hardware or was the original install used. Plus was the replacement motherboard the same make model etc. It all factors into whether activation fails or not. If Windows was reinstalled, what key, if any was entered?
A response to post #15.
The new motherboard is not of the same make/model as the old one.
With reference to other questions, I have asked them in this post.
I'm not making any accusations, apologies if that's how I sounded. But with no proof, I highly doubt it activated all on its own after swapping the motherboard. Like I said, if you believe it fine, I don't. Not with out more info.
A motherboard swap, as far as activation goes makes that PC a new PC. The hardware ID will change and won't match what is stored on the activation server for that product code. If no match is found no activation.
No apologies are needed.
I think it doesn't matter whether Activation Troubleshooter was actually used in this case; it does matter whether it actually works when it is needed in similar cases, as my PC was upgraded to Windows 10 from an OEM version of Windows 7.