📎 AI Summary:
The thread discusses a Windows 7-compatible utility that fails to run on Windows 10 due to an error related to the MSVCR100.DLL file, despite the DLL being designed for Windows. The original poster questions whether a different version of MSVCR100.DLL is needed for Windows 10 and explains they set the PATH to include the local DLL, but the error persists. A respondent suggests that DLLs should be consistent across Windows versions and recommends using Process Monitor to check if the program is correctly locating and accessing the DLL, indicating that the issue might be due to the DLL not being found or loaded properly. Overall, the conversation points to a DLL visibility or compatibility issue rather than a fundamental incompatibility.
P

pstein

Extraordinary Member
Joined
Mar 20, 2010
Messages
454
Thread Author #1
I have a small utility which uses the MS C++ Redistributable library msvcr100.dll

It works successfully on Windows 7.

Now I put the program and all accompaning files (including msvcr100.dll) on an USB flash drive.

When I plugin that USB flash drive into another computer with Win10 and try to start it Win10 tells me something similar to

"MSCVR100.DLL is not design for Windows or contains errors."

It IS designed for Windows and it works on Windows 7!!!

So whats the error?

Do I have to use a different MSVCR100.DLL for Windows 10? From where do I get this?

Or does the program use another MSVCR100.dll?
I set the PATH (temporarily) to

.;<....normal PATH...>

Mind the leading dot!

So from my point of view the current local msvcr100.dll from local directory must be fetched.

Any other ideas?

Peter
 

Solution
Neemobeer
They should be the same across Windows versions. If the utility is dynamically linked to the library it will for it in the PATH variable, so the error may be misleading in that it actually can't find the library where it should be in C:\Windows\System32. Procmon Process Monitor with a filter for your utility would show you where it's looking for the DLL and whether or not it's able to find and access it.
Sort by date Sort by votes
Neemobeer

Neemobeer

Windows Forum Team
Staff member
Joined
Jul 4, 2015
Messages
8,995
#2
They should be the same across Windows versions. If the utility is dynamically linked to the library it will for it in the PATH variable, so the error may be misleading in that it actually can't find the library where it should be in C:\Windows\System32. Procmon Process Monitor with a filter for your utility would show you where it's looking for the DLL and whether or not it's able to find and access it.
 

Upvote 1 Downvote
Solution
You must log in or register to reply here.

Similar threads

WindowsForum AI
  • Article Article
Fix Missing DLL Errors Like MSVCP140.dll on Windows 11: Complete Troubleshooting Guide
Replies
0
Views
11K
WindowsForum AI
WindowsForum AI