- Apr 1, 2010
- 27
- 0
- 18,530
I have an ASUS Z-170P motherboard with a MyDigitalSSD 480GB BPX m.2 SSD. I also have a Mushkin Reactor 1 TB SATA SSD, two Western Digital 1 TB SATA hard drives and a SATA DVD writer.
I installed Windows 10 on the m.2 drive from a USB flash drive and, upon starting Windows, saw that the SATA SSD drive (the Mushkin) with all my data wasn't visible in File Explorer. After some troubleshooting, I went into Windows Disk Management and found the drive without a letter assigned. I re-lettered all my drives and that brought my data drive back in File Explorer. But the strangeness didn't end there.
Every time I booted up, the system would take me to a screen where I would choose Windows 10 or some blank entry that I suppose the system thought was bootable. I went into Windows' advanced system configuration to turn off the dual-boot option. This hadn't happened with previous Windows installations.
Finally, I noticed that, in the BIOS, the boot drive was listed as the Mushkin drive, even though the OS was on the m.2 drive and the system presumably was booting from that drive since it was the only one with an OS installed. When I set the hard drive priority to make the m.2 drive (BPX) the first boot option, however, I got into a loop where rebooting would take me back into the BIOS. It was only upon changing the boot option back to the Mushkin drive that it booted into Windows. I should also note that the OS Type under Secure Boot has to be set on "Other OS" rather than Windows UEFI.
One other observation - the m.2 drive has a single boot partition, and none of the other partitions I've come to expect on the boot drive.
What's going on and can I fix it? Everything is working but I'm not convinced it's configured optimally.
I installed Windows 10 on the m.2 drive from a USB flash drive and, upon starting Windows, saw that the SATA SSD drive (the Mushkin) with all my data wasn't visible in File Explorer. After some troubleshooting, I went into Windows Disk Management and found the drive without a letter assigned. I re-lettered all my drives and that brought my data drive back in File Explorer. But the strangeness didn't end there.
Every time I booted up, the system would take me to a screen where I would choose Windows 10 or some blank entry that I suppose the system thought was bootable. I went into Windows' advanced system configuration to turn off the dual-boot option. This hadn't happened with previous Windows installations.
Finally, I noticed that, in the BIOS, the boot drive was listed as the Mushkin drive, even though the OS was on the m.2 drive and the system presumably was booting from that drive since it was the only one with an OS installed. When I set the hard drive priority to make the m.2 drive (BPX) the first boot option, however, I got into a loop where rebooting would take me back into the BIOS. It was only upon changing the boot option back to the Mushkin drive that it booted into Windows. I should also note that the OS Type under Secure Boot has to be set on "Other OS" rather than Windows UEFI.
One other observation - the m.2 drive has a single boot partition, and none of the other partitions I've come to expect on the boot drive.
What's going on and can I fix it? Everything is working but I'm not convinced it's configured optimally.
Facebook
Twitter
Instagram