Unsolved

This post is more than 5 years old

13 Posts

79203

April 5th, 2017 02:00

Why Windows Boot Manager is not in UEFI list?

Hi.

I am installing Windows 10 into Samsung EVO 850 SSD. I have no other drives installed. This SSD is complitely empty.

Computer: Alienware 18 2013. 2x GTX 880m. i7-4910MQ. 4x 4GB RAM. And at the momenta my own 250GB SSD. (On the "Fixed HDD" slot)(I removed the 1TB HDD and cache SSD as they caused other problems)

In the manual it says that in the UEFI boot menu there is Windows Boot Manager, as well as UEFI Onboard LAN IPv4 and IPv6.

Problem is, if I install Windows 10 in UEFI boot, (settings below) I can not boot from the SSD. I can seet it in Main in BIOS, but not in Boot. (It will be installed in GPT format)

The boot settings:
Windows 8 fast boot: enabled,
usb hotkey: disabled,
Secure boot: enabled,
Load Legacy options rom: disabled,
Boot list option: UEFI,
Secure boot mode: Standard,

Under the Advanced window  'SATA Operation is set to 'AHCI'.

If I boot in Legacy, the installer gets stuck in the 'Where do you want to install Windows" screen as it says "Windows cannot be installed on this disk. Hardware may not support..." (Attachment picture).

I have used diskpart to clean the SSD before trying to install.

I can't see the Windows Boot Manager if I am in the UEFI. It has to be the SSD, right? Why???

1 Attachment

13 Posts

April 5th, 2017 17:00

Will the reseting reset the overclocking options?

2 Intern

 • 

872 Posts

April 5th, 2017 17:00

yes.

2 Intern

 • 

872 Posts

April 5th, 2017 17:00

that's the correct option.

bottomline. your SSD should have GPT part.

13 Posts

April 5th, 2017 17:00

There is a option to "load Optimal defaults".

Yes, I have done diskpart and clean every time.

13 Posts

April 5th, 2017 17:00

Update.

I was bored so I unblugged the SSD and blugged in the cacheSSD, the M.2 one.

In the Intel Rapid Storage options I removed the RAID configuration and set it non-RAID.

I went in Legacy boot and tried installing Windows from USB to the M.2 drive. Worked. Installed. AND BOOTED.

Just like I imagined the SSD would have done.

So why does the M.2 work in Legacy, why the HDD work in Legacy in port 1, but the Samsung SSD does not work on in Legacy in port 1.

This is so stupid

2 Intern

 • 

872 Posts

April 5th, 2017 17:00

write down the OC settings if you want to reset the bios.

but more important read Tesla1856  posts again. he made alot of good suggestions.

13 Posts

April 5th, 2017 20:00

I dont understand why it gives the error in my original post.

If it can install Windows into M.2 SSD from Legacy Boot mode and SATA operation set to RAID, why can it not install Windows into normal SSD?

I think this is the biggest question.

Or can we get the SSD that has Windows installed working and booting in UEFI boot mode?

Strike me. Make me do something or get information or whatever. What do you need to know?

10 Wizard

 • 

17.9K Posts

 • 

71.3K Points

April 5th, 2017 20:00

Ok, but that pic was from before you started posting here, looking for help.

 

Two things wrong with that pic.

1. You have more than the one SSD connected. More than the one disk you want to make bootable.

2. The disk already has existing partitions created on it.

10 Wizard

 • 

17.9K Posts

 • 

71.3K Points

April 5th, 2017 20:00

Could be because it was the only disk connected (if that was the case).

Or, it could be because if a disk is connected in M.2 slot, it will take precedence over other drives and becomes Boot Priority 1. I think I remember reading a note like that on some system lately. If that doesn't work for you, remove it.

As per my above directions, it should not have been connected anyway. However, as a trouble-shooting step, its good to see something work, so good job.

13 Posts

April 6th, 2017 03:00

Oh, you are right. I took it a ehile back when it first occured and I was starting to try different things.

But the error remains the same if only the SSD is blugged in. It remains the same even if I 'diskpart', 'select disk', 'clean', 'convert mbr' in cmd.

No Events found!

Top