Executing vc++ program in VS pro 2017 after migration from VS2010

If you rebuild in VS 2017 you won't need

mfc100d.dll

And 'd' suffix suggest it is a "debug" version of DLL that should never be shipped with executable. So your downloading it won't do a thing.

you need to throw out the old mfc100d.dll from project. Rebuilding should do the job.

Watchout for sub project or other own dlls in your projects. Best is to check all other modules for rebuild or newer versions.

It is the old and ugly dll hell.

As mentioned, you should NOT need mfc100d.dll at all. The fact that the program uses it means you do not have your project set up correctly or you have not fully rebuilt it.

The cause of your problem is a null pointer passed into a MFC function or method. Once you are linking with the correct version of MFC, you should be able to determine the location of the crash by using the debugger. Look at the call stack when the program crashes and you should be able to determine where in your code the problem is. You should be able to see what value is null and track it back to where it came from. This is one of the fundamental uses of the debugger and one you should become familiar with because this kind of problem arises often.