F5F Stay Refreshed Software Operating Systems Unable to start from the M.2 Samsung 970 SSD drive.

Unable to start from the M.2 Samsung 970 SSD drive.

Unable to start from the M.2 Samsung 970 SSD drive.

D
DeanIsGod
Member
62
12-15-2016, 07:16 PM
#1
I built a new PC for my sister and connected a Samsung 970 M.2 SSD to the motherboard. I installed Windows using an USB drive. The system launched with two installs: one from her old Kingston SSD and another from the new M.2 SSD. When we booted both drives together, a blue screen appeared asking which drive to start from. It suggested the M.2 SSD should work. Now, after moving data from the old Kingston SSD to the new M.2, I removed the old one to use it elsewhere. The issue persists—when I try to boot from the new M.2 SSD, it won’t unless I connect the old Kingston drive again. In BIOS, I switched from UEFI to CSM, but the M.2 still doesn’t boot. My disk manager shows the Kingston SSD formatted, yet the system refuses to recognize it.
D
DeanIsGod
12-15-2016, 07:16 PM #1

I built a new PC for my sister and connected a Samsung 970 M.2 SSD to the motherboard. I installed Windows using an USB drive. The system launched with two installs: one from her old Kingston SSD and another from the new M.2 SSD. When we booted both drives together, a blue screen appeared asking which drive to start from. It suggested the M.2 SSD should work. Now, after moving data from the old Kingston SSD to the new M.2, I removed the old one to use it elsewhere. The issue persists—when I try to boot from the new M.2 SSD, it won’t unless I connect the old Kingston drive again. In BIOS, I switched from UEFI to CSM, but the M.2 still doesn’t boot. My disk manager shows the Kingston SSD formatted, yet the system refuses to recognize it.

N
nexusRawr
Member
198
12-17-2016, 04:06 AM
#2
Not my intention to reference
N
nexusRawr
12-17-2016, 04:06 AM #2

Not my intention to reference

B
BreezyTaco
Member
61
12-18-2016, 08:29 PM
#3
I used a secure transfer method to move the data.
B
BreezyTaco
12-18-2016, 08:29 PM #3

I used a secure transfer method to move the data.

S
Sunahh
Posting Freak
863
12-18-2016, 10:15 PM
#4
Using Windows File Explorer, moved user data such as game saves, photos, and homework. No Windows files were transferred; only personal information was backed up. I performed a clean installation on an M.2 drive using the Win10 Media Creation Tool.
S
Sunahh
12-18-2016, 10:15 PM #4

Using Windows File Explorer, moved user data such as game saves, photos, and homework. No Windows files were transferred; only personal information was backed up. I performed a clean installation on an M.2 drive using the Win10 Media Creation Tool.

B
blue10x
Member
74
01-05-2017, 11:06 AM
#5
From the fresh installation, does the computer start up on the M.2 slot? Also, was this fresh install done without any additional drives installed? Windows sometimes places the boot loader on the incorrect drive.
B
blue10x
01-05-2017, 11:06 AM #5

From the fresh installation, does the computer start up on the M.2 slot? Also, was this fresh install done without any additional drives installed? Windows sometimes places the boot loader on the incorrect drive.

B
brobear7
Posting Freak
892
01-05-2017, 02:31 PM
#6
I believe that's the solution now. I set up a 50GB partition on the M.2, reinstalled Windows there, took out the old Kingston SSD, and it started booting without issues. The M.2 appears in the boot order, which resolved the problem. However, I still prefer using the Windows I installed on the main partition of the M.2, including everything we moved and updated yesterday, instead of relying on the new test partition. One issue fixed, another appears.
B
brobear7
01-05-2017, 02:31 PM #6

I believe that's the solution now. I set up a 50GB partition on the M.2, reinstalled Windows there, took out the old Kingston SSD, and it started booting without issues. The M.2 appears in the boot order, which resolved the problem. However, I still prefer using the Windows I installed on the main partition of the M.2, including everything we moved and updated yesterday, instead of relying on the new test partition. One issue fixed, another appears.

P
ProTurkeyDN
Junior Member
34
01-07-2017, 05:03 AM
#7
It's not possible to simply transfer the bootloader to fix an existing partition issue.
P
ProTurkeyDN
01-07-2017, 05:03 AM #7

It's not possible to simply transfer the bootloader to fix an existing partition issue.

A
Andrewlol10PT
Member
53
01-09-2017, 05:56 AM
#8
I just reinstalled Windows on the M.2 drive, connected just the USB, and it functioned properly. Thanks!
A
Andrewlol10PT
01-09-2017, 05:56 AM #8

I just reinstalled Windows on the M.2 drive, connected just the USB, and it functioned properly. Thanks!