Install Win 10 on two hard disks, same computer

I am running Win10 Home, and wanted to start a clean install on my second SSD, slowly and carefully installing / customizing over some time and making backups as I go.
I'd like to be able to still use the current install, until I've installed enough of the programs I use on the fresh install.
I figured I would disconnect whichever Win10 drive I am not using at the time.
I just started doing it by restoring an old "nice& clean" backup with my core programs...
But then I read some and began to realize this potential problem with what I want to do.

If I understand correctly, I might run into problems rebooting from one to the other, and that is because: It is not even legal!
Is that right?

Thanks for the reply, cereberus .
It seems to be working ok, but I'd hate to have it de-authorize me or something.
What Affganos said made me wonder:
"If you have to use that win with same key, then its necessary to switch them between longer time distance (sry my lang). Just the problem will happen if u will switch winX with same cdkey immediately"

I won't be running them "concurrently" (i suppose) as I have been rebooting and I guess that is a long enough time, but don't really know as yet.
Do you know of any trouble I'd have with that?
Thanks!

If you look the computer will have a digital license, not a product key activation. Both of your Windows installations will have the same product key, but it will be the generic product key for a digital license. They will not deactivate just by dual booting them.

cereberus said:

I trust you mean generic product key . Auto correct can be funny sonetimes - lol

You haven't heard about Microsoft's new genetic activation system?

NavyLCDR said:
You haven't heard about Microsoft's new genetic activation system?



Oh - is that the new cloning method ;-).

cereberus said:

Oh - is that the new cloning method ;-).

I have read about so many problems now I was getting paranoid.
I have good backups of everything because I like to personalize my setup, but if a new digit begins to sprout, I'm not sure backups will help me ...
Hopefully I won't have the "cannibalization" I read about (someplace) if i leave both drives attached and just choose in BIOS which to boot... apparently one install was attempting to "fix" the other install, and it was suggested "One Drive" was to blame.
I usually disable most things that i can and only use the calculator app
I love open-source stuff and freebies - That's part of the reason for so many backups and also eventual wondering how "clean" my system is as far as registry,etc. I have gone to stand-alone versions and portable apps a lot lately.
I've been running my current install for about a year and don't have any problems,but there are many installed programs I've found i don't use and ... well, let me confess my OCD with organization
It is a rabbit-hole ... but an ORGANIZED rabbit-hole!
Thanks again !

drexlar said:

Good day everyone
…. install Windows 10 on each of my two hard disks ...
Thanks in advance

I know this is two years later, but out of curiosity, I wanted to do what you wanted to with windows 10 So I did, I put windows on c and d , where as I have one instance of windows running on my computer thus it is the same device. I have 1809 installed on each drive , and only have upgraded C to 1903/1909 (which messed up my battery function - no battery). 1903 did the same with Updates through Windows. Had to manually install it again to fix that. Anyway, back to the issue. Yes, I just booted to D to see what happens and yes, my battery problem is gone. Seems Like I will have to install 1903V2 all over again on C to rid this problem. All this battery bs happens when windows runs an update process, and hangs the system in sum kind of limbo, so it seems

But I am on my D / windows 10 now, and MS has not flagged me with any notices on my computer. My key is OEM embedded to the hardware, so it seems Validation doesn't care what Partition I am running it on, as long as I don't have Two instances running at the same time and it is one the same machine It probably looks to them, Like I reinstalled, and then later downgraded to a previous build, who knows. In anyway, MS doesn't care about it, However, I did do this before with windows 8 pro, and Put it on an VHD, and it thought I was on a second machine, and that messed me up. Had to get a new valid key issued.