[FIXED] [EBCD-499] Win8 x86 CP and EasyBCD 2.2 170beta

X

xpk7

Member
Installed beta 170 and application won't execute (no UI is shown). A log from Process Monitor is attached.
 

Attachments

  • Logfile.zip
    180.9 KB · Views: 29
Hi, thanks for your bug report.

When you attempt to turn on EasyBCD, do any of these applications turn on and remain on (in the task manager), hanging in the background?
* bootgrabber.exe
* bcdedit.exe
 
[EBCD-499] EasyBCD 2.2 Beta - Build 173 installed in windows8, but it can not run!

help:?? even run as administrator, there have no reply!
 
Last edited:
[EBCD-499] Nothing happens when you try to run EasyBCD 2.2

I see several people have reported this problem where you click on the shortcut and nothing actually opens. But they never answer you (computer-guru), after you ask them a question.

No there are no processes that stay open in the background related to easybcd. I've tried builds 170, 172, and 173.

This is Win8 CP 32bit. Let me know what else you need to know.

Event Viewer errors:
Faulting application name: EasyBCD.exe, version: 2.2.0.170, time stamp: 0x4f5391a4
Faulting module name: KERNELBASE.dll, version: 6.2.8250.0, time stamp: 0x4f3f37cf
Exception code: 0xe0434352
Fault offset: 0x0004e09f
Faulting process id: 0x2c8
Faulting application start time: 0x01cd0a3a0e4fd4df
Faulting application path: C:\Program Files\NeoSmart Technologies\EasyBCD\EasyBCD.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: 4c274a02-762d-11e1-8e2d-bce9bfac6809
Faulting package full name:
Faulting package-relative application ID:

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

bootgrabber.exe tlist:
BootGrabber utility.
Copyright NeoSmart Technologies 2009-2011 <http://neosmart.net/>


WARN: Unable to get volume information for \\?\Volume{45b51904-760d-11e1-8e2c-806e6f6e6963}\
WARN: Unable to get volume information for \\?\Volume{45b51907-760d-11e1-8e2c-806e6f6e6963}\
WARN: Unable to get volume information for \\?\Volume{45b51909-760d-11e1-8e2c-806e6f6e6963}\
WARN: Unable to get volume information for \\?\Volume{45b5190a-760d-11e1-8e2c-806e6f6e6963}\
WARN: Error issuing IOCTL_DISK_GET_LENGTH_INFO on disk 3. Last error: 0x15
WARN: Error issuing IOCTL_DISK_GET_LENGTH_INFO on disk 4. Last error: 0x15
WARN: Error issuing IOCTL_DISK_GET_LENGTH_INFO on disk 5. Last error: 0x15
WARN: Error issuing IOCTL_DISK_GET_LENGTH_INFO on disk 6. Last error: 0x15
D0,3,3,0,80000000000,0
P1,,222,41094144,33474560,Yes,multi(0)disk(0)rdisk(0)partition(1),No,
P2,D:\,7,76725411840,50269982720,Yes,multi(0)disk(0)rdisk(0)partition(2),Yes,NTFS
P3,,219,3224309760,631521280,Yes,multi(0)disk(0)rdisk(0)partition(3),No,
D1,1,1,0,320072933376,1
P1,C:\,7,320070483968,125646675968,Yes,multi(0)disk(0)rdisk(1)partition(1),Yes,NTFS
D2,2,2,0,200049647616,2
P1,E:\,7,147617480704,66174853120,Yes,multi(0)disk(0)rdisk(2)partition(1),Yes,NTFS
P2,F:\,7,52428800000,39364411392,Yes,multi(0)disk(0)rdisk(2)partition(2),No,NTFS
 
Last edited:
Does this happen with build 169? 170 was the one where I introduced the .NET 4.0 hack.

And thank you for providing info!

Addendum:

And can you please provide either the BCD backup (created with EasyBCD or bcdedit /export) or the output of bcdedit.exe /enum all
 
Last edited:
You are welcome. If you see any discrepancy between this info and what I included in the first post its because I took out a tertiary HDD and switched the system partition between that one and the primary HDD because the boot drive and the system drive differed. So now the primary is now both system and boot. (Just FYI in case something doesn't add up.)

I have not tried build 169 yet. I'll edit the post when I do. Having done the above the situation hasn't changed.

EDIT: Build 169 works just fine..

Here ya go...

C:\>bcdedit.exe /enum all

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=C:
description Windows Boot Manager
locale en-us
inherit {globalsettings}
default {current}
resumeobject {7a82d5b2-7634-11e1-8e2d-bce9bfac6809}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30
custom:26000025 Yes


Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \windows\system32\winload.exe
description Windows 8 Consumer Preview
locale en-us
inherit {bootloadersettings}
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \windows
resumeobject {7a82d5b2-7634-11e1-8e2d-bce9bfac6809}
nx OptIn
bootmenupolicy Standard
detecthal Yes


Resume from Hibernate
---------------------
identifier {7a82d5b2-7634-11e1-8e2d-bce9bfac6809}
device partition=C:
path \windows\system32\winresume.exe
description Windows Resume Application
locale en-us
inherit {resumeloadersettings}
allowedinmemorysettings 0x15000075
filedevice partition=C:
filepath \hiberfil.sys
bootmenupolicy Standard
pae Yes
debugoptionenabled No


Windows Memory Tester
---------------------
identifier {memdiag}
device partition=C:
path \boot\memtest.exe
description Windows Memory Diagnostic
locale en-us
inherit {globalsettings}
badmemoryaccess Yes
allowedinmemorysettings 0x15000075


EMS Settings
------------
identifier {emssettings}
bootems No


Debugger Settings
-----------------
identifier {dbgsettings}
debugtype Serial
debugport 1
baudrate 115200


RAM Defects
-----------
identifier {badmemory}


Global Settings
---------------
identifier {globalsettings}
inherit {dbgsettings}
{emssettings}
{badmemory}


Boot Loader Settings
--------------------
identifier {bootloadersettings}
inherit {globalsettings}
{hypervisorsettings}


Hypervisor Settings
-------------------
identifier {hypervisorsettings}
hypervisordebugtype Serial
hypervisordebugport 1
hypervisorbaudrate 115200


Resume Loader Settings
----------------------
identifier {resumeloadersettings}
inherit {globalsettings}
 
Last edited:
matt, is there any chance you can repost that as an attachment txt? The spacing is all wrong due to the vBulletin software. I feed it directly into EasyBCD to mimic the behavior on your system, and it's not working because of the differences.
(you could try using [ c o d e ] blocks around it, too)

Or just zip the BCD backup and attach.

Thanks!
 
Ok I attached a zipped backup from Easybcd. Hope this works better!
 

Attachments

  • EasyBCD Backup (2012-03-25) (2).zip
    3.6 KB · Views: 4
I'm unfortunately unable to reproduce that behavior.

If you see any discrepancy between this info and what I included in the first post its because I took out a tertiary HDD and switched the system partition between that one and the primary HDD because the boot drive and the system drive differed. So now the primary is now both system and boot. (Just FYI in case something doesn't add up.)
Click to expand...

This wasn't responsible for it starting to work, right? (it's still broken with build 170-3 after this change?)
 
Same problem.
Win8 CP 32bit, Event Viewer errors:

Faulting application name: EasyBCD.exe, version: 2.2.0.173, time stamp: 0x4f5f571a
Faulting module name: KERNELBASE.dll, version: 6.2.8250.0, time stamp: 0x4f3f37cf
Exception code: 0xe0434352
Fault offset: 0x0004e09f
Faulting process id: 0xcc0
Faulting application start time: 0x01cd171b01019eb1
Faulting application path: C:\Program Files\NeoSmart Technologies\EasyBCD\EasyBCD.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: 3eb4bab5-830e-11e1-8e61-50e5493e1824
Faulting package full name:
Faulting package-relative application ID:

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

Note- installed VS 2011 beta
 
Thanks for the footnote. It's possible that's the reason as this is an issue related to which version of the framework EasyBCD uses.

I'll try to reproduce.
 
Merged all threads on this issue

I have attempted to reproduce this by installing Visual Studio 11 Beta in Windows 8 CP, but cannot. EasyBCD starts and runs fine for me (build 177).

Addendum

OK, found it. Had to install VS11 then enable .NET 3.5. It now crashes immediately on run (which is good).
 
I believe this issues has been fixed in EasyBCD 2.2 beta build 180. There were a number of issues some with Windows 8 and some with EasyBCD that were working together to cause this crash. Filed bugs on MSDN that were fixed in RC and updated EasyBCD to better handle mixed CLR2 and CLR4 .NET environments and all possible permutations thereof.
 
Back
Top