quick windows 10 cloning question

emosun · May 11, 2022

Is windows 10 smart enough to know it's been cloned in terms of hardware detection?

Like if I clone a windows 10 drive then move it to an identical machine with the same hardware , would the os know that it's been cloned and as a result have some sort of functionality broken/disabled?

Reason I'm asking is I've had this rational of cloning my OS drive where in the event something happens to the original machine (stolen/broken beyond repair) I theoretically could just use the backup drive and repurchase all the same parts and just remake the same machine again. This would be on Windows AME

wseaton · May 11, 2022

Yes.

Hard drives / SSDs, motherboards and CPUs all have unique device ID's that even when changed with identical parts Operating Systems are well aware they have been changed. The only real way to spoof this is if the OS is running in a virtual machine, and you export the virtual machine and import in a specific way that the 'virtual' devices assigned to the guest OS don't change these signatures. So, the OS has no idea it's been moved to a new box. Many a VMware novice has been caught blind sided by this. Every blank VM you create has unique device ID's by default.

However, changing a hard drive typically doesn't cause issues. Note the zillions of people who clone to SSD from HD with no issues. Windows is aware the drive has been changed but does it's best to work with the migration, enable trim automatically, etc. Many people assume Windows doesn't know the drive has been changed. Yes, it does.

.A CPU change to an identical one isn't going to cause an issue, although that's pretty rare. Upgrading a CPU presents more issues for the BIOS, etc. A motherboard change however will almost certainly trip Windows activation. If it's the same motherboard you won't have an issue with drivers, but you might have to reactivate given Windows will detect this as a new computer, and if you're running an OEM this is kind of a no-no....kind of. I dealt with this a few days ago with a 7 year old Dell Optiplex running Windows 10 and some accounting software that could not be reinstalled. I cloned it to a brand new Dell XPS, and after downloading all the new drivers from Dells site everything ran perfectly. Windows required a reactivation because it was an OEM and obviously a new motherboard, but this is where it gets fuzzy. If you're running Windows 10 pro, and assign the activation to your Microsoft account then Windows kind of looks the other way and reactivates automatically. If you're running Win10 home I've noticed this process is not always guaranteed. So, Microsoft is not exactly following their own EULA in regards to OEMs in an attempt to get people to buy Pro version of Windows and sign up for Microsoft accounts. That's my take

Oddly Windows 95/98 would take extreme hardware changes and not blink an eyelash. NT was extremely fussy. XP wasn't as tolerant as Win95/98 but workable with a sysprep , Win7 was better yet, and Windows 10 very tolerant, especially if you flip it in safe mode. Me thinks Microsoft's EULA dept and lawyers aren't on the same floor as their activation team.