I can't run EasyBCD after running Windows Repair [SOLVED]

[Docfxit]

I had a program called EasyBCD installed and running fine before I ran Windows Repair ver. 3.9.33 in Win7. After running Windows Repair I get an error saying EasyBCD has stopped working.  I can't run the program. 
When I run EasyBCD ver. 2.3.0.207  The problem details are:
Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: EasyBCD.exe
Problem Signature 02: 2.3.0.207
Problem Signature 03: 562643e9
Problem Signature 04: System.Management
Problem Signature 05: 4.6.1087.0
Problem Signature 06: 583e5c09
Problem Signature 07: 259
Problem Signature 08: fe
Problem Signature 09: PSZQOADHX1U5ZAHBHOHGHLDGIY4QIXHX
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

I noticed in the event viewer there is an Information entry saying:
Fault bucket , type 0
Event Name: CLR20r3
Response: Not available
Cab Id: 0

Problem signature:
P1: EasyBCD.exe
P2: 2.3.0.207
P3: 562643e9
P4: System.Management
P5: 4.6.1087.0
P6: 583e5c09
P7: 259
P8: fe
P9: PSZQOADHX1U5ZAHBHOHGHLDGIY4QIXHX
P10:

Attached files:

These files may be available here:
C:\Users\Gary\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_EasyBCD.exe_7023d58a543d969b965edf1bc39ac323d94b6f53_10a8b9cd

Analysis symbol:
Rechecking for solution: 0
Report Id: ee1228f9-4bfd-11e7-be72-402cf4ec0779
Report Status: 0
In the file above it shows:
Version=1
EventType=CLR20r3
EventTime=131413644564121398
ReportType=2
Consent=1
ReportIdentifier=b06b1d73-4bf6-11e7-be72-402cf4ec0779
IntegratorReportIdentifier=b06b1d72-4bf6-11e7-be72-402cf4ec0779
Response.type=4
Sig[0].Name=Problem Signature 01
Sig[0].Value=EasyBCD.exe
Sig[1].Name=Problem Signature 02
Sig[1].Value=2.3.0.207
Sig[2].Name=Problem Signature 03
Sig[2].Value=562643e9
Sig[3].Name=Problem Signature 04
Sig[3].Value=System.Management
Sig[4].Name=Problem Signature 05
Sig[4].Value=4.6.1087.0
Sig[5].Name=Problem Signature 06
Sig[5].Value=583e5c09
Sig[6].Name=Problem Signature 07
Sig[6].Value=259
Sig[7].Name=Problem Signature 08
Sig[7].Value=fe
Sig[8].Name=Problem Signature 09
Sig[8].Value=PSZQOADHX1U5ZAHBHOHGHLDGIY4QIXHX
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.256.1
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=0a9e
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=0a9e372d3b4ad19135b953a78882e789
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=0a9e
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=0a9e372d3b4ad19135b953a78882e789
UI[2]=C:\Programs\EasyBCD\EasyBCD.exe
UI[3]=EasyBCD has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=C:\Programs\EasyBCD\EasyBCD.exe
LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\Windows\SYSTEM32\MSCOREE.DLL
LoadedModule[3]=C:\Windows\system32\KERNEL32.dll
LoadedModule[4]=C:\Windows\system32\KERNELBASE.dll
LoadedModule[5]=C:\Programs\Bitdefender\Bitdefender 2017\Active Virus Control\Avc3_00123_004\avcuf32.dll
LoadedModule[6]=C:\Windows\system32\ADVAPI32.dll
LoadedModule[7]=C:\Windows\system32\msvcrt.dll
LoadedModule[8]=C:\Windows\SYSTEM32\sechost.dll
LoadedModule[9]=C:\Windows\system32\RPCRT4.dll
LoadedModule[10]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscoreei.dll
LoadedModule[11]=C:\Windows\system32\SHLWAPI.dll
LoadedModule[12]=C:\Windows\system32\GDI32.dll
LoadedModule[13]=C:\Windows\system32\USER32.dll
LoadedModule[14]=C:\Windows\system32\LPK.dll
LoadedModule[15]=C:\Windows\system32\USP10.dll
LoadedModule[16]=C:\Windows\system32\IMM32.DLL
LoadedModule[17]=C:\Windows\system32\MSCTF.dll
LoadedModule[18]=C:\Windows\system32\VERSION.dll
LoadedModule[19]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
LoadedModule[20]=C:\Windows\system32\MSVCR120_CLR0400.dll
LoadedModule[21]=C:\Windows\system32\shell32.dll
LoadedModule[22]=C:\Windows\system32\ole32.dll
LoadedModule[23]=C:\Windows\system32\profapi.dll
LoadedModule[24]=C:\Windows\assembly\NativeImages_v4.0.30319_32\mscorlib\02795048c7ede81af33acdb56f905958\mscorlib.ni.dll
LoadedModule[25]=C:\Windows\system32\CRYPTBASE.dll
LoadedModule[26]=C:\Windows\system32\uxtheme.dll
LoadedModule[27]=C:\Programs\Unlocker\UnlockerHook.dll
LoadedModule[28]=C:\Windows\system32\urlmon.dll
LoadedModule[29]=C:\Windows\system32\api-ms-win-downlevel-ole32-l1-1-0.dll
LoadedModule[30]=C:\Windows\system32\api-ms-win-downlevel-shlwapi-l1-1-0.dll
LoadedModule[31]=C:\Windows\system32\api-ms-win-downlevel-advapi32-l1-1-0.dll
LoadedModule[32]=C:\Windows\system32\api-ms-win-downlevel-user32-l1-1-0.dll
LoadedModule[33]=C:\Windows\system32\api-ms-win-downlevel-version-l1-1-0.dll
LoadedModule[34]=C:\Windows\system32\api-ms-win-downlevel-normaliz-l1-1-0.dll
LoadedModule[35]=C:\Windows\system32\normaliz.DLL
LoadedModule[36]=C:\Windows\system32\iertutil.dll
LoadedModule[37]=C:\Windows\system32\WININET.dll
LoadedModule[38]=C:\Windows\system32\USERENV.dll
LoadedModule[39]=C:\Windows\system32\Secur32.dll
LoadedModule[40]=C:\Windows\system32\SSPICLI.DLL
LoadedModule[41]=C:\Windows\system32\api-ms-win-downlevel-advapi32-l2-1-0.dll
LoadedModule[42]=C:\Windows\system32\OLEAUT32.dll
LoadedModule[43]=C:\Windows\system32\CRYPTSP.dll
LoadedModule[44]=C:\Windows\system32\rsaenh.dll
LoadedModule[45]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\clrjit.dll
LoadedModule[46]=C:\Windows\assembly\NativeImages_v4.0.30319_32\System\e49af6abc3fb5dda64392cae6ca45db9\System.ni.dll
LoadedModule[47]=C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Drawing\c55a38896fef55fafafd1be9c8437243\System.Drawing.ni.dll
LoadedModule[48]=C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Windows.Forms\0fab00859ac0f599e69bc12e0cc2c497\System.Windows.Forms.ni.dll
LoadedModule[49]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\nlssorting.dll
LoadedModule[50]=C:\Windows\system32\RpcRtRemote.dll
LoadedModule[51]=C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Management\b20e452e941a29c33a7257c5681837aa\System.Management.ni.dll
LoadedModule[52]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.18837_none_41e855142bd5705d\comctl32.dll
LoadedModule[53]=C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Core\6ad7bdc64040bfda8aa2c21b1e4394b0\System.Core.ni.dll
LoadedModule[54]=C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Configuration\e4b51f793514a0d7324ef02828145130\System.Configuration.ni.dll
LoadedModule[55]=C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Xml\4d0104bb5509d906f129d54b070d1bd6\System.Xml.ni.dll
LoadedModule[56]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.23545_none_5c06d189a00e2c29\gdiplus.dll
LoadedModule[57]=C:\Windows\system32\WindowsCodecs.dll
LoadedModule[58]=C:\Windows\system32\dwmapi.dll
LoadedModule[59]=C:\Windows\system32\CLBCatQ.DLL
LoadedModule[60]=C:\Windows\System32\msfeeds.dll
LoadedModule[61]=C:\Windows\System32\elscore.dll
LoadedModule[62]=C:\Windows\System32\MLANG.dll
LoadedModule[63]=C:\Windows\System32\NETAPI32.dll
LoadedModule[64]=C:\Windows\System32\netutils.dll
LoadedModule[65]=C:\Windows\System32\srvcli.dll
LoadedModule[66]=C:\Windows\System32\wkscli.dll
LoadedModule[67]=C:\Windows\System32\SLC.dll
LoadedModule[68]=C:\Windows\system32\rasapi32.dll
LoadedModule[69]=C:\Windows\system32\rasman.dll
LoadedModule[70]=C:\Windows\system32\WS2_32.dll
LoadedModule[71]=C:\Windows\system32\NSI.dll
LoadedModule[72]=C:\Windows\system32\rtutils.dll
LoadedModule[73]=C:\Windows\system32\mswsock.dll
LoadedModule[74]=C:\Windows\System32\wshtcpip.dll
LoadedModule[75]=C:\Windows\System32\wship6.dll
LoadedModule[76]=C:\Windows\system32\winhttp.dll
LoadedModule[77]=C:\Windows\system32\webio.dll
LoadedModule[78]=C:\Windows\system32\credssp.dll
LoadedModule[79]=C:\Windows\system32\IPHLPAPI.DLL
LoadedModule[80]=C:\Windows\system32\WINNSI.DLL
LoadedModule[81]=C:\Windows\system32\dhcpcsvc6.DLL
LoadedModule[82]=C:\Windows\system32\dhcpcsvc.DLL
LoadedModule[83]=C:\Windows\system32\CFGMGR32.dll
LoadedModule[84]=C:\Windows\system32\SXS.DLL
LoadedModule[85]=C:\Windows\system32\DNSAPI.dll
LoadedModule[86]=C:\Windows\system32\rasadhlp.dll
LoadedModule[87]=C:\Windows\system32\wbem\wmiutils.dll
LoadedModule[88]=C:\Windows\system32\wbemcomn.dll
LoadedModule[89]=C:\Windows\System32\fwpuclnt.dll
LoadedModule[90]=C:\Windows\system32\wbem\wbemprox.dll
LoadedModule[91]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\wminet_utils.dll
LoadedModule[92]=C:\Windows\system32\psapi.dll
LoadedModule[93]=C:\Windows\system32\schannel.DLL
LoadedModule[94]=C:\Windows\system32\CRYPT32.dll
LoadedModule[95]=C:\Windows\system32\MSASN1.dll
LoadedModule[96]=C:\Windows\system32\SETUPAPI.dll
LoadedModule[97]=C:\Windows\system32\DEVOBJ.dll
LoadedModule[98]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\diasymreader.dll
LoadedModule[99]=C:\Windows\system32\ncrypt.dll
LoadedModule[100]=C:\Windows\system32\bcrypt.dll
LoadedModule[101]=C:\Windows\system32\bcryptprimitives.dll
LoadedModule[102]=C:\Windows\system32\GPAPI.dll
FriendlyEventName=Stopped working
ConsentKey=CLR20r3
AppName=EasyBCD
AppPath=C:\Programs\EasyBCD\EasyBCD.exe

I noticed in the event viewer there is an error saying:
Faulting application name: EasyBCD.exe, version: 2.3.0.207, time stamp: 0x562643e9
Faulting module name: KERNELBASE.dll, version: 6.1.7601.23392, time stamp: 0x56eb2fb9
Exception code: 0xe0434352
Fault offset: 0x0000845d
Faulting process id: 0x1350
Faulting application start time: 0x01d2e00aacbd562b
Faulting application path: C:\Programs\EasyBCD\EasyBCD.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: ee1228f9-4bfd-11e7-be72-402cf4ec0779

And another error saying:
Application: EasyBCD.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Runtime.InteropServices.COMException
at System.Management.ThreadDispatch.Start()
at System.Management.ManagementScope.Initialize()
at System.Management.ManagementEventWatcher.Initialize()
at System.Management.ManagementEventWatcher.Start()
at ..()
at NeoSmart.EasyBCD.MainUI..ctor()
at ..()

I have tried uninstalling EasyBCD and re-installing it.
I get the same error.

Do you have any idea why this might have happened?

Thanks,

Docfxit

[Boggin]

No, I don't but I would have thought a reinstall would have sorted it.

Did you reboot after the uninstall but before the reinstall ?

See if it works after reinstalling it in Safe Mode with Networking and running it in that mode as Bitdefender could have had a hand in this.

I'll wait until you get back on this to see if I need to pass this on.

Did you run the repair program in Safe Mode with Networking and why did you need to run the repair program ?

You can use Option 5 in the program to use the Registry restore option and then see if the program works - don't rely upon the Restore Point option if you also created one of those.

[Docfxit]

No, I don't but I would have thought a reinstall would have sorted it.

Did you reboot after the uninstall but before the reinstall ?

Yes

See if it works after reinstalling it in Safe Mode with Networking and running it in that mode as Bitdefender could have had a hand in this.

I have had Bitdefender off during all of this.
I have Uninstalled EasyBCD.
I have booted into Safe Mode with Networking.
I have re-installed EasyBCD.
I have updated Windows-All-In-One to ver. 34 in Normal mode.
I have run Windows-All-In-One in safe mode with Bitdefender off.
I have Uninstalled EasyBCD.
I have re-booted.
I have Re-Installed EasyBCD.
I have installed Visual BCD.
I'm having the same problem with Visual BCD.  As soon as I start it I get a window saying in needs to close.
I'm thinking something was done to .NET during the first run of Windows-All-In-One ver. 33
I have run .NET verifier on all the versions I have.  They were all successful.
I still think it has something to do with .NET.
 

I'll wait until you get back on this to see if I need to pass this on.

Did you run the repair program in Safe Mode with Networking and why did you need to run the repair program ?

Yes I did.  I also updated it to ver. 34 before running it.
I had a problem with Windows Update.

You can use Option 5 in the program to use the Registry restore option and then see if the program works - don't rely upon the Restore Point option if you also created one of those.

Thanks,

Docfxit

[Boggin]

Okay - I'll pass this one.

[jpm]

I was stumped here for a bit but researching the error code I'm 99% sure that windows firewall is blocking the programs you have listed.

If you go to start -> control panel -> security -> windows firewall you should be able to added exceptions for them there.


 

[Docfxit]

I was stumped here for a bit but researching the error code I'm 99% sure that windows firewall is blocking the programs you have listed.

If you go to start -> control panel -> security -> windows firewall you should be able to added exceptions for them there.

Thanks for the reply...

I have turned off the windows firewall.
I have Uninstalled both programs EasyBCD and Visual BCD with Total Uninstall.
I have re-booted.
I have cleaned out the temp files.
I have re-installed with run as administrator.
I have tried to run them with Run As Administrator.
Both programs stop with the option to Close the program.

Thanks,

Docfxit

[jpm]

I have a couple of other guesses - none that make sense totally to me.

The repair program itself wouldn't touch the easy BCD program. So it must be something else. Perhaps it is a user account problems - or perhaps a VB issue (as both apps are VB).

I'm assuming easybcd doesn't work in safe mode either, yes?

[Docfxit]

Neither program will work in safe mode.  I'm guessing .NET is damaged.  Even though the .NET verify says they are fine.

Thanks,

Docfxit

[jpm]

.net is a common thread. But, I'm thinking maybe the User Account Control.

If you right click on easy BCD and choose run as administrator..does it work?

[Docfxit]

No it doesn't.

Nice thought though.

Thanks,

Docfxit

[Docfxit]

I thought I would give re-installing .NET a try to fix this issue.

I downloaded and ran NetFxRepairTool.exe
I rebooted and it didn't fix the issue.
I tried to uninstall .NET 4.7 and received the error in the attachment:
That version was the only version in Programs and Features.
So I Uninstalled .NET 4.7 with Total Uninstall.
I went to control panel, Programs and Features and selected Turn Windows features on or off.
I turned off .NET 3.5.1 and re-booted.
I ran dotnetfx_cleanup_tool with .NET Framework - All Versions (Windows7) selected.
I re-booted.
I cleaned all temp folders.
I ran Windows Update.
It suggested installing.
.NET 4.6.1
.NET 4.5.2
.NET 4.7
I re-booted.
I ran windows update again.
One important update failed:
Internet Explorer 11 for Windows 7
All .NET updated installed with no errors.
I re-installed EasyBCD with Run as Administrator.
I received an error (attached) for a registry entry to point to the .NET Framework install Location.
I exported the registry link from a different Win7 install.
I removed all entries except InstallRoot from the reg file and installed it on first PC.
I Uninstalled EasyBCD with Total Uninstall.
I removed any registry entries with EasyBCD.
I re-booted.
I installed EasyBCD with run as administrator.
I'm getting the same error.  EasyBCD stopped working.

I have no idea what is causing this.

Docfxit

[Boggin]

What does it say when you click on View problem details in your last pic and does Event Viewer record anything with a time stamp for when the program failed ?

[Docfxit]

I included that information in my first post.

I have done an repair install.  That fixed the problem.

I thought Shane may have wanted to find out what caused this during the All In One repair.  He may have been to busy.  He may not have wanted to look at this issue.  Sometimes it's just a timing issue.  I couldn't wait an longer.

Thank you both for your support.

Docfxit

[Boggin]

Thanks for the update.

I'll add Solved to your thread title.