Swapping motherboards without paying for another Key ?

DayRider

Reputable
Mar 3, 2014
216
0
4,680
So i contacted Microsoft techincal support live chat. They said to me since i have the OEM Key and CD that when i change motherboards and CPU to a intel from FX 6300 i WILL NOT have to buy another key and that i can just reinstall using that key . Is this True?


Thanks!
 
Solution


1. Never call before and ask.
2. The only entity in control is the activation server farm. It may or may not choke.
3. If it DOES choke and not activate, that is when you call and say 'Pretty please'
4. They may or may not. They are under no obligation to allow it.
The OEM key should only ever reactivate on the motherboard it was first activated on. HOWEVER, Microsoft sometimes allows you to call in and do a manual activation over the phone. I have never tried this with Windows 10, but assume it still works.
 


1. Never call before and ask.
2. The only entity in control is the activation server farm. It may or may not choke.
3. If it DOES choke and not activate, that is when you call and say 'Pretty please'
4. They may or may not. They are under no obligation to allow it.
 
Solution
I've had success getting troublesome OEM keys to activate with the phone activation option, but I was using the keys on same system just with a clean windows install. My guess is that it will work, but the only way to know is to try. I agree with USAFRet that tech support is only useful if you try and it doesn't work.
 


Are you sure because I gave the tech support guy my key and he said I can use it again to reinstall windows with new mobo

 


The license agreement for OEM is 'that original motherboard'.

That Tech Support guy saying that is not the activation server that actually authorizes it.
Try it. See what happens.

If it activates, great.
If it doesn't, call the phone robot and try.
If that fails, then you talk to a human.
 


Ok , I'm getting a i5 6500 in a few weeks m currently I have a fx 6300 and gtx 970 so yeah . I get a small bottleneck so I'm getting Intel to fix that .