Windows 10: Win 10 installed another boot loader to an unformatted 2TB Nvme M.2 now I can't access the...

After Installing Windows 10 64bit I found the OS was installed on the wrong Hard Drive. I cloned the right hard drive and removed the original hard drive that had windows installed on it. That didn't work. Then I installed the original Hard drive again and removed the cloned hard drive. This Is a server. Everything worked. I then installed another unformatted hard drive along with 7 other hard drives all formatted NTFS with existing data on them. Everything worked fine the BIOS showed 1 Win boot loader on the main drive that contained the boot loader/ Drive C/ system restore files. Ev

:)

 

M.2 SATA to NVME clone: Windows 10 won't boot

Problem: Windows partition won't boot after cloning M.2 SATA drive to M.2 NVME. Simply returns to BIOS splash screen are restarts boot sequence.

Background: Cloning process was simple raw dd copy. Drive had EFI, Windows 10, and Linux partitions. Cloning preserved exact partition sequence, sizes, and UUIDs.

Linux partition needed minor tweaks to /etc/fstab due to the device names being different (/dev/nvme0n1px vs. /dev/sdax), but boots fine.

The disk is GPT, and I believe the original Windows 10 was UEFI - the Linux installation definitely was.

Boot sequence brings up Linux 'grub' menu first. Choosing the EFI partition then brings up Windows EFI boot menu. Fresh Windows install (see below) boots fine from here, old install fails.

Attempts at solution: I did a fresh Windows install in a spare partition and it boots fine. Using the new Windows installation, I've edited the BCD entry for my original Win 10 install. I have
the correct BCD device, osdevice, and path.

Questions:

• What else needs to be done to make Windows boot again?
• Are there any config file or registry changes that need to be made to account for the SATA to NVME move?
• How do I see boot error messages for a UEFI boot failure? No errors displayed and no log files that I can find in Windows or EFI partitions...

 

My Samsung 970 EVO 2TB NVMe m.2 ssd not being detected in BIOS

I am having problems with the Samsung 970 EVO 2TB NVMe m.2 ssd and it not being detected in BIOS. I recently had to submit my motherboard in RMA for repairs and the drive was working perfectly before, but now it's not being detected. I receive this code
in "Secure Erase" in ASUS BIOS: SMNVMeROM

I have an ASUS ROG RAMPAGE VI OMEGA x299 motherboard and I have 2 other NVMe m.2 drives that do work on the motherboards m.2 slots, and in the dimm.2 adapter slot. It's just that the 970 EVO had my operating system on it, and I'm confused by what SMNVMeROM
means. Did it turn into a ROM file? Should I try putting an operating system on one of the working m.2 drives, to see if I can access the m.2 drive in question(windows disk management)? ASUS wasn't able to help me out in terms of tech. support.

Thanks,

Steve

 

M.2 NVMe not seen when trying to install Win 10 64 bit.

Laptop got hacked and they encrypted the hard drive with bitlocker. I disk part / clean the M.2, then tried to reformat it back Win 10. The install program dose not see the M.2

I put the M.2 in another laptop and Win 10 installed fine.

The M.2 is a PM991 NVMe HP PN:L65187-002 out of a HP 15-dw3000.

HP dose not seem to have the driver for this.

look for the Driver / Standard NVM Express Controller

The HP BIOS is very basic and I have set it back to Default.

Any help is welcome.