![]() GoodSync was another example and I haven't tried wringing out the clone SSD to see what else fails. Or because files aren't exactly in the same place from an OS perspective the links are failing. There seems to be relationships between the SSD and the HDD that aren't being captured in the clone process. After shutdown, reconnected source SSD and it's fine. Went throught the complete clone process, selected shutdown, after shutdown removed the DVD from the drive, connected the cloned SSD to the source cables, kept the source SSD diconnected and rebooted. Shutdown, connected both SSDs, rebooted to the DVD and ran True Image 2016 (64bit) from the DVD. I created a bootable recovery DVD from the Media Builder tool. So I'm doing something wrong that isn't capturing all the windows related relationships in the clone process. I noticed that GoodSync, which is installed on the D:\ drive also lost some activation certificate data in the clone process. Most other programs are installed on the D:\ drive. The Win 10 OS and FSX are loaded on the SSD along with some FSX add ons and few programs such as Norton 360, Office 365 etc. What am I missing? Something in the clone / reboot / windows 10 process something isn't carrying over.ĮDIT: my configuration is C:\ is the Samsumg EVO 500GB SSD and D:\ is a WD 1TB HDD. ![]() When I shutdown and reconnect the original source SSD everything is fine. ![]() Rebooted and when I run FSX there is some dependency that prevents a critical set of gauges form loading properly. When it shut down I changed the cloned SSD cables to source cables and kept the source disconnected. In that process the computer shuts down at completion, so I don't get an opportunity to sign out. Started over fresh and still doesn't work. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |