Segmentation Fault using Linux based Universal Restore (Windows 10)
Hello,
I'm having trouble restoring a full system backup to new hardware. I've tried using the linux-based Universal Restore media mounted on a flash drive. After I'm presented to launch True Image, the application throws a segmentation fault while enumerating local drives. I've tried disabling secure boot as advised by another post with no luck.
I saw another post advising to try the Windows PE method with the Windows 10 PE kit. It launches straight into the Universal Restore dialog where it shows no OS found (as expected). From what I understand, the restore process is to first restore the backups to the local drive(s) and then use the Universal Restore dialog to adjust the Windows partition(s) with new drivers and such to make it bootable. How can I access the image restore functionality using Windows PE?
Hardware:
Destination drives: 2 NVME M.2
Source of backups: USB3 external harddrive
Imaged flash drive of Universal Restore media: USB3 64GB
Thank you


- Log in to post comments

Thank you for the quick response.
I was able to restore the backups to both of my NVME SSD's. While restoring, I selected "Recover Disk Signature" for both drives. Previously, in the BIOS both drives were correctly recognized as a Firecuda NVME drive - now only 1 drive is recognized as a Firecuda device and the other has a generic name of "NVME SSD". Could this be related to restoring with the "Recover Disk Signature" option?
I am able to boot into Windows but the generic "NVME SSD" device is not displayed in disk management. I booted into Seagate's SeaTools and it does not recognize it as a Firecuda device. I have confirmed I am able to read/write to the drive using their tool.
Is there a known fix for this situation?
Thank you
- Log in to post comments

Jeffrey, if the backup images were from the same NVMe SSD's then the disk signatures should be identical to how they were when the backup was created, so if the drives displayed correctly then, it should do so after restoring the backup and signature.
I would more suspect that the drive showing as a generic NVMe SSD has the wrong driver installed so would suggest looking more closely in the Device Manager to see what the correct SSD driver is showing, then change the driver on the incorrect SSD to that same driver if they are both the same type of drive.
- Log in to post comments