Create a clone of W10 on a new NVMe drive.
Create a clone of W10 on a new NVMe drive.
ash_n_brad
04-18-2019, 10:14 PM #11It's known as Norton Ghost 2003. You can find it on Amazon at the link provided. It worked well with both NT and Windows 10.
XxGrenidierXx
05-09-2019, 11:22 AM #12Insert a USB drive and you'll notice the fourth choice appears. It becomes visible between the Windows Boot Menu and the CD/DVD Burner section.
You should use GPT to boot from the NVMe converter first, then create a clone on the new drive. I wouldn’t rely on an outdated Ghost version. Usually I run dd using a Linux boot disk. I just made this change recently, copying from a Samsung 850 Evo to an SX8200 Pro.
1. Install NVMe drivers; if the maker doesn’t offer them, look elsewhere. A helpful link I found: https://www.win-raid.com/t29f25-Recommen...ivers.html
2. Use a cloning tool from the manufacturer—Paragon, Clonezilla, or Micron Media USB. Acronis (by Adata) was my choice; make sure to boot Windows first.
3. After cloning, power down the system.
4. Disconnect the old drive.
5. In BIOS, adjust UEFI settings (like Windows OS Config → UEFI Boot Mode → UEFI). This step was key.
Before jumping on random software, take a moment. Not every suggestion fixes everything. Thanks for the support, everyone—I hope this helps someone later.
x_HmOoDy_KsA_x
05-10-2019, 06:15 PM #14Alright team, I cracked the code. The real challenge wasn’t the tools or the program you’re using—it was understanding how it functions and why it’s gaining traction. Most guides overlook what I covered. Here’s what worked:
1. Install NVMe drivers; if the maker doesn’t offer them, look elsewhere. A helpful link I found: https://www.win-raid.com/t29f25-Recommen...ivers.html
2. Use a cloning tool from the manufacturer—Paragon, Clonezilla, or Micron Media USB. Acronis (by Adata) was my choice; make sure to boot Windows first.
3. After cloning, power down the system.
4. Disconnect the old drive.
5. In BIOS, adjust UEFI settings (like Windows OS Config → UEFI Boot Mode → UEFI). This step was key.
Before jumping on random software, take a moment. Not every suggestion fixes everything. Thanks for the support, everyone—I hope this helps someone later.
goalsavingnick
05-17-2019, 08:59 PM #15It's intentional software with repeated use, especially in NVMe discussions. Naturally, results can vary based on different conditions. Nice that you completed the task!
. Everyone recommends using Paragon, Micron, fixing BCD boot, etc. So yes, it feels random.
ayapasdepb
06-08-2019, 07:34 PM #16It's actually quite unpredictable. Each poster has a unique approach and most succeed with the standard methods. What matters is proper drivers and BIOS configurations. Nobody considers that, and subjects like this are rapidly becoming common topics . Everyone recommends using Paragon, Micron, fixing BCD boot, etc. So yes, it feels random.
It’s not mainly about drivers. You can simply connect your drive before the clone and the system will install the necessary drivers automatically. That’s why boot issues aren’t usually due to driver problems. Remember, Windows needs to load NVME drivers from your storage device, which creates a loop. Your NVME drive will only boot if BIOS settings are correct; drivers will follow later. If something goes wrong, generic drivers will be used. Motherboards and systems are built to manage this situation. I respect the BIOS configuration, but the focus should be on proper setup rather than cloning itself.
bluehypergiant
06-11-2019, 09:41 PM #18The issue isn't always related to the drivers; sometimes it depends on other factors.