Win10 cannot see bootable nvme drive

[TudorFinalBosz]

After I installed a new nvme drive and installed Windows on it, I used AOMEI to erase another internal disk, an older HDD which had no useful data on it. 

The method used was by writing zeroes on it. But the operation was taking too long and I fell asleep. After some hours, I woke up, I checked the PC and AOMEI reported that it finished erasing that HDD, I clicked OK. Then I noticed the HDD drive was MBR, so I selected it and chose to convert to GPT. But the system was getting very sluggish. Everything was just very slow.

 

So I tried to check TaskManager to see what was using so many resources. Everything looked normal, no process or device showed abnormal activity or temperatures. 

 

So I restarted and thought maybe I should check the physical drives. I opened the case and everything looked normal. 

 

Then I restarted again but this time the computer went directly to the Bios. I checked the Boot section and there was no bootable drive listed. In fact, there was no drive at all, even though I have this setup:

- 1 nvme ssd drive I've just installed

- another SATA ssd drive on which I saved some documents

- an HDD that I just erased with AOMEI

 

I realised something must have gone wrong with what AOMEI did and maybe it did some operation on the bootable Nvme drive. So I plugged the Windows installation USB drive and I'm now in Command Prompt, reading the drives with DISKPART. 

ThIs is what I can see when I list volume (pic included, sorry about crappy camera). 

Apparently all the internal disks are visible in DISKPART from the CMD that I'm running off the USB Win10 installation drive. 

 

How do I check if the Nvme drive has a valid boot and if not, how can I fix it. 

Pls help.

Spoiler

 

 

[ChrisLoudon]

Try this:

 

https://neosmart.net/wiki/fix-mbr/#Fix_the_MBR_in_Windows_10

 

Maybe unplug all other hard disks whilst doing this.

 

If that fixes it then plug your other disks back in one at a time and reboot to make sure everything works as it should.

[TudorFinalBosz]

@ChrisLoudon

Thanks. Should I use this method if all the disks, including the Nvme one which had a bootable partition, were using GPT? Wouldn't converting to MBR cause other issues? 

[ChrisLoudon]

3 minutes ago, TudorF said:

Thanks. Should I use this method if all the disks, including the Nvme one which had a bootable partition, were using GPT? Wouldn't converting to MBR cause other issues? 

Good question. I'd be lying if I knew the answer to that.

 

TBH, even if its a small issue with Windows I tend to do a fresh reinstall. It only take 10mins on fast SSD these days and all my files are backed up on OneDrive so its never an issue.

[TudorFinalBosz]

Well, all these tutorials that explain how to fix unbootable drive say that even GPT disks have FAT32 format. 

But all the disks I see listed with Diskpart show that my drives are all NTFS.

The same system booted fine some hours ago, before I used AOMEI to erase that HDD I had no use for. So, the system was working fine with an NTFS formatted drive with GPT partition table as a bootable drive. 

Not sure why all these tutorials assume that the bootable drive must be FAT32. 

[SamClan]

5 minutes ago, TudorF said:

Well, all these tutorials that explain how to fix unbootable drive say that even GPT disks have FAT32 format. 

But all the disks I see listed with Diskpart show that my drives are all NTFS.

The same system booted fine some hours ago, before I used AOMEI to erase that HDD I had no use for. So, the system was working fine with an NTFS formatted drive with GPT partition table as a bootable drive. 

Not sure why all these tutorials assume that the bootable drive must be FAT32. 

I am not sure either. it doesn't sound right. FAT32 is old very old I mean windows 98 old, at least XP. 

 

what you should try, turn off your computer unplug it, wait 5 minits and try to restart it. 

[TudorFinalBosz]

@SamClan

Tried that, but no effect. 

I just went on and installed a new windows on the empty HDD that was erased by Aomei. 

Now I can at least see the other drives from another bootable windows. 

And the other drives seem fine, I can read the data on them, but the Nvme drive doesn't have the boot directory in its root.