EasyBCD keeps saying "The boot partition must be a primary partition." It is. Help? Thanks.

Here is the power console output:

C:\Program Files (x86)\NeoSmart Technologies\EasyBCD\bin>
C:\Program Files (x86)\NeoSmart Technologies\EasyBCD\bin>bootgrabber /tlist

BootGrabber utility.
Copyright NeoSmart Technologies 2009-2015 <NeoSmart Technologies>

WARN: Unable to get volume information for \\?\Volume{3fed47d7-129a-11ea-939d-80
6e6f6e6963}\
WARN: No active partition detected on disk 0.
WARN: No active partition detected on disk 1.
WARN: No active partition detected on disk 2.
WARN: No active partition detected on disk 3.
WARN: No active partition detected on disk 5.
D0,1,1,0,240057409536,4
P1,H:\,7,240053649408,93603041280,Yes,multi(0)disk(0)rdisk(4)partition(1),No,NTF
S
D1,1,0,1,480103981056,2
P1,C:\,162,480102055936,181746085888,No,multi(0)disk(0)rdisk(2)partition(1),No,N
TFS
D2,7,0,7,4000787030016,3
P1,,164,554696704,149757952,No,multi(0)disk(0)rdisk(3)partition(1),No,
P2,,40,104857600,69558272,No,multi(0)disk(0)rdisk(3)partition(2),No,
P3,,22,16777216,16777216,No,multi(0)disk(0)rdisk(3)partition(3),No,
P4,D:\,162,123241234432,74309312512,No,multi(0)disk(0)rdisk(3)partition(4),No,NT
FS
P5,E:\,162,1083101413376,529166991360,No,multi(0)disk(0)rdisk(3)partition(5),No,
NTFS
P6,F:\,162,1336772919296,242982952960,No,multi(0)disk(0)rdisk(3)partition(6),No,
NTFS
P7,G:\,162,1456991109120,1112473522176,No,multi(0)disk(0)rdisk(3)partition(7),No
,NTFS
D3,2,0,2,3000592982016,6
P1,J:\,162,2456102633472,1217113366528,No,multi(0)disk(0)rdisk(6)partition(1),No
,NTFS
P2,K:\,162,544489267200,431152459776,No,multi(0)disk(0)rdisk(6)partition(2),No,N
TFS
D4,2,2,0,1000204886016,5
P1,I:\,7,305781538816,151987814400,Yes,multi(0)disk(0)rdisk(5)partition(1),Yes,N
TFS
P2,L:\,7,694420504576,664938778624,Yes,multi(0)disk(0)rdisk(5)partition(2),No,NT
FS
D5,1,1,0,32078036992,0
P1,O:\,12,32077987840,19045597184,Yes,multi(0)disk(0)rdisk(0)partition(1),No,FAT
32
D6,1,1,0,8065646080,1
P1,P:\,11,8065515008,7586951168,Yes,multi(0)disk(0)rdisk(1)partition(1),Yes,FAT3
2

C:\Program Files (x86)\NeoSmart Technologies\EasyBCD\bin>
 
1607818647436.png
Windows Boot Manager
--------------------
identifier {9dea862c-5cdd-4e70-acc1-f32b344d4795}
device partition=\Device\HarddiskVolume2
path \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI
description Windows Boot Manager
locale es-ES
inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
default {7b837853-6f32-11e9-9089-ca9a9b7d6937}
resumeobject {7b837852-6f32-11e9-9089-ca9a9b7d6937}
displayorder {7b837853-6f32-11e9-9089-ca9a9b7d6937}
{8569f542-3cc8-11eb-ad8b-80a589a044a0}
{8569f543-3cc8-11eb-ad8b-80a589a044a0}
{8569f544-3cc8-11eb-ad8b-80a589a044a0}
{8569f545-3cc8-11eb-ad8b-80a589a044a0}
toolsdisplayorder {b2721d73-1db4-4c62-bf78-c548a880142d}
timeout 8
displaybootmenu Yes

Windows Boot Loader
-------------------
identifier {7b837853-6f32-11e9-9089-ca9a9b7d6937}
device partition=C:
path \WINDOWS\system32\winload.efi
description Windows 10 SSD (Slow disk)
locale es-ES
inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
recoverysequence {52543b5d-6f2a-11e9-b1ec-ed7919144cd5}
displaymessageoverride Recovery
recoveryenabled Yes
nointegritychecks No
testsigning Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \WINDOWS
resumeobject {7b837852-6f32-11e9-9089-ca9a9b7d6937}
nx OptIn
bootmenupolicy Standard

Windows Boot Loader
-------------------
identifier {8569f542-3cc8-11eb-ad8b-80a589a044a0}
device partition=Y:
path \Windows\system32\winload.efi
description Windows 10 SSD (Fast Disk)
locale es-ES
osdevice partition=Y:
systemroot \Windows
resumeobject {865e12e6-3cd3-11eb-a8b4-806e6f6e6963}
 
What are you trying to do ?
You are on a UEFI PC - the boot files must be in the EFI System Partition.
You can't move them somewhere else like you could in BIOS/MBR, so EasyBCD is not going to try.
The screen shot you include suggests that you're trying to use the "Create Bootable EXTERNAL Media" feature (my emphasis) onto your system drive (which is internal)
That feature is for creating bootable flashdrives and would make an unholy mess of your PC if you'd succeeded in getting it to overwrite your sysres.
 
Thank you Terry for the information. I thought I could change boot from one internal SSD drive to another internal SSD much faster.

My system actually has 5 internal disks (2 SSD + 3HDD), each one having a WIndows 10 OS, plus a SATA optical disk. I tried to boot from the faster one (Samsung) and I messed everything. So I disconnected everything but the DVD drive and the Samsung SSD and I was not able to boot again, from that disk or repair it with a windows installation disk, so I bought Easy Recovery Essentials CD and it saved me. Thanks! Once I was able to boot from the fast disk, I reconnected anything again and used EasyBCD 2.4 to create a boot menu in the Samsung disk. Apparently it is exactly the same I have in the old disc but, while 3 of the 5 systems start OK 100% of the times, the other two, half of the times end in a blue screen while starting. So I am still booting from the old disc. Do you have any hint about what may be happening?
 
The fact that you can get all of the systems up some of the time indicates that it's not a boot problem caused by an error in the BCD contents.
The boot sequence is:-

1.After pressing the power button, the PC’s firmware initiates a Power-On Self Test (POST) and loads firmware settings. This pre-boot process ends when a valid system disk is detected.
2.Firmware reads the master boot record (MBR), and then starts Bootmgr.exe. Bootmgr.exe finds and starts the Windows loader (Winload.exe) on the Windows boot partition.
3.Essential drivers required to start the Windows kernel are loaded and the kernel starts to run, loading into memory the system registry hive and additional drivers that are marked as BOOT_START.
4.The kernel passes control to the session manager process (Smss.exe) which initializes the system session, and loads and starts the devices and drivers that are not marked BOOT_START.
5.Winlogon.exe starts, the user logon screen appears, the service control manager starts services, and any Group Policy scripts are run. When the user logs in, Windows creates a session for that user.
6.Explorer.exe starts, the system creates the desktop window manager (DWM) process, which initializes the desktop and displays it.


BCD entries created or altered by EasyBCD are read and acted upon in step 2 by MS bootmgr.
If you get further than that then your BCD is OK.

Depending on exactly when a blue screen occurs should give you a clue whether you have a driver problem or possibly a user account problem.
Why that would be intermittent is impossible to say.
You need to refer to your event log and look for errors occurring at that time for a clue as to what's wrong
 
Back
Top