An application has made an attempt to load the C runtime library incorrectly

Question

0.00/5 (No votes)

See more:

Hello All,

In vc++, I am getting below error when try to run exe (Myapp.exe) on windows XP machines.

Not sure why...

Program: C:\Program Files\MyApplicationFolder\Myapp.exe
R6034
An application has made an attempt to load the C runtime library incorrectly.
Please contact the application's support team for more information.

Observation: There is a manifest file corresponding to EXE, when I rename that manifest file, I can see that Myapp.exe runs succesfully.

How does the manifest file depend with EXE and why I get above error when I do not rename.

Regards,
Joy

Posted 10-Nov-14 3:54am

joyjhonson

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

KarstenK · Answer 1 · 2014-11-10T04:53:00

In the manifest are the dlls with its versions for the app. The Microsoft-runtime searches and loads at startup the manifest. If it doesnt find that matching dll versions it complains- When you rename the manifest the loaders finds NOT that manifest, and maybe it uses the manifest in exe or defaults to something.

PS: if you had appended the manifest, I had a better understanding of your "DLL Hell" ;-)