Bios no longer recognizes the NVMe drive once you removed it and then reinstalled it.
Bios no longer recognizes the NVMe drive once you removed it and then reinstalled it.
I proposed to set up a brand new Windows 10 installation on my friend's M.2 NVMe storage, but I only have one M.2 port available on my motherboard, so I shut down and removed the existing drive. I installed it and ran a trusted Windows installer that I frequently use. Everything proceeded without issues, so I powered off and reinstalled my original drive.
Problem
I possess a 500GB SATA SSD with an outdated Windows installation still connected (in case I overlooked something during the upgrade to my 2TB NVMe), and now my computer starts from that old SSD. It boots normally, so I accessed BIOS to configure the boot order. There, the NVMe appears by name, but there’s no mention of a Windows install or bootable Windows option—only the manufacturer details. When I try to boot anyway, I encounter a black screen with the message:
"Reboot and Select proper Boot device, or Insert Boot Media in selected Boot device and press any key."
Temporary Workaround
If I turn off all BIOS boot settings and unplug my previous Windows SATA drive so only the NVMe remains connected, the system somehow boots to the correct storage. This seems to happen because in BIOS it shows zero selected options and zero available drives, yet it still works.
Desired Outcome
I need the bootable Windows installation on the NVMe to display correctly in BIOS, allowing me to choose it as the preferred boot device. Additionally, I want my old SATA drive to be recognized as well, so the system boots to the right drive even when both are connected. This was the normal behavior before I removed the original drive and used the M.2 slot for Windows installation.
Have you considered using only the NVMe drive, starting from the USB install media, and performing a complete fresh installation? Ideally, using the latest installation media rather than the same one you've been using for a long time. The schedule here can be a bit confusing to follow.
I'm also puzzled about why someone would install Windows on their friend's NVMe drive in your PC—that’s clearly a poor practice. It raises questions about what else might be happening.
The OS must be set up once the drive is placed in the system where it will remain.
Do not install here, then move to there.
But I have a windows install on the drive... It was previously working and I want to keep that data there. Maybe I can try to run it through a repair process...
I didn't know it would be an issue. It's just an SSD right, why should it care where it was installed... I mean, I believe you, I just didn't see it that way before and still don't know why it's an issue.
Windows doesn't prefer being transferred between different physical hardware setups. We all hope it were more modular, but it isn't. Transferring this drive to another system can result in three possible scenarios:
1. It functions perfectly
2. It fails entirely
3. It "works," yet you're dealing with problems for weeks or months.
#3 is the most common outcome.
A Windows installation has no worth. It's important to be ready for the possibility of needing to reinstall Windows. I believe, based on what you mentioned, that there haven't been any backups made of anything? Windows isn't designed in a modular way. This is worrying because if you're handling things this way, other issues might exist as well. Simply erase the drive and install Windows correctly, then remove it from consideration.
Since Windows functions as an operating system, it enables various software to interact with hardware through drivers. Each piece of hardware typically requires its own distinct driver. When you set up Windows on a drive, it adapts itself to the machine's specifications. Otherwise, you might simply copy the drive and alter the license key.
So when you install Windows on a storage device in one computer, it identifies the hardware—like the Gigabyte Z720—and downloads the necessary drivers for that chipset, ensuring compatibility with the i7 7700K processor and the USB interface. It also fetches drivers for the Xonar soundcard, configures the onboard Wi-Fi, and sets up the GeForce GTX970 graphics card. Once everything is configured, it completes the installation.
After finishing, you power off your computer, remove the drive, and insert it into another machine. Windows restarts and begins searching for compatible hardware. It then prompts you with questions about missing components—such as the Z720 chipset, Wi-Fi functionality, or the Radeon 6800XT graphics card—and continues to adjust itself until it functions properly.
In essence, this process resembles fitting an engine into a vehicle and expecting it to work seamlessly in another car; over time, even with adjustments, issues can arise.
You're all right, I messed up. But the M.2 in my friend's system is actually working! It was taken out briefly and put back, yet my BIOS still doesn't recognize it—unless there are other bootable drives available, then it loads just fine. This is quite tricky. I'll share an update once I solve it. Thanks for your support.
I can't display or upload images directly, but you can follow these steps:
Open Disk Management in Windows, take a screenshot, and share the link here.