Won't start: "The application failed to initialize properly (0xc0000135)"

[GoogleCodeExporter]

Program won't start, i get a "OpenHardwareMonitor.exe - Application error" 
dialog box with "The application failed to initialize properly (0xc0000135). 
Click on OK to terminate the application."

v0.3.2. beta on Windows XP Home ed with 5.1.2600 SP3 build 2600
This is on an old HP pavilion zx5000 with a Pentium 4 (yeah, i read your 
posting about that processor at Tom's Hardware)

Extracted zip file in C:\Program Files\
files are in a OpenHardwareMonitor sub-folder

Original issue reported on code.google.com by jerome.p...@gmail.com on 18 Jun 2011 at 5:47

[GoogleCodeExporter]

This happens when there is no suitable Microsoft .NET Framework version 
installed. Can you please check which versions are available on your system? 
You can do this as described here: 
http://msdn.microsoft.com/en-us/kb/kbarticle.aspx?id=318785

I am surprised that you can have a Windows XP system without .NET Framework (or 
the wrong version). You can fix the problem by just installing .NET Framework 
2.0 or above, but I would be really interested what .NET versions are currently 
present on your system that cause the failure.

Original comment by moel.mich on 18 Jun 2011 at 7:02

• Changed title: Won't start: "The application failed to initialize properly (0xc0000135)"
• Changed state: NeedsInfo

[GoogleCodeExporter]

Thanks. I didn't locate any of those keys in the registy, so i guess that i 
don't have any .Net framework installed. This is a brand new install of XP, 
upon which i ran software updates repeatedly to catch up with the current 
stuff, until there were no more required updates, hence the SP3 level. However, 
while doing so i did decline the upgrade to IE 7 and IE 8 (i use Firefox or 
Chrome, so...), so perhaps that is how it didn't pull in the .Net stuff.

Back in the Windows updates again, i see a .Net framework 4 available in the 
optional updates (one has to go look for it there), so i am currently 
installing that. I will report back whether that solves the problem.

Original comment by jerome.p...@gmail.com on 18 Jun 2011 at 9:24

[GoogleCodeExporter]

Yes, that did it. No need even to reboot. Thanks again.

Original comment by jerome.p...@gmail.com on 18 Jun 2011 at 9:37

[GoogleCodeExporter]

Ok, thank you for checking. As far as I know we can't do anything to improve 
the error message for this case, because the Open Hardware Monitor doesn't even 
start without .NET Framework. Presenting a better error message is something 
that the operating system should do (but I guess it never will).

Original comment by moel.mich on 19 Jun 2011 at 12:46

• Changed state: WontFix

[GoogleCodeExporter]

Perhaps OHM could have a non-dot-net wrapper (Windows native code) around it 
which checks for an installed suitable dot-net framework, then spawns its 
dot-net core, else pop up an error msg? Perhaps such a wrapper has already been 
written somewhere?

Original comment by jerome.p...@gmail.com on 20 Jun 2011 at 6:15

[GoogleCodeExporter]

Issue 420 has been merged into this issue.

Original comment by moel.mich on 11 Dec 2012 at 10:06

[GoogleCodeExporter]

Issue 489 has been merged into this issue.

Original comment by moel.mich on 18 Jul 2013 at 12:47