Windows 10: Activation Error after HW change - Unable to activate windows

Hi,

3 days ago I update my HW (MB, CPU, RAM & SSD), so after reinstalling all drivers and after couples of reboots I was awaited by this message on desktop "Activate Windows, go to setting and activate windows." so I do that I go to "Settings/Update & Security/Activation" there I select "troubleshoot" and than select "I change hardware on this device recently" and after that I get message "Unable to Activate Windows / We can't reactivate Windows as our servers aren't available right now. Wait for a few minutes or try adding your Microsoft account again."

What can I do next, has anyone have any solution?

:)

 

activation after change hw.

A motherboard change alone is usually enough.

 

activation after change hw.

Hi, I had a Windows 7 1-2 years ago. I updated to Windows 10 and the activation was OK. Now, I had to change my mainboard. Because of new type, I had to change CPU and RAM also.

I started my windows 10, and activation is out. I tried to use generated key, but nothing. I tried to TROUBLESHOTTING and pressed "change hardware" But still nothing.

I still have error 0x803f7001.

 

as you switched your mobo, which actually is the "key" for activating the windows 10 (or 8/8.1 in that matter), you have a problem at hand.
if i were you, id make a LONG phonecall to a MS and mourn/whine/pray quite a bit for letting them to reactivate your system *Smile

the 2nd, least favorite option is to buy retail win10 and get the system activated via that.

sure, there might be 3rd option (to install your old motherboard back) or 4th (that im not aware of?) option too, but dunno if theyre viable ones + id be interested to hear what those cases would prolly be

edit - btw, if you recently switched the motherboard, wait 4-5 days until you make a call, it might be just waiting for the reactivating too so cant say for sure for the first 72-120hours

 

If the previous PC was registered with the activation migration tool, digital licence will be transferred with MSA logon, not sure in the case that it was an OEM, however.