- Joined
- Dec 27, 2008
[Solved] Windows 10 wouldn't reactivate on the same hardware.
First time I have run into this. Not sure what is responsible but the thought crossed my mind that sense Windows 7 support is now officially a legacy product $MS may have tightened the reigns on Windows 10 activation.
The story line is I built a new box for a customer using the Macrium reflect image from the old hardware so as not to forfeit all her apps. It was a hardware upgrade from an old core 2 duo machine to a Skylake Pentium G. I didn't think it would work but thought it worth trying as opposed to a clean install from scratch. Well the new machine booted fine into Windows 10 and the OS found all the appropriate drivers for the new hardware, or so it seemed initially. I purchased a new Windows 10 activation key from URCDKey and activated the new build with the "change the product key" feature found in the activation wizard.
A few days later the customer's wifi connection started dropping out repeatedly and to make a long story short it wasn't the USB wifi adapter that was the problem or the router but a more general USB issue. External hard drives were not being recognized at all but flash drives were so I backed up her data onto a flash drive. I just figured there was some driver issue that had developed over the few days since the build, given the patch over way I installed the new system.
So last night I did a clean install of Windows (same version) on the same hardware but to my surprise it wasn't activated when I checked. Historically, you can reinstall Windows 10 on the same hardware and it would automatically activate. To cut the story short again (after trying various things) I had to purchase another product key off ebay, I did a new clean install adding in the key at the front end of the install and it activated fine.
The only change I made in the first attempt at a clean build was changing the partition scheme from MBR to GPT. Do you think that could have fouled up the activation?
Anyway, I'm sharing this to see if anyone else is running into Windows 10 activation issues recently that were not happening historically.
First time I have run into this. Not sure what is responsible but the thought crossed my mind that sense Windows 7 support is now officially a legacy product $MS may have tightened the reigns on Windows 10 activation.
The story line is I built a new box for a customer using the Macrium reflect image from the old hardware so as not to forfeit all her apps. It was a hardware upgrade from an old core 2 duo machine to a Skylake Pentium G. I didn't think it would work but thought it worth trying as opposed to a clean install from scratch. Well the new machine booted fine into Windows 10 and the OS found all the appropriate drivers for the new hardware, or so it seemed initially. I purchased a new Windows 10 activation key from URCDKey and activated the new build with the "change the product key" feature found in the activation wizard.
A few days later the customer's wifi connection started dropping out repeatedly and to make a long story short it wasn't the USB wifi adapter that was the problem or the router but a more general USB issue. External hard drives were not being recognized at all but flash drives were so I backed up her data onto a flash drive. I just figured there was some driver issue that had developed over the few days since the build, given the patch over way I installed the new system.
So last night I did a clean install of Windows (same version) on the same hardware but to my surprise it wasn't activated when I checked. Historically, you can reinstall Windows 10 on the same hardware and it would automatically activate. To cut the story short again (after trying various things) I had to purchase another product key off ebay, I did a new clean install adding in the key at the front end of the install and it activated fine.
The only change I made in the first attempt at a clean build was changing the partition scheme from MBR to GPT. Do you think that could have fouled up the activation?
Anyway, I'm sharing this to see if anyone else is running into Windows 10 activation issues recently that were not happening historically.
Last edited: