Debug assertion failed

Question

1.00/5 (2 votes)

See more:

Debug assertion failed
program/c:/windows/system32/mfc140d.dll

What I have tried:

I tried to put the mfc140d.dll in the system32

Posted 29-Nov-22 16:48pm

Member 15848435

Updated 30-Nov-22 1:55am

Add a Solution

Comments

Rick York 29-Nov-22 23:30pm

Usually a debug assertion failure will also tell you where the assertion occurred. Without that knowledge there is nothing anyone can do to help you.

3 solutions

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)

merano99 · Answer 1 · 2022-11-29T20:15:00

MFC programs are usually not to be distributed in the debug version, but only as release versions. That's why you won't find a debug version of the MFC DLL on systems without a compiler. Copying the file into a system folder by hand is not a good idea. Either install the redistributable or copy the MFC DLL to the same folder as the application. For more information about redistributing MFC, see Redistributing Visual C++ Files.
https://learn.microsoft.com/de-de/cpp/windows/redistributing-the-mfc-library

OriginalGriff · Answer 2 · 2022-11-29T18:55:00

You need to run your code under the debugger, and when the assertion fails, you then look at the information that is provided: the assertion message and the call stack. The latter tells you where the problem was detected, and the "chain" of functions that was called to get to that point. Somewhere in that chain will we your code - so start with there and look at what system functions / classes / delegates you are calling and what parameters you are passing. Something is wrong, and you will probably need to put a breakpoint on the call and run it again to start looking for what.

Sorry, but we can't help you - time to start learning a new skill: debugging.

KarstenK · Answer 3 · 2022-11-30T01:55:00

The assertation is a failure of the program which is using that dll. So you need to debug your app and remove that bug.

Take a First look at the Visual Studio Debugger to better understand that tool and its features.
Find the place where the assert occurs and than figure out why it happens. Often it is an invalid handle in startup or exit code.

Debug assertion failed

3 solutions

Solution 2

Solution 1

Solution 3

Add your solution here

Preview 0