New
#1
Win10 motherboard change activation saga
I recently changed the motherboard and CPU in my primary system. It was running Win10 Pro X64, upgraded from Win8.1 . That was an upgrade from Win 8, which was an upgrade from Win7, which was... you get the idea. The ancestral OS was retail. The most recent license I had purchased was the Win8 upgrade, from January of 2013.
The old MB was an Intel X99 one. The new, AMD x470. After Win10 detected the change and installed some different drivers, it ran normally. It didn't activate online. However, when I changed the key to the Win8 upgrade one, it activated OK.
The motherboard turned out to be defective. The RAM slots A1 and A2 weren't working properly. So, I returned it, and replaced it with a different X470 MB.
That swap went fine also. However, nothing I could do would permit it to activate online.
I called MS activation support. After they led me through a number of steps (all of which I'd tried previously), I was referred to another level of support. I went through that a couple of times. The first time, the support person suggested that I re-install Windows 8 and upgrade that to 10. I managed to avoid screaming obscenities at the man, but it was a near thing. On the second try, I got a tech who asked to be allowed to remotely log into to the system. I agreed. He tried a number of things, none of which worked.
He finally took a screen capture of the invoice for the new MB, which I purchased online a few days ago. His boss permitted him the generate a new Win10 key for me. That worked. I don't know whether the key is equivalent to a full retail license, but I hadn't expect to be given any sort of new key.
The short version: if you swap motherboards, and have a Win10 installation with retail origins (not OEM), I expect that Microsoft will support re-activating Windows on the new hardware. If you have to deal with humans, you may encounter some who offer nonsense solutions. Persevere, and you may eventually find a support person who is both considerate and competent. (Thanks, Kamalesh.)