Page 2 of 2
Posted: Sun Jan 11, 2026 11:06 pm
by 0jY3807U
Yeah, You could also try running the activation troubleshooter again, but select "I changed hardware on this device recently" when it prompts you. Let me know if that works.
Posted: Mon Jan 12, 2026 12:48 am
by vsax58232
Same here. Also, double-check that you're signed into the Microsoft account that was linked to your Windows 10 license.
Posted: Mon Jan 12, 2026 1:31 pm
by 5554romh
This happened to me. I had to use the activation troubleshooter and select the "I changed hardware on this device recently" option, even though I hadn't.
Posted: Mon Jan 12, 2026 9:11 pm
by 171r3zujs
Yeah, that trick worked for me too—did you already try running the command "slmgr /rearm" in an admin command prompt?
Posted: Mon Jan 12, 2026 11:01 pm
by fw8523
Yeah, Agreed, that command can help reset things. Also, double-check that you're signed into the Microsoft account linked to your old Windows 10 license.
Posted: Thu Jan 22, 2026 1:53 pm
by xS6ab2
This. You could also try using the Activation Troubleshooter again, but this time choose the "I changed hardware on this device recently" option.
Posted: Wed Jan 28, 2026 4:17 am
by OFhMD7R6LfD
Another option is to run the Windows Activation troubleshooter from the Settings app, which can sometimes automatically fix these upgrade-related glitches.