Can't boot windows 10 unless I go through Boot manager??

[chocolovee]

I have a custom build computer and I just installed Windows 10 OS on my SSD drive.

The Windows installation was fine, but I have major issues booting it.

So this is my bios boot order:

When I boot though, this comes up:

The only way to get into Windows is by going to the boot menu:

And choosing the Windows boot manager option:

What's going on? Does it have anything to do with the disk partitions?

How do I fix this????

Thank you!!!!

 

[Colif]

None of your images work, they all 404. You best off uploading them to imgur and sharing the links here. And then we can get a little further.

what are specs of PC? What motherboard do you have so I can look in manual?

 

[LukeFatwalker]

This is caused by one of two things:

1) Hard drive is not connected to the original SATA port found in the original build. If you changed a hard drive recently and didn't connect to the original port this could cause this.

2) There's a loose, missing, or otherwise wrong cabling job. Ensure everything is hooked up correctly, when in doubt, consult your original manuals.

Before you do anything here, back up your data. Don't want to do irreversible damage to the computer and lose your data. Using a disk imager like Macrium Reflect or Drive Cloner Rx will work.

 

[chocolovee]

None of your images work, they all 404. You best off uploading them to imgur and sharing the links here. And then we can get a little further.

what are specs of PC? What motherboard do you have so I can look in manual?

Hello! I just updated the pictures, please let me know if this works. My motherboard is the msi 2170A KRAIT GAMING.

Other specs:

Corsair Vengeance LPX16GBDDR4 2400MHz CL14DualChannel Kit (2 x 8GB)
MSI Z170A Krait Gamingw/ DDR4 2400, 7.1 Audio, Gigabit LAN, SLI/ 3-Way CrossFireX($174.99)
Cooler Master Hyper T2 CPU Cooler
Asus Z170M-PLUS
GSKILL 16GB PC4-22400 Dual Channel DDR4 (2 x 8GB)
Intel CoreTMi5-6600 Processor, 3.30GHz w/ 6MBCache

The SSD drive in question is:

OCZ ARC 100 2.5" 240GB SATA III MLC Internal Solid State Drive (SSD) ARC100-25SAT3-240G

 

[chocolovee]

This is caused by one of two things:

1) Hard drive is not connected to the original SATA port found in the original build. If you changed a hard drive recently and didn't connect to the original port this could cause this.

2) There's a loose, missing, or otherwise wrong cabling job. Ensure everything is hooked up correctly, when in doubt, consult your original manuals.

Before you do anything here, back up your data. Don't want to do irreversible damage to the computer and lose your data. Using a disk imager like Macrium Reflect or Drive Cloner Rx will work.

Thank you so much!
1) I'll take a look when I check home, to make sure it is hooked up the same way as it was previously. How come I'll still able to boot up via boot manager though?
2) I'll also take a look!

All of my important data is on another external drive (E, the SSD only has my operating system. I'll check out these disk imagers as well.

Thanks!

 

[LukeFatwalker]

This is caused by one of two things:

1) Hard drive is not connected to the original SATA port found in the original build. If you changed a hard drive recently and didn't connect to the original port this could cause this.

2) There's a loose, missing, or otherwise wrong cabling job. Ensure everything is hooked up correctly, when in doubt, consult your original manuals.

Before you do anything here, back up your data. Don't want to do irreversible damage to the computer and lose your data. Using a disk imager like Macrium Reflect or Drive Cloner Rx will work.

Thank you so much!
1) I'll take a look when I check home, to make sure it is hooked up the same way as it was previously. How come I'll still able to boot up via boot manager though?
2) I'll also take a look!

All of my important data is on another external drive (E, the SSD only has my operating system. I'll check out these disk imagers as well.

Thanks!

If you've changed the cabling it's smart enough to know that there's still a drive there, but it's not the default connection that you originally had, hence why it's essentially asking you to confirm which drive it is. If you change it back, it shouldn't be asking you to confirm any more.