bcdedit.exe hangs in detailed view

#1
Hi Mahmoud,

I am still getting a freeze when trying Detailed View with 66. Need to End Process in Task Manager to get out of it.

If I add another Real mode entry - Easybcd won't start up at all - each attempt to start results in another instance of bcdedit.exe and Easybcd in Task Manager - but no GUI.

Is there something strange about my my bcd?

View attachment EASY66.zip
 

mqudsi

Mostly Harmless
Staff member
#2
Try EasyBCD | Diagnostics | Reset BCD
 
#3
Tried that. This is what happens when I try Detailed View - just freezes there.

EASYBCD- 66-2009-10-30_190859.jpg

After ending it in Task Manager - tried the Reset bcd store:

GUI doesn't display the Drive you selected ( I selected the system partition, obviously)

EASYBCD -66-DRIVELETTER-2009-10-30_193113.jpg

It removed all the entries - except Vista.

EASYBCD-66-VISTA-ONLY-2009-10-30_193313.jpg

Did I do it wrong?

Fantastic new features in this build - when I get it working.

Love the Bios Extender ( no need for PLOP now) and the boot from ISO is an amazing idea.
 
Last edited:

mqudsi

Mostly Harmless
Staff member
#4
No, you didn't.


It actually removed ALL the entries, then re-created a Vista entry for the currently booted partition.

Add some entries.... Do they show?
 
#5
I added the entries back - looks good.

Will try it out a bit more.

May be the problem was my manual PLOP entry ?

I Notice Easy does it differently.

Addendum:

LOL. That didn't work out too well.

I added some entires - looked good in normal View - Detailed View opened without crashing ( I didn't check the entries carefully - just assumed they were ok ).

On restart - I got our old friend;

Windows failed to start , a recent hardware or software change, etc.:wtf:

How does this Boot from .iso work ? Where should the .iso be for that?
 
Last edited:

mqudsi

Mostly Harmless
Staff member
#6
I don't understand.... that message means that Windows was loaded, but improperly shut down.

Is the ISO option not working for you?
 
#7
I tried addding an entry for an .iso on another partition G: ( like you would with a .wim).

Selected to boot it using ireboot - that's when I got the above message.

I must have done that wrong - that same .iso boots fine from dvd.

Windows Legacy OS Loader
------------------------
identifier {466f5a88-0af2-4f76-9038-095b170dc21c}
device unknown
path \ntldr
description Earlier Version of Windows
custom:45000001 1
custom:47000005 301989892
6

Real-mode Boot Sector
---------------------
identifier {02e05be1-c590-11de-8596-001966657855}
device partition=C:
path \NST\AutoNeoGrub3.mbr
description DB10SER_ISO

Just realised G: is logical.
 
Last edited:

mqudsi

Mostly Harmless
Staff member
#8
I just tried it - it works fine here....

1) Can you confirm that the problem with bcdedit getting stuck is fixed?
2) Can you post the current contents of detailed mode here?
3) Does the path to the ISO contain any spaces?
 
#9
It's freezing agin - seemed to stop for a while.

Path to .iso is:

"G:\ISO'S\Paragon_DB10SER_bootcd.iso"

Can't open Easy now - will have to remove PLOP , I think, to get it to open

bcdedit output:



Code:
D:\windows\system32>bcdedit /enum /v

Windows Boot Manager
--------------------
identifier              {9dea862c-5cdd-4e70-acc1-f32b344d4795}
device                  partition=C:
description             Windows Boot Manager
locale                  en-us
inherit                 {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
default                 {9e3fa847-c586-11de-a473-001966657855}
resumeobject            {9e3fa846-c586-11de-a473-001966657855}
displayorder            {9e3fa847-c586-11de-a473-001966657855}
                        {887f1677-9c58-11de-89e5-001966657855}
                        {887f1674-9c58-11de-89e5-001966657855}
                        {458f972d-aa22-11de-8269-001966657855}
                        {458f972f-aa22-11de-8269-001966657855}
                        {4a8b3ad4-c228-11de-9001-8f37b74c90b8}
                        {29e41572-c59a-11de-9bd7-001966657855}
                        {29e41573-c59a-11de-9bd7-001966657855}
toolsdisplayorder       {b2721d73-1db4-4c62-bf78-c548a880142d}
timeout                 30

Windows Boot Loader
-------------------
identifier              {9e3fa847-c586-11de-a473-001966657855}
device                  partition=D:
path                    \windows\system32\winload.exe
description             Windows 7
locale                  en-us
inherit                 {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
osdevice                partition=D:
systemroot              \windows
resumeobject            {9e3fa846-c586-11de-a473-001966657855}
nx                      OptIn
detecthal               Yes

Windows Boot Loader
-------------------
identifier              {887f1677-9c58-11de-89e5-001966657855}
device                  partition=C:
path                    \windows\system32\winload.exe
description             Microsoft Windows Vista
locale                  en-us
inherit                 {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
osdevice                partition=C:
systemroot              \windows
resumeobject            {887f1676-9c58-11de-89e5-001966657855}
nx                      OptIn
detecthal               Yes

Windows Boot Loader
-------------------
identifier              {887f1674-9c58-11de-89e5-001966657855}
device                  ramdisk=[C:]\Recovery\Winre.wim,{ae5534e0-a924-466c-b836-758539a3ee3a}
path                    \Windows\System32\Boot\winload.exe
description             7 x64 WinPE Image
osdevice                ramdisk=[C:]\Recovery\Winre.wim,{ae5534e0-a924-466c-b836-758539a3ee3a}
systemroot              \Windows
detecthal               Yes
winpe                   Yes

Windows Boot Loader
-------------------
identifier              {458f972d-aa22-11de-8269-001966657855}
device                  ramdisk=[C:]\BOOT.WIM,{ae5534e0-a924-466c-b836-758539a3ee3a}
path                    \Windows\System32\Boot\winload.exe
description             DB10 WinPE Image
osdevice                ramdisk=[C:]\BOOT.WIM,{ae5534e0-a924-466c-b836-758539a3ee3a}
systemroot              \Windows
detecthal               Yes
winpe                   Yes

Windows Boot Loader
-------------------
identifier              {458f972f-aa22-11de-8269-001966657855}
device                  ramdisk=[G:]\BOOT.WIM,{ae5534e0-a924-466c-b836-758539a3ee3a}
path                    \Windows\System32\Boot\winload.exe
description             P2V R2 WinPE Image
osdevice                ramdisk=[G:]\BOOT.WIM,{ae5534e0-a924-466c-b836-758539a3ee3a}
systemroot              \Windows
detecthal               Yes
winpe                   Yes

Windows Boot Loader
-------------------
identifier              {4a8b3ad4-c228-11de-9001-8f37b74c90b8}
device                  partition=E:
path                    \Windows\system32\winload.exe
description             Vistax86
locale                  en-US
inherit                 {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
osdevice                partition=E:
systemroot              \Windows
resumeobject            {4a8b3ad5-c228-11de-9001-8f37b74c90b8}
nx                      OptIn
custom:42000002         \system32\winload.exe
custom:45000001         2
custom:47000005         301989892
                        3

Real-mode Boot Sector
---------------------
identifier              {29e41572-c59a-11de-9bd7-001966657855}
device                  partition=C:
path                    \NST\AutoNeoGrub4.mbr
description             EasyBCD BIOS Extender

Real-mode Boot Sector
---------------------
identifier              {29e41573-c59a-11de-9bd7-001966657855}
device                  partition=C:
path                    \NST\AutoNeoGrub5.mbr
description             DB10_SER_ISO

D:\windows\system32>
 

mqudsi

Mostly Harmless
Staff member
#12
Are you adding PLoP manually?
 
#13
No. I had done that originally. Took the entry out and removed it from the HD before trying anything with Build 66.

As soon as I add it with Easy - freeze in detailed view.

Just booted into Vista - exactly the same.


I had originally used plpgenbtldr v0.7 20090804, not the .iso.

Is there a vestige of that somewhere causing the trouble?

Doesn't seem to be a way to uninstall as such. I removed the bcd entry and removed the folder from the drive.

I guess that does it?

I am on x64 if that makes a diff. I notice bcdedit in the bin folder looks awful small - 32 bit? Does that matter?
 
Last edited:

mqudsi

Mostly Harmless
Staff member
#14
I use Windows 7 x64 as my main OS, so it's not a 64-bit issue.

I've attempted to load your store on my PC, but EasyBCD continues to work (though it did crash on the "Advanced Options" page).

TBH, your BCD registry is extremely messed-up. Lots of incomplete entries and missing identifiers..

Your main issues is with the "Windows Bootloader" for E: and because it came before the real-mode bootsector entries removing them made it seem like it fixed the problem... or at least I think that's the case but I cannot be sure because like I said, I can't reproduce it on my end.

Addendum:

OK, I think I found the issue... Bear with me and I'll send you a new build to test.
 
Last edited:

mqudsi

Mostly Harmless
Staff member
#16
Please try the attached build and see if it hangs on the detailed screen.

I realize it takes quite a bit of work to keep testing, but I really appreciate your sticking it through :smile:
 

Attachments

#17
Hi,

I am having a look at this now. On Vista SP2 x64 - no crashes.

Bit of an issue with the boot from .iso - appears to boot OK - but the progarm itself( Paragon DB10 Server - Linux boot cd ) won't load - just get past the first screen and it stays on the second screen forever.

Not an Easy issue I don't think.

I will try another location for the .iso - and another .iso and see.

Also - I get this error when trying to add .wim - I tried 2. They both added fine previously.

View attachment Easy69_Vista_AddWinPE_Error.txt


Then will try on 7 x64.

It is the least I can do - thanks to you for all the effort you put in to make Easybcd for everyone.
 
#18
Tried it on a new install of 7x64.

No crashes.

Added PM10 .iso entry ( drive G)

Code:
Windows Boot Manager
--------------------
identifier              {9dea862c-5cdd-4e70-acc1-f32b344d4795}
device                  partition=D:
description             Windows Boot Manager
locale                  en-us
inherit                 {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
default                 {d9e1c292-c5d1-11de-a9da-001966657855}
resumeobject            {d9e1c291-c5d1-11de-a9da-001966657855}
displayorder            {d9e1c292-c5d1-11de-a9da-001966657855}
                        {d9e1c293-c5d1-11de-a9da-001966657855}
                        {d9e1c294-c5d1-11de-a9da-001966657855}
                        {d9e1c295-c5d1-11de-a9da-001966657855}
                        {d9e1c298-c5d1-11de-a9da-001966657855}
                        {d9e1c299-c5d1-11de-a9da-001966657855}
toolsdisplayorder       {b2721d73-1db4-4c62-bf78-c548a880142d}
timeout                 30

Windows Boot Loader
-------------------
identifier              {d9e1c292-c5d1-11de-a9da-001966657855}
device                  partition=D:
path                    \windows\system32\winload.exe
description             Windows 7
locale                  en-us
inherit                 {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
osdevice                partition=D:
systemroot              \windows
resumeobject            {d9e1c291-c5d1-11de-a9da-001966657855}
nx                      OptIn
detecthal               Yes

Windows Boot Loader
-------------------
identifier              {d9e1c293-c5d1-11de-a9da-001966657855}
device                  partition=C:
path                    \Windows\system32\winload.exe
description             Vista x64
osdevice                partition=C:
systemroot              \Windows
resumeobject            {970871c8-c5d5-11de-996d-806e6f6e6963}

Windows Boot Loader
-------------------
identifier              {d9e1c294-c5d1-11de-a9da-001966657855}
device                  partition=E:
path                    \Windows\system32\winload.exe
description             Vista x86
osdevice                partition=E:
systemroot              \Windows
resumeobject            {4484d653-c6a3-11de-9e84-806e6f6e6963}

Real-mode Boot Sector
---------------------
identifier              {d9e1c295-c5d1-11de-a9da-001966657855}
device                  partition=D:
path                    \NST\AutoNeoGrub0.mbr
description             EasyBCD BIOS Extender

Real-mode Boot Sector
---------------------
identifier              {d9e1c298-c5d1-11de-a9da-001966657855}
device                  partition=D:
path                    \NST\AutoNeoGrub2.mbr
description             DB10_bootcd_iso

Real-mode Boot Sector
---------------------
identifier              {d9e1c299-c5d1-11de-a9da-001966657855}
device                  partition=D:
path                    \NST\AutoNeoGrub1.mbr
description             PM10_WINPE_ISO
Selecting that PM10 entry with ireboot just brings up the PLOP bootscreen - selecting HD 1 from PLOP - the windows boot menu for the bcd store on C comes up.

Selecting an .iso I added to that C bcd ( Paragon a_r WinPe .iso ) boots up and loads fine.


Still get the same unhandled exception error when trying to add a WinPe.wim on 7.

Hope it helps.
 

mqudsi

Mostly Harmless
Staff member
#19
OK, not *all* ISOs are supported and some incorrectly made or configured in a non-standard way will not boot. But most will.

I assume PM10 is Partition Magic? I don't really get how selecting an ISO entry will load PLoP.... interesting for sure.

But the hang is gone, right? That's excellent news.... Means I get to push out a new build soon :grinning:
 
#20
Yes, no hanging.:grinning:

I thought it was something to do with the the construction of the .iso's as to whether they actually load - they all boot - not all load properly. Since they boot fine - I don't think it's an Easybcd issue.

The unhandled exception when trying to add a WinPe entry is new though. It happens on both Vista and 7. Those are the same .wim's that picked up fine with previous builds.:frowning:

I get the same unhandled exception trying to add WinPE entry with a brand new clean install of 7 x64.
 
Last edited: