Cannot Restore Windows to NVMe M.2 SSD

Page 2 of 2 FirstFirst 12

  1. Posts : 28
    Windows 10 Pro
    Thread Starter
       #11

    Bree said:
    Your screenshot clearly states that the source you used was an image of a 1TB MBR disk.

    Attachment 249099
    Ah, I see it now. That's my new SSD. I installed it in June and made this BU in July. It is, indeed, a 1 TB SSD, but the Windows installation on it came from my 2 TB HDD. I had been booting from the HDD prior to June.

    - - - Updated - - -

    Bree said:
    Your source backup is a system image of an mbr disk, typical of a system set up in legacy bios mode.
    Your destination disk is a gpt disk,
    Everything that I've checked on this computer says that the SSD is MBR and cannot be converted to GPT. Here's a screenshot from my newly-installed Disk Management screen:

    Cannot Restore Windows to NVMe M.2 SSD-2019_09_28_04_48_111.jpg

    That's only one of several places that shows that my SSD is MBR. I don't know why Macrium Reflect thinks otherwise. I've tried running MBR2GPT on this drive several times, but I always get an error message stating that this kind of drive cannot be converted to GPT.

    Bree said:
    the extra partitions beind a Fat32 EFI partition and a 16MB MSR partition, typical of a UEFI system. In order to be able to replace the C: drive with the one from the backup the destination system needs to be the same type as your backup, an mbr legacy instsall.
    Well, my system says they are the same. MR actually did install the BU to the C:, but I couldn't boot from it. A quick search shows there is a way to install an MBR BU to a GPT disk:

    How to Restore an MBR System image to UEFI/GPT (Convert, GPT, MBR, Restore)

    - - - Updated - - -

    I followed Macrium Reflect's directions in creating a rescue boot stick with MR and WinPE on it, ran the "Fix Boot Problems" option in MR, which now, at least, allows me to get an error message when I try booting my machine, instead of just a black screen. The error message says, in brief, "The Boot Configuration Data for your PC is missing or contains errors." The BCD was one item that I opted for MR to fix!
      My Computer


  2. Posts : 17,256
    Windows 11 Pro
       #12

    I should have clarified my post #6. Do the clean install to the wiped clean SSD as I described in Post #4. Then, however, to restore ONLY the C: drive partition of your backup image over the top of the newly created C: drive partition on the SSD, you have to boot the computer from a Macrium Reflect Rescue Drive (probably a USB flash drive). Boot the computer from the Macrium Reflect Rescue Drive. Open you image file. Select ONLY the C: drive partition to restore. You might have to delete the new C: drive partition on the SSD before you can restore the C: drive partition from the image file. You should be working ONLY with the C: drive partitions, leave all other partitions completely alone.

    After the C: drive partition is restored from the backup file, then under the restore menu, select the utility to fix Windows boot problems. Run that utility. Then try to boot the computer from the SSD.
      My Computer


  3. Posts : 28
    Windows 10 Pro
    Thread Starter
       #13

    That worked! Thank you! I'm amazed that worked! Four days after my PC crashed, I finally have it back, 99.99% (Dropbox is complaining that it has been moved or deleted, but I don't actually use it) functional.

    I think the problem began when Microsoft did a massive update to my system the previous night. I got a message saying that support for the April 2018 version would end at the end of November, so I would need to update by then. I chose to update right then. I'm told (on another help forum) that Windows might have seen my other drives and stuck stuff on them that should have gone on the SSD. I was told that I should have done the update with all my other drives disconnected, especially the drive with my old Windows boot partition on it.

    - - - Updated - - -

    This fix required me to use two, unused USB Flash drives (8+ GB each), convert one to Windows 10 bootable repair media, convert the other to Macrium Reflect bootable repair media (with Windows PE), use my external HDD with my Macrium Reflect disk images stored on it and my original Windows 7 Product Key that I had to recover a few months ago when I initially installed my SSD. I didn't know how to do half of the things that I just did (like, how to create a Macrium Reflect bootable repair Flash drive).

    Oops; it looks like Adobe is choking on my recovered drive. My Adobe apps are still listed in the menu, but they won't launch and the icons are turned to generic blank sheets. Ugh!
      My Computer


  4. Posts : 17,256
    Windows 11 Pro
       #14

    Then it sounds like the Windows in the image file was corrupted when you imaged it.
      My Computer


  5. Posts : 28
    Windows 10 Pro
    Thread Starter
       #15

    NavyLCDR said:
    Then it sounds like the Windows in the image file was corrupted when you imaged it.
    Possibly. However, it occurred to me that I probably have Adobe Photoshop on one of the other partitions that you told me not to install when I was trying to get my system to boot. Now that my system is booting, I think I'll give that partition a shot.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 06:35.
Find Us




Windows 10 Forums