EasyBCD blocking new entries on my BIOS/MBR-GPT-system

FelixL

New Member
Hi,
I downloaded and installed EasyBCD, but it start's with message :

"EasyBCD has detected that your machine is currently booting in EFI mode. Due to limitations set by Microsoft, many of EasyBCD’s multi-booting
features cannot be used in EFI mode and have been disabled."

So adding a new Linux-entry is not possible though my system is booting by BIOS/MBR and not "EFI mode".

My laptop : real BIOS/MBR (not UEFI) booting to GPT-SSHD-disk;
normally booting with Win-Bootloader-menu to Win10 or Win7;
Linux-Mint and Lubuntu are also installed.

Q.: Why ist EasyBCD blocking functions on my BIOS/MBR-system ?

:smile: Felix
 

Terry60

Knows where his towel is.
Staff member
Do you mean you have enabled legacy BIOS ?
That's not going to change anything if the OS was installed in UEFI mode.
Does W10 have an EFI System partition visible in Disk Management (and flagged "system") ?
Does EasyBCD "view settings" show bootmgr loading Winload.exe or Winload.efi ?
 

FelixL

New Member
Hi Terry,
the system has a normal BIOS-MBR-start, no UEFI shows up anywhere.
On the GPT-SSHD-disk exists a EFI-Partition and there are stored the following entries :
/EFI/Microsoft/Boot with BOOTMGFW.EFI and BOOTMGR.EFI
and
/EFI/Boot with BOOTX64.EFI.

More Infos : BCDEdit lists :
Windows-Start-Manager
---------------------
... {bootmgr}
device partition=\Device\HarddiskVolume3
path \EFI\Microsoft\Boot\bootmgfw.efi
description Windows Boot Manager

etc.

So I guess, the MBR points to the EFI-Partition, there starting the BootMgr, but I cannot proof it exactly.

Infos from EasyBCD View settings :
Windows Boot Manager
--------------------
identifier {9dea862c-5cdd-4e70-acc1-f32b344d4795}
device partition=\Device\HarddiskVolume3
path \EFI\Microsoft\Boot\bootmgfw.efi
description Windows Boot Manager
locale de-DE
...
timeout 10

Windows Boot Loader
-------------------
identifier {e3dd3ac8-f47e-11e8-a8f4-c3efecf6eb73}
device partition=C:
path \Windows\system32\winload.efi
description Windows 7
locale de-DE
...
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
...
nx OptIn

Windows Boot Loader
-------------------
identifier {e3dd3ac4-f47e-11e8-a8f4-c3efecf6eb73}
device partition=W:
path \Windows\system32\winload.efi
description Windows 10
locale de-DE
...
displaymessageoverride Recovery
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=W:
systemroot \Windows
resumeobject {e3dd3ac3-f47e-11e8-a8f4-c3efecf6eb73}
nx OptIn
bootmenupolicy Standard

--------------------------------------------------------------
More Infos with diskpart :
Microsoft DiskPart-Version 6.1.7601
Copyright (C) 1999-2008 Microsoft Corporation.
Auf Computer: FUJITSU-FL-SSHD

DISKPART> list volume

Volume ### Bst Bezeichnung DS Typ Größe Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
Volume 0 F DVD-ROM 0 B Kein Medi
Volume 1 G DVD-ROM 0 B Kein Medi
Volume 2 W Win10 NTFS Partition 28 GB Fehlerfre
Volume 3 E E_W7PGMe NTFS Partition 20 GB Fehlerfre
Volume 4 RAW Partition 32 GB Fehlerfre
Volume 5 RAW Partition 25 GB Fehlerfre
Volume 6 P P_Pagefile NTFS Partition 36 GB Fehlerfre Auslager
Volume 7 C C_Win7 NTFS Partition 58 GB Fehlerfre Startpar
Volume 8 D D_Daten NTFS Partition 231 GB Fehlerfre
Volume 9 E_alt NTFS Partition 19 GB Fehlerfre
Volume 10 Recovery NTFS Partition 443 MB Fehlerfre Versteck
Volume 11 FAT32 Partition 100 MB Fehlerfre System
Volume 12 H VERBATIM32G FAT32 Wechselmed 28 GB Fehlerfre


Note 1 : Vols 4 + 5 are Linux-Systems.
Note 2 : I cannot see any flag "system"; where could/should the flag be ?

I hope, I could answer your questions, Terry.

Perhaps you are able too contribute more to my
Q.: Why ist EasyBCD blocking functions on my BIOS/MBR-system ?
Best greetings from Felix.

BTW : What do mean by "no requests in private messages" ?
I don't think I posted a private request ???
:sunglasses:
 

Terry60

Knows where his towel is.
Staff member
Yes, that's definitely a UEFI installation of W10.
You'll see the BCD has .efi on the boot manager and the boot loader, and you have the EFI system partition.
You don't have a "system" flag (which would exist on an MBR/BIOS PC) because the EFI System Partition makes that implicit. (Sorry, my error to suggest they'd both be there)
The info in my sig is general, not aimed at you.
That's why EasyBCD "greys" a load of function, because none of those things are permitted by MS in the efi bootmgr,
More info here
 
Top