Cloning Roon’s database directories at the disk level will cause some confusion and we don’t recommend it. On first run, Roon generates identifiers for the Roon Core, audio devices, and other stuff, and when you blindly duplicate these, it’s difficult for Roon to tell the two sets of identifiers apart.
Instead of cloning Roon’s database at the drive level, I suggest making a backup using Roon on the source machine, and restoring it on the target machine.
Then, to get out of trouble with the audio devices, exit roon, delete the c:\Users\YOUR USERNAME\AppData\Local\RAATServer folder and then restart Roon. You will have to re-enable the audio devices on the new machine, but they should get fresh identifiers and no longer conflict with each other.