

There are a few posts about this in the forums and an excellent KB article about when Reflect can and does retain disk signatures. Or you could take an image of the drive, detach it from the system then restore it to the new drive to keep they same disk signature. I believe you could perform the clone operation via a Linux recovery boot media and do this. This is a limitation of the operating system, not Reflect. Thing is, in the Windows environment, two hard drives attached at the same time CANNOT have the same disk signature. Maybe you can make this an option in the "Cloning" I would like the clone to "leave the disk signature alone".

Once the clone is complete it changes the disk signature on the "testing" SSD which would be OK normally, but I use a program that lets me use the same drive letter whenever the "testing" SSD is mounted, which is based on the disk signature. I periodically clone from the "normal" SSD to the "testing" SSD which is done while in Windows (Not the PE environment). I have two of the same SSDs that are hot swappable, one I use for "normal" stuff and the other for testing. Would be nice if the "Clone" operation did NOT change the disk signature.
