Msvcr100.dll Windows 10 64 Bits

0 views

Skip to first unread message

Lajuana Paling

unread,

Aug 5, 2024, 12:50:52 PM8/5/24

to hercompdispli

Cansomeone please help me? I also tried first installing Java 1.8 (64 bit) and then the SQL developer version without Java. This doesn't work either. When I select the location of the JDK home, it also sent one error message saying that it couldn't find any JVMs where I said. To add insult to injury, every time I follow this procedure, the Panda antivirus tells me that sqldeveloper is infected, deletes the file and encourages me to restart.

I was using JDK 8 and windows 64 bit version. Also I downloaded the oracle sql developer software with no jdk/jre option since I already have jdk 8 installed in my system. While double clicking the sqldeveloper.exe file, it asked me to input the path of the JDK. I gave the path and then it gave me the JVM MSVCR100.DLL error.

Copying it from Windows systemfolder to the installation folder of application should fix the problem. Also, you could add the PATH to the msvcr100.dll file based on 32/64 bit requirements. If the local file itself is deleted or corrupt by any chance, then it could be downloaded online or could also be reinstalled via Microsoft visual C++ 2010 Redistributable package. It is important to use the correct version based on the software. Use the 32bit dll file for 32bit software, and 64bit dll file for 64bit software.

Today I try to use oracle client 64 and failed connect Connection Identifier which is defined at tnsnames.ora file. I assume that try to connect Oracle 32 Bit Server using SQL Developer 64 bit. That is why I install new jdk x86 and trying to change jdk path but this error happened:

Windows 32-bit/64-bit: This archive. will work on a 32 or 64 bit Windows OS. The bit level of the JDK you install will determine if it runs as a 32 or 64 bit application. This download does not include the required Oracle Java JDK. You will need to install it if it's not already on your machine.

My fault, I pin sqldeveloper64W.exe to taskbar, why that error occured then after I move cursor and it was sqldeveloper64W.exe, I try to click sqldeveloper.exe, then I found that my setting is goes well.

For Windows Users: If anyone downloaded a non-jre version and faced issue, then later trying with the JRE version and still facing the issue, you need to delete SQLDeveloper folder inside "%AppData%\sqldeveloper". After deleting try opening sqldeveloper.exe again.

The default settings still seem to be -Xms128m -Xmx800m. I can generate a similar error by setting -Xmx to be large than the physical RAM in my (physical) PC. So with the default settings, you will have problems if you don't have 800m of memory allocated to Windows. That doesn't seem like much, but it seems to be in the recommended window based on this knowledgebase article.

While you could attempt to reduce the JVM requirements in your product.conf file that will likely lead to other issues later, if it works at all. So increase your Windows VM memory allocation, reboot, and try to launch SQL Developer again.

I tried most of the suggestions in this post to no avail, so I downloaded the one from oracle's download page (you must register) which asks for the location of the jdk folder (rather than the location of java.exe). This worked for me without any problems.

I couldn't find the file in C:\Program Files\Java\jdk1.8.0_261\jre\bin. My sqldeveloper came without jre at all so what it worked for me was copying the file from an older Oracle jre release to C:\Program Files\Java\jdk1.8.0_261\jre\bin.

I asked him to try installing BT11 (my application) on a machine that is already running BT10. If BT10 is running, I'm assuming all of the other prerequisites are in place. He'll get back to me tomorrow...

I think the 32-bit dll's I provided weren't right... I sent my customer the correct ones, but he decided to install my 64-bit software instead, no problems. So, he hasn't tested with the new drivers I sent. Hopefully I got the right dll's ... I don't have another computer I can test with. Will close this question for now (don't like having unresolved questions hanging around.)

With my PB 2019 R3 application, copying those alt100.dll, msvcp100.dll, msvcr100.dll files before running the runtime installer solved this issue. I used to copy those 3 files in c:\windows directory.

Ok, so recently I switched to Visual Studio 2010. I had a C++ application that worked perfectly in Visual Studio 2008. Once I compiled it with Visual Studio 2010 and ran it on a clean 2008 server (fully patched but otherwise clean), it failed to run with the following error.

I create a new project in Visual Studio 2010 using the project type of C++ Win32 Project and without making a single change to the default project, I built the file and tested it on my clean machine and the same issue occurred.

If you are missing MSVCR100D.dll, then that is a debug dll and is not part of the free to download Visual C++ Redistributable package. So you pretty much are stuck with copying it from your dev box. Copy it to the C:\Windows\System32 directory. You need admin privileges to do this.

This is called "side-by-side deployment" and is intended for the case where you have need for a specific version of a DLL, but do not want to force the user to install the entire package that contains the one DLL you need.

I new I needed to switch from DLLs to static linking but I believed the option to be found under the Linker node. Only after reading your article I realized the use of a run-tume linked DLL requires additional code such as calls to LoadLibrary(), GetProcAddress(), FreeLibrary().

This is a very lackluster and undeveloped feature of the game, and brings the multiplayer experience down a little.

Sony will start sending emails out to all customers shortly

with details on how to sign-up for the program. Nothing has been confirmed, and it appears that

this service, if it is indeed in development, will not be available until at least 2013.

I've to use Common Language Runtime Support '/clr' to compile my dll.

However, '/clr' and '/MT' options are incompatible so i can't change to Multi-threaded (/MT).

Do you have any solutions ?

Thank you.

But your suggestion of statical linking does not work.

In VS 2010, I selected /MT for Code Generation in 64 bit release DLL and rebuilt. Size increased (from 32K to 93K). But Dependency Walker still shows MSVCR100.DLL as used.

Currently, did not find a way to link without this DLL.

So, had to search another ways.

Force Redistributable setup - problems to detect whether already installed, a lot of GUIDs for different versions. And I have also VM which have msvcr100 without Redistributable installed.

So, my current solution in Setup - try to load msvcr100.dll. If fails, redistribute it in Program Files.

Just having to figure out where C/C++ node is in VS2010 was troublesome. I had to add a dummy cpp file (and then I deleted it) to view the node in the configuration properties (whereas my project already include cpp files...).

Yes, you either have to increase size by including the vcredist installer, or add the dlls to your own installer, or static link. They all increase size just in different ways. There is no way to avoid increased size in one way or the other.

I was able to get past the error using several methods above, static link, moving the .dll in with the package,

etc. Now I get a "The application was unable to start correctly (0xc000007b)" error.

Honestly Microsoft, just kill off the .dll nonsense already. Its a nightmare, it causes way more problems than it

was ever designed to solve, and nobody (but nobody) needs to save memory the way dlls were designed to do.

So the follow up is that installing visual studio on the target machine fixed the issue. This solution

really stinks, but it is good enough for right now. Note that both the machine used to generate the

application and the target (which is one foot away) are both running windows 7 64 bit. None of the