F5F Stay Refreshed Hardware Desktop Bios detects new NVMe as bootable but fails to recognize it as a real drive.

Bios detects new NVMe as bootable but fails to recognize it as a real drive.

Bios detects new NVMe as bootable but fails to recognize it as a real drive.

W
Waverabbit
Senior Member
643
05-16-2019, 01:43 AM
#1
Hey everyone, I've been working on this for about seven hours and still nothing. Back then, I was using a WD Green SATA M.2 with my ROG B350-F board and a Ryzen 5 3600. I just swapped it out for a new Samsung 980PRO NVMe drive, planning to install Windows 10 fresh on the 980 Pro. I did the usual setup and picked the NVMe option. After the install, I ran into an error—Windows setup couldn't reinitialize the deployment engine and I had to quit the installer. Now, in the BIOS, I see the bootable drive listed, but it gives me an option to boot from it. However, the BIOS doesn’t recognize the drive and says the M.2 slot is N/A in EZ mode. I’m using the default settings now, which means CSM is on, AHCI enabled, Secure Boot active. Trying to boot the NVMe just brings me back to the BIOS again. I think the installer might have partially installed the partition and it’s stuck in some kind of state. Maybe the BIOS is detecting it but not fully recognizing it? I’m really confused and don’t know what to do next. I’ve tried reseating the drive, resetting BIOS settings, disabling CSM, turning Secure Boot on/off, and checking all combinations. All of these either stop me from booting or just don’t show the drive at all. Any advice would be greatly appreciated!
W
Waverabbit
05-16-2019, 01:43 AM #1

Hey everyone, I've been working on this for about seven hours and still nothing. Back then, I was using a WD Green SATA M.2 with my ROG B350-F board and a Ryzen 5 3600. I just swapped it out for a new Samsung 980PRO NVMe drive, planning to install Windows 10 fresh on the 980 Pro. I did the usual setup and picked the NVMe option. After the install, I ran into an error—Windows setup couldn't reinitialize the deployment engine and I had to quit the installer. Now, in the BIOS, I see the bootable drive listed, but it gives me an option to boot from it. However, the BIOS doesn’t recognize the drive and says the M.2 slot is N/A in EZ mode. I’m using the default settings now, which means CSM is on, AHCI enabled, Secure Boot active. Trying to boot the NVMe just brings me back to the BIOS again. I think the installer might have partially installed the partition and it’s stuck in some kind of state. Maybe the BIOS is detecting it but not fully recognizing it? I’m really confused and don’t know what to do next. I’ve tried reseating the drive, resetting BIOS settings, disabling CSM, turning Secure Boot on/off, and checking all combinations. All of these either stop me from booting or just don’t show the drive at all. Any advice would be greatly appreciated!

M
193
05-16-2019, 03:26 AM
#2
I'm unsure if this assists, but I encountered an issue when I added the identical Samsung drive to my system. After installation, Windows failed to recognize it and couldn't initialize. I used AOMEI Partition Assistant which successfully detected and formatted the drive for boot use. I created a clone of the operating system onto the NVME drive with Samsung Data Migration software, and everything functioned perfectly. I kept the Samsung SSD on the workstation as a backup, performing a monthly OS clone there.
M
McGamerPro2000
05-16-2019, 03:26 AM #2

I'm unsure if this assists, but I encountered an issue when I added the identical Samsung drive to my system. After installation, Windows failed to recognize it and couldn't initialize. I used AOMEI Partition Assistant which successfully detected and formatted the drive for boot use. I created a clone of the operating system onto the NVME drive with Samsung Data Migration software, and everything functioned perfectly. I kept the Samsung SSD on the workstation as a backup, performing a monthly OS clone there.

H
Haamuh
Member
107
05-16-2019, 07:25 AM
#3
Thanks for the input—currently I’m limited to using just one M.2 drive on the system. Cloning and external software won’t work without a dedicated external enclosure. It seems like this might be a common challenge others have faced too.
H
Haamuh
05-16-2019, 07:25 AM #3

Thanks for the input—currently I’m limited to using just one M.2 drive on the system. Cloning and external software won’t work without a dedicated external enclosure. It seems like this might be a common challenge others have faced too.