Windows 10: Add a new disk and move windows to the new disk, will I needs reactivation windows?

I have Windows 10 LTSC 2019 installed on my computer, It licensed with a key not digital license

The hard drive where windows on is a SMR hard disk and it is too slow, I'm planning add a SSD and clone whole windows partition to SSD, The old HDD will still connected to computer.

Now im worring about the license, will i needs reactivation Windows after boot from the new SSD?
And also will i needs reactivation Windows after removing the old HDD from my computer?

:)

 

How to eliminate Windows from disk

I installed windows on a hard disk on which were present stored data, without formatting the disk and then leaving the data there. I would now like to uninstall / remove windows and installed folders, without formatting the disk as they are always present stored data.

 

Disk bloat in Windows 10 Fall Creators Update

Is it my imagination, or does the Windows 10 Fall Creators Update consume an additional 20-30GB of disk space over the previous Creators Update release? Unfortunately, I didn't log my disk usage before the upgrade, but now my C: drive has 56GB of stuff, and I know it wasn't anywhere near that full before. I've run "Disk Cleanup -> Clean up system files" and selected everything on the list, including remove previous version of Windows. I also emptied my Recycle Bin, my Temp folder, \Windows\Temp folder, and \Windows\SoftwareDistribution\Download folder. Finally, I ran Wise Disk Cleaner to delete assorted application garbage.

Has anyone else noticed the bloat in Fall Creators Update?

 

I put in a new SSD, copied my old disk using Samsungs SW, and want to make my original disk a second disk.

I run Windows 10 and have just had the same problem.

A technet blog (Fixing Disk Signature Collisions) says the following of the above suggested solution::

"When you chose the Online menu option, Windows will without warning generate a new random disk signature and assign it to the disk by writing it to the MBR. It will then be able
to process the MBR and mount the volumes present, but when Windows updates the disk signature, the BCD entries become orphaned, linked with the previous disk signature, not the new one. The boot loader will fail to locate the specified disk and boot files
when booting from the disk and give up, reporting the following error:"

My question, multi-part, therefore, before I try the above solution, is this:

• The above blog is from 2011, and most of the reports I've read precede Windows 10 so that I'd hope MS would have corrected the deficiency by now. Is the above quote still valid (for Win10) or has Win10 corrected it?

• If it is still true, I read it to say only that you can't boot from that disk. Apparently you could boot the machine from a different boot disk with that disk attached?

• If it is true, is the procedure described in the technet blog still valid, or no?