Windows 10 is much more forgiving moving between computers than even Microsoft says. I've moved two hard drives with Windows 10 between different computers due to upgrades and repairs and neither one had any problem at all, without even doing the sysprep command. You get a delay in the first boot on the new system and it says something like install new devices on the screen for a few minutes and then just boots up on the new system like nothing happened. Except, that if that version of Windows 10 (Home or Pro) was not on that computer before, it will deactivate itself and you have to enter a valid product key to reactivate it. My computers all have licenses for Windows 10 Pro, so my Windows just stayed activated moving between the computers.

There are two major hardware differences that will, for sure, interfere with just moving the entire hard drive over (either physically, or by cloning it). One is legacy BIOS v. UEFI. To switch between a legacy BIOS computer and a UEFI computer it's easiest to just do a clean install on the new computer and then copy over only the OS (C: drive) partition - replacing the newly installed OS partition with the old OS partition. Then you have to do a quick repair of the boot files.

The other show stopper is if the drive controllers are different types or in different modes. Moving from a SATA controller to an SSD on an M.2 interface, or moving from a SATA controller in IDE mode to a SATA controller in AHCI mode as examples. This can be fixed by booting the old computer into safe mode and deleting the disk controller from device manager first. Shut down. Move the OS over to the new computer, then boot up.

But you do have to have a legitimate way of activating Windows 10 once it is moved/copied over.