F5F Stay Refreshed Hardware Desktop Installation complete but starting issues with the SSD even though it's a brand-new Windows 10 setup

Installation complete but starting issues with the SSD even though it's a brand-new Windows 10 setup

Installation complete but starting issues with the SSD even though it's a brand-new Windows 10 setup

T
TheRedPhoenixx
Member
Find
95
05-17-2016, 01:47 AM
#1
Hello! You recently swapped your old hard drive for a new SSD to use as your boot drive. You thought the installation would go smoothly with Windows 10, but you encountered some unexpected issues. The OS didn’t prompt for a key, yet it performed tasks and installed files. In your BIOS settings, the SSD wasn’t recognized as a boot device, and after removing the HDD, you received a "Boot Device Not Found" message. Are you missing any steps or settings?
Reply
Reply
T
TheRedPhoenixx
05-17-2016, 01:47 AM #1

Hello! You recently swapped your old hard drive for a new SSD to use as your boot drive. You thought the installation would go smoothly with Windows 10, but you encountered some unexpected issues. The OS didn’t prompt for a key, yet it performed tasks and installed files. In your BIOS settings, the SSD wasn’t recognized as a boot device, and after removing the HDD, you received a "Boot Device Not Found" message. Are you missing any steps or settings?

Reply
Reply
S
Selini
Member
Find
161
05-17-2016, 03:49 AM
#2
The issue involved handling windows volumes. I tried using volume 4 instead of the default, which then got added to the Windows setup.
Reply
Reply
S
Selini
05-17-2016, 03:49 AM #2

The issue involved handling windows volumes. I tried using volume 4 instead of the default, which then got added to the Windows setup.

Reply
Reply
_
_ReflexLegend_
Member
Find
112
05-17-2016, 05:32 AM
#3
Windows sometimes installs the bootloader to the incorrect drive when it finds one already containing a boot sector. This is quite unusual and problematic, yet Microsoft continues to support it. The main issue arises when you remove your hard drive or delete the old boot sector, preventing Windows from starting. To fix this, temporarily disconnect all drives except the one you want Windows on, install Windows, and then reconnect the remaining drives. Now the bootloader will be on the correct drive.
Reply
Reply
_
_ReflexLegend_
05-17-2016, 05:32 AM #3

Windows sometimes installs the bootloader to the incorrect drive when it finds one already containing a boot sector. This is quite unusual and problematic, yet Microsoft continues to support it. The main issue arises when you remove your hard drive or delete the old boot sector, preventing Windows from starting. To fix this, temporarily disconnect all drives except the one you want Windows on, install Windows, and then reconnect the remaining drives. Now the bootloader will be on the correct drive.

Reply
Reply