Windows Boot Manager

[Skynet5]

Hi all,

I've just got my new Samsung Evo 500 SSD.

I plugged it in and had all sorts of problems with windows 8.1 installer (off a USB stick selecting UEFI option). The bios couldn't see the drive, the installer could but kept erroring when trying to setup the paritions (error 0x80070057)

In the end I've plugged my old SSD back in, put the EVO as another drive and then in windows diskpart removed all the paritions and formatted it a fresh. I tested the drive with ATTO and I'm seeing the 550MB/s r/w performance which is as I expect.

I then shutdown, unhooked my old SSD and moved my new one to the same port as the old one.

On installing windows this time all went well. I could partition and format and the installation went like a breeze.

However, in the bios I now have "Windows Boot Manager (p1:samsung evo 500)" and then "P1: Samsung evo 500". I have to ensure the Windows Boot Manager is the selected option for Windows 8.1 to boot..

Is this normal? Never seen this option before in my bios previously.

Output of bcdedit is:

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume2
path \EFI\Microsoft\Boot\bootmgfw.efi
description Windows Boot Manager
locale en-GB
inherit {globalsettings}
integrityservices Enable
default {current}
resumeobject {d813d4a9-b457-11e3-bc40-de7aae5da699}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.efi
description Windows 8.1
locale en-GB
inherit {bootloadersettings}
recoverysequence {d813d4ab-b457-11e3-bc40-de7aae5da699}
integrityservices Enable
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \Windows
resumeobject {d813d4a9-b457-11e3-bc40-de7aae5da699}
nx OptIn
bootmenupolicy Standard

 

[Skynet5]

Anyone?

 

[Orcvader]

Noticed something similiar with my laptop as well, I assume it's the way UEFI works. I guess it's just to give the OS tighter control over the BIOS or something. There's an extra partition labeled "UEFI" on the drive for me, do you have that as well as the normal 100mb boot partition?

 

[RavenLunatic]

I had a similar problem yesterday, for some reason after a rebuild and re-installation of windows 7 the UEFI just would not recognise my botable raid 0 array made with 2 480GB SSD's despite the re-installation being sucsessfull . Like you I noticed I had a Windows Boot manager option. When I selected that, windows loaded without any problems. Turns out my windows partition has been created using gpt rather then mbr format. Not something I asked anything to do but I think that is the reason for the extra option in the UEFI BIOS.

 

[Skynet5]

Noticed something similiar with my laptop as well, I assume it's the way UEFI works. I guess it's just to give the OS tighter control over the BIOS or something. There's an extra partition labeled "UEFI" on the drive for me, do you have that as well as the normal 100mb boot partition?

Can't check at the moment. But I'm pretty sure there is an EFI partition when looking in disk management in windows.

 

[Skynet5]

I had a similar problem yesterday, for some reason after a rebuild and re-installation of windows 7 the UEFI just would not recognise my botable raid 0 array made with 2 480GB SSD's despite the re-installation being sucsessfull . Like you I noticed I had a Windows Boot manager option. When I selected that, windows loaded without any problems. Turns out my windows partition has been created using gpt rather then mbr format. Not something I asked anything to do but I think that is the reason for the extra option in the UEFI BIOS.

My research had stuff related to gpt too. Don't remember options around that when I did format in windows to test the drive. Nor in the windows installer.