If your motherboard doesn't even see the SSD, how did you restore your image onto it in the first place?  Did you do that using another PC or external enclosure and then install the SSD?  Even if you did that, does the Rescue Media see that disk at all if you check the Backup tab to view all of your disks?  If Reflect can't see the disk at all, then ReDeploy definitely won't work.  If Reflect DOES see the disk, then your motherboard hardware support isn't the issue.  Did you try running Fix Boot Problems after running ReDeploy?

The fact that the motherboard isn't listing your SSD as a boot device doesn't necessarily mean it's not detecting the SSD itself.  Some systems that boot in UEFI mode don't list boot options that reside on local storage until the specific bootloader file on that SSD has been registered into the firmware.  UEFI systems do not work like Legacy BIOS systems where you just choose to boot from "a device".  On UEFI you choose to boot from a specific bootloader file on a specific partition of a specific disk.  Windows Setup handles that bootloader registration if you're installing from scratch, but an image restore won't, especially if you did it on a completely different system.  But Fix Boot Problems can fix that.

On that subject, make sure your motherboard boot mode matches what's appropriate for your disk layout.  If your SSD is set up using MBR, you'd need to boot in Legacy BIOS.  If it's set up for GPT, then UEFI is the correct choice.

And on the subject of Fix Boot Problems, make sure you boot the Rescue Media itself in the correct mode for the OS you're trying to fix.  If Rescue was booted in UEFI mode, you'll see "[UEFI]" at the end of the title bar at the very top of the display.  The reason this matters is because if you boot Rescue Media in UEFI mode, it will attempt fixes appropriate for a GPT disk to boot in UEFI mode.  If you boot it in BIOS mode, it will attempt Legacy BIOS fixes.  And some motherboards support both BIOS and UEFI boot simultaneously, so it's possible to boot in either mode, which can cause problems.

+x

 

jphughan - 26 January 2020 11:41 PM

^ Drac144 is correct. ReDeploy just looks at and works with what’s on disk. It doesn’t care how it got there, and it’s available as a standalone tool in the Rescue environment, so no need to restore anything. And yes, expect to install more drivers within Windows. You MIGHT need to provide drivers to the ReDeploy wizard itself if none of the drivers built into Windows or already otherwise available on your disk will work for boot-critical components, but the newer your version of Windows (you didn’t mention what Windows version you're running), the less likely that will be an issue.

You will however need to make sure your new motherboard’s boot mode — Legacy BIOS or UEFI — matches your old system. ReDeploy does NOT deal with that, because Windows sets itself up on disk very differently depending on whether it will be booted in BIOS or UEFI mode. The former uses an MBR disk while the latter uses a GPT disk and different partition layout. If your old system used BIOS mode and your new system only allows UEFI (or you want to switch to it anyway, which honestly isn’t a bad idea), then Macrium does provide a KB article showing how to perform a custom restore of a Legacy BIOS/MBR environment backup onto a GPT disk such that the restored backup will be bootable in UEFI mode. It involves some prep work on the target disk and some custom partition restore measures. Microsoft also has an MBR2GPT in-place conversion tool, but that can be more finicky.

Hi,
i have 1 image of my old ssd on Windows 10. MBR of course. no way to work with mbr2gpt! if i restore the image to my new SSD empty with GPT partition  (same Samsung EVO but bigger, no other HW changes) Reflect convert my image to MBR again......it is crazy and useless. Microsoft does not update the OS anymore unless on GPT. my MB of course supports UEFI. any idea? am i doing something wrong?

Have you checked whether the MBR2GPT utility is available inside Rescue?  Open Command Prompt and type MBR2GPT to see if you get a response.  If so, then you should be able to use it to perform a conversion if you supply the right parameters.  Or better yet, follow this Macrium KB article that specifically addresses how to restore a backup of an MBR disk from a Legacy BIOS system onto a GPT disk in a way that will make it usable on a UEFI system.

thank you!
i discovered the same kb earlier today.
followed carefully the instructions.
it is done!!!! not it is finally GPT
the only difference i formatted the drive as NTFS, not fat32 (for USB pen)

Congrats! Although you really should use FAT32 because most UEFI systems won’t boot in UEFI mode from NTFS sources. The reason is that unlike BIOS booting where boot code is stored in a specified part of a partition and can include a file system driver, a UEFI system has to point to a specific bootloader file, which means it must natively understand the file system it’s booting from without loading any additional code. NTFS support is optional in the UEFI spec and not widely implemented, whereas FAT32 support is mandatory.

You can create a multi-partition flash drive with a small FAT32 partition for Rescue Media and a larger NTFS partition for general purposes storage, FYI.

Also, consider enabling Secure Boot now that you’re booting Windows in UEFI. It’s a nice anti-root measure.

i didn't know this
my system is booting fine from NTFS ( MB Asus Z170 pro)

but i am still in time to throw everything away, clean the new ssd again and start from scratch with the FAT32 and the image

my BIOS really is saying Windows Boot Manager not UEFI.
do you think it is worth the effort?

Windows update is working now....no more MBR

HOLD ON!!

I didn't mean to suggest that you reformat your Windows volume as FAT32, which you should absolutely not do.  I don't think Windows even supports being installed on FAT32 partitions anymore.  On disks containing full OS installations that are set up to boot in UEFI mode, there's a small hidden FAT32 partition called an ESP (EFI System Partition), and that contains the bootloader files that then turn around and load Windows.  You can see that partition in Reflect itself.

My post was simply saying that you should consider formatting your Rescue Media flash drive as FAT32 for compatibility, because flash drives don't typically have the partition structure I just described above set up.  But if you're able to boot from your Rescue Media while it's formatted NTFS in UEFI mode -- verify by looking for "[UEFI]" at the end of the title bar at the very top of the Rescue environment -- then I guess no worries.  ASUS might have built a UEFI NTFS driver into their motherboard firmware.  Just be aware that you might not be able to use that Rescue Media on other systems, including a system you might find yourself moving to unexpectedly after a failure of that one

Hi again and thanks for the support

i guess something went wrong with my first disk Image using the new ssd,

i got I/O error inside Reflect!!!!!!
i had to boot from the Rescue Media and fix the Boot problem

i should submit a support ticket and upload the logs.
BUT from Paramount i am redirected to the Zoho portal where the only option is to login (no register option) , but my Macrium Forum password does not work
i am doing something wrong?
i attach a simple Disk Manager screenshot.

To my knowledge, the support portal and forum do not use a common user credential database, but I'm not sure since I haven't submitted a support ticket in a very long time. Sorry!  You can always email support at macrium dot com, fyi.

thanks
i wrote to them with Logs and msconfig file, and already received an acknowledge
i have just to wait
.