I've swapped hard drives, video cards, etc in the past and had no issues. I've even swapped similar, but not identical motherboards, ASUS M2N64 for a M4N64 and activation was OK. As always though YMMV. IMHO, a hard drive swap is no big deal. It's one of the most common hardware swaps done. They wear out faster than most other component's.
Interesting quote from Microsoft License Terms that came with W10 upgrade.
It seems if you upgraded a Retail (Stand-alone) version then you can transfer it to new hardware. It may take a call to MS but don't know.4. Transfer. The provisions of this section do not apply if you acquired the software as a consumer in Germany or in any of the countries listed on this site (aka.ms/transfer), in which case any transfer of the software to a third party, and the right to use it, must comply with applicable law.
a. Software preinstalled on device. If you acquired the software preinstalled on a device (and also if you upgraded from software preinstalled on a device), you may transfer the license to use the software directly to another user, only with the licensed device. The transfer must include the software and, if provided with the device, an authentic Windows label including the product key. Before any permitted transfer, the other party must agree that this agreement applies to the transfer and use of the software.
b. Stand-alone software. If you acquired the software as stand-alone software (and also if you upgraded from software you acquired as stand-alone software), you may transfer the software to another device that belongs to you. You may also transfer the software to a device owned by someone else if (i) you are the first licensed user of the software and (ii) the new user agrees to the terms of this agreement. You may use the backup copy we allow you to make or the media that the software came on to transfer the software. Every time you transfer the software to a new device, you must remove the software from the prior device. You may not transfer the software to share licenses between devices.
Jim
I'm not a lawyer so some of that is over my head. I'm not saying your wrong, just that I don't fully understand what is said in what you posted.
After I had finished the transfer, I signed in to new hardware (the transferred 10) using an MS / Insider account and used the Media Creation Tool to create a USB install media for clean install. Clean installed Windows 10 using this install media on original hardware with the generic key, first wiping the hard disks.
Am using that Windows 10 now, clean installed and activated on the original hardware.
Two more tests I made:
- Using the ISO created with Media Creation tool from Microsoft, clean installed Windows 10 Pro to a Hyper-V virtual machine. Windows was automatically activated
- Generalized that Hyper-VM Windows setup
- Captured the image
- Restored this image on an old HP laptop
- Booted the HP laptop, gave the generic key in OOBE
- Windows was setup correctly and automatically activated
-- AND --
- Using Disk2VHD, created a VHD of this HP laptop's activated Windows setup
- Created a new Hyper-V virtual machine using the existing VHD option
- Used the VHD I had made with Disk2VHD
- Windows was activated
Conclusion: Three working and activated Windows 10 Pro machines using the same installation and generic key:
- I created a virtual machine clean installing Windows 10 and activated it
- Using the system image of that vm I transferred it to a laptop, it was activated
- Using Disk2VHD on the laptop I created a new VHD of the same Windows 10 setup
- Created a new vm using the VHD, Windows was activated
Hi Kari,
Can you confirm that the computer at step 5 (I numbered your list) had never had an activated Insider build (especially not 10240)?
I'm wondering if it was possible that the second machine activated because the activation servers recognised the hardware from an earlier activation, and not because of the method you used to transfer?
Absolutely not. I don't do piracy and I detest the fact that you are calling me a pirate. I am expecting an apology.
Those are clean installs using the MS / Insider account which was registered in Insider Program October 2014. I have remained an Insider opting for Fast Ring on each machine and as such I am totally allowed to do a clean install.
If piracy in your books means that a clean installed and automatically without any whatsoever hacking / cracking / tools activated MS / Insider Windows 10 is a pirate copy, then we clearly have different opinion regarding this.
Quoting myself, all according to this:
Hi there
Thanks for clarifying
I've also got a whole slew of VM's all activated.
I think the whole issue will become clearer in the days to come after the intitial download frenzy is over.
I think even Ms has been overwhelmed by the demand for W10.
I agree with you too -- I might have "loosely" interpreted my old TechNet subscription terms and have used the odd "leaked build" - but running Ms Software on machines I actually use for PRODUCTIVE purposes -- no I don't believe in Piracy either.
@Kari
Anybody who even suggests to you that you are pirating software should give you an immediate apology -- you've been one of the most helpful contributors on this Forum as any user whose been around for some time will know and appreciate.
Cheers
jimbo
If your still in the Insider program on these PC's then these are insider builds not the consumer release right? You only just stated this now. I was originally talking about the free upgrade being non transferable. If you had said these were insider builds I wouldn't have said anything about pirating Windows. You can install the Insider release on as many PC's as you want so why go through all of what you posted?
Quote