Can't open EasyBCD interface on Windows 10

Tech

Member
I've tried the latest three beta versions and can't open EasyBCD interface (GUI) on Windows 10.
The process is running in background, but no interface jumps at all.
Is there a log that I can provide to help troubleshooting this?

Sometimes, GUI crashes.
 

Attachments

  • Screenshot-2015-08-31 09-14-50.jpg
    Screenshot-2015-08-31 09-14-50.jpg
    41.6 KB · Views: 3
  • Screenshot-2015-08-31 09-14-41.jpg
    Screenshot-2015-08-31 09-14-41.jpg
    9.9 KB · Views: 3
Hi Tech,

Can you please run an elevated command prompt window (right-click on the start menu and choose admin cmd) and type the following in:
Code:
bcdedit /export "c:\users\YOUR USER NAME\desktop\bcd"

Then go to your desktop and zip up the bcd file that appears and post it here as an attachment?
 
It looks like this might be a Windows/hardware issue, have a look at what it says:

Code:
Windows Boot Manager
--------------------
identifier              {9dea862c-5cdd-4e70-acc1-f32b344d4795}
device                  unknown
path                    \EFI\Microsoft\Boot\bootmgfw.efi
description             Windows Boot Manager
locale                  pt-BR
inherit                 {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
default                 {b02790b4-3934-11e5-9bc2-18a99bffcb39}
resumeobject            {b02790b3-3934-11e5-9bc2-18a99bffcb39}
displayorder            {b02790b4-3934-11e5-9bc2-18a99bffcb39}
                        {ab4d9158-3934-11e5-9bc2-18a99bffcb39}
toolsdisplayorder       {b2721d73-1db4-4c62-bf78-c548a880142d}
timeout                 8

Windows Boot Loader
-------------------
identifier              {b02790b4-3934-11e5-9bc2-18a99bffcb39}
device                  unknown
path                    \windows\system32\winload.efi
description             Windows 10
locale                  pt-BR
inherit                 {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
osdevice                unknown
systemroot              \windows
resumeobject            {b02790b3-3934-11e5-9bc2-18a99bffcb39}
nx                      OptIn
pae                     ForceDisable
bootmenupolicy          Standard

Windows Boot Loader
-------------------
identifier              {ab4d9158-3934-11e5-9bc2-18a99bffcb39}
A device attached to the system is not functioning.

In particular, the last line:
A device attached to the system is not functioning.

This is what you see on a machine that isn't attached to this hardware; it's possible that it hangs instead on your PC.
You can try by running this command instead:

Code:
bcdedit /enum /v
 
The saga continues...
1. Restored Windows Recovery Environment (lost after upgrading from Windows 8.1) with the fantastic command: reagentc /enable
2. Then I was able to boot Windows 10 in Advanced Recovery mode and choose Command line boot option.
3. Rebuild bcd with: bootrec /rebuildbdc
Although the command reports success, it seems to have done nothing.
Manual deleting the entries and rebuilding bdc did the same and I can't open EasyBCD after reboot.
4. Then I've used Dual-boot Repair Windows 10 for automatic repairing bcd.
5. I was finally able to start EasyBCD and work with it again. Add my two extra entries of Macrium Reflect System Recovery and WinPE.

Seems to be working again. Thanks for the support.
 
Last edited by a moderator:
I am having the exact same issue. Though, I don't, yet, currently have any additional OS's installed at the moment. I did notice that it is kicking out Application errors in the windows logs, but I cant find anything helpful on those, at least not specifically helpful. I believe it may be a .NET error, but I am not sure what package I need to uninstall/reinstall/install to resolve the issue. I have uninstalled the full 3.5 and 4.x .NET that is built into Windows 10 and I have run the .NET verification tool for every version of .NET available and they all come up a successful tests. Maybe there is something specific to BCD that I am missing. Please help me if you can. I have attached the bcd.zip here as well. Below are the Application log errors:

"
Faulting application name: EasyBCD.exe, version: 2.3.0.207, time stamp: 0x562643e9
Faulting module name: KERNELBASE.dll, version: 10.0.10240.16384, time stamp: 0x559f38c3
Exception code: 0xe0434352
Fault offset: 0x000000000002a1c8
Faulting process id: 0x3b18
Faulting application start time: 0x01d158a54e9f554e
Faulting application path: C:\Program Files (x86)\NeoSmart Technologies\EasyBCD\EasyBCD.exe
Faulting module path: C:\WINDOWS\system32\KERNELBASE.dll
Report Id: 6f072ab9-e197-4d11-a193-7fd50c1da324
Faulting package full name"

.NET Runtime Error

"
Application: EasyBCD.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.BadImageFormatException
Stack:
at NeoSmart.EasyBCD.MainUI..ctor()
at ..()
"
 

Attachments

  • bcd.zip
    6.9 KB · Views: 0
We believe that this was caused by an incorrectly uploaded copy of EasyBCD 2.3 to our file server.
Can you please try download it again and re-installing?
 
Back
Top