New to Rust? Grab our free Rust for Beginners eBook Get it free →
Fix Failed to Load the JNI Shared Library in Eclipse

Getting Eclipse open is the first step before you can work on a Java project. The jvm.dll error points to a problem loading the Java runtime Eclipse needs to start.
You’ll learn what jvm.dll refers to, then follow the checks and fixes for Eclipse’s selected Java runtime.
TL;DR: Fix the Eclipse jvm.dll error
Point Eclipse to a Java runtime that exists and matches its architecture. Repair the vendor’s runtime if that installation is damaged.
| Case | First fix |
|---|---|
| Stale or missing path | Set -vm to an installed javaw.exe |
| Architecture mismatch | Choose compatible Eclipse and Java builds |
| Damaged runtime files | Repair the vendor’s Java installation |
What does jvm.dll mean in Eclipse?
The JVM, or Java Virtual Machine, runs Java programs. On Windows, jvm.dll is a native library used by the Java runtime. Eclipse loads a JVM to start its Java-based workbench, so the message identifies a failure loading the runtime Eclipse selected.
The filename alone does not tell you whether the file is missing. The dialog’s full path can point to an old Java folder, while an architecture mismatch or damaged installation can cause a similar failure.
I checked the live Eclipse package selector, which offers Windows AArch64 and x86_64 downloads. Choose the build that matches the Java runtime you intend to use.
How to fix the Eclipse jvm.dll error step by step
Read the path in the error first, then point the affected Eclipse installation to a valid Java executable. The examples below show Windows paths and configuration, not changes made on this Linux host.
Step 1: Check the path in the error
Copy the full jvm.dll path shown in the dialog and inspect it before changing configuration. The Windows example below names a typical location. Replace it with the path from your own error dialog.
Test-Path 'C:\Program Files\Java\jdk-25\bin\server\jvm.dll'
Run this in PowerShell on the affected Windows computer. True means the path exists. False means the path is stale or the runtime files are absent.
A DLL copied from another machine may belong to a different release or architecture. Repair or reinstall the Java distribution that owns the missing runtime file.
Step 2: Match Java and Eclipse architecture
Check the architecture shown for the Eclipse package and the Java installer. An x86_64 Eclipse build needs a compatible x86_64 runtime, while an AArch64 build needs a compatible AArch64 runtime.
| Eclipse build | Java runtime | Result |
|---|---|---|
| x86_64 | x86_64 | Compatible architecture pair |
| AArch64 | AArch64 | Compatible architecture pair |
| x86_64 | AArch64 | Choose matching builds instead |
Windows being 64-bit does not identify the architecture of software already installed. Get Eclipse from its official package page and Java from its vendor, then check the Java release against the requirements for your Eclipse release.
Step 3: Set Eclipse’s Java executable
Put both lines before -vmargs if that option appears in the file. The second line must name the installed javaw.exe executable.
-vm
C:\Program Files\Java\jdk-25\bin\javaw.exe
Replace that path with the javaw.exe file installed on your machine. A folder path or the jvm.dll file is not the executable Eclipse expects for this setting.
Step 4: Repair or reinstall the runtime
Use the vendor installer to repair a runtime folder with missing files. Choose a build for the Eclipse architecture. Update eclipse.ini when the installation path changes.
java -version
The command reports the Java executable found through PATH. It does not reinstall files. Eclipse may still select another runtime from its own configuration.
Oracle’s Java help covers an older Java 7 or 8 installer error and recommends removing traces of that failed installation before using its offline installer. That advice applies to the installer failure described there, not every Eclipse startup error.
A standalone DLL may belong to another release or architecture, so keep runtime files with their vendor installation.
Step 5: Launch Eclipse and verify
Set the installed javaw.exe path in eclipse.ini and reopen this Eclipse installation. If the dialog returns, compare the named path with the configured executable and inspect the Java folder again.
-vm
C:\Program Files\Java\jdk-25\bin\javaw.exe
-vmargs
What if Eclipse still cannot load jvm.dll?
Use the symptom to choose the next check rather than changing Windows-wide settings. These cases separate a stale selection from an incompatible or damaged runtime.
| Case | Symptom | Fix |
|---|---|---|
| Stale path | The configured executable or DLL path does not exist | Set -vm to an installed javaw.exe path |
| Architecture mismatch | Eclipse and Java package architectures differ | Install compatible builds from official sources |
| Damaged runtime | The Java folder exists but its runtime files are absent | Repair or reinstall that vendor distribution |
| Java installer error | The message appears during Java installation, not Eclipse startup | Follow the Java vendor’s installer-specific guidance |
Eclipse’s own -vm setting selects a runtime for that launcher. Leave JAVA_HOME unchanged unless another tool’s documentation requires a system-wide variable.
After Eclipse starts, remove obsolete Java entries from eclipse.ini so later launches do not select a moved installation. For a separate Java application, CodeForGeek’s guide to debugging Java in Kubernetes covers a different runtime troubleshooting task.
The launcher error refers to the runtime Eclipse selected, rather than a Java source file in your project. A project can compile successfully in another IDE and Eclipse can still fail before its workspace opens, because the launcher must load its own Java runtime first.
Check whether the error names a path under an old JDK folder, a removed drive, or a directory that changed after an update. A valid installation can be present elsewhere while Eclipse continues to use the old location recorded in eclipse.ini.
Keep the distinction between the executable and the library in mind. The -vm option points to javaw.exe, while the startup dialog may name jvm.dll inside the selected runtime. Setting the executable lets the launcher select the matching library from that Java installation.
When the path exists but loading still fails, confirm that both installations target the same processor architecture. The operating system’s architecture does not tell you whether a particular Java package is x86_64 or AArch64, so read the architecture on each download and installer.
Do not change JAVA_HOME as the first fix. That variable can guide build tools and other applications, but the Eclipse launcher has its own -vm setting. A targeted launcher setting avoids changing how unrelated programs find Java.
After editing eclipse.ini, keep the option and executable path on separate lines. Place them before -vmargs, which marks the start of arguments passed to the virtual machine. If -vm is placed after that marker, Eclipse can treat it as a JVM argument instead of launcher configuration.
Use the exact executable path from the installed vendor package. Paths containing spaces do not need extra quotation marks in this two-line Eclipse configuration. Avoid pointing to a Java directory that belongs to a different installation than the one you repaired.
For a damaged installation, use the same vendor’s installer or package manager to repair it, then check that the executable and runtime library are both present. A fresh install to a new directory can leave the old directory in eclipse.ini, so update that path after reinstalling.
A project-specific JRE selection in Eclipse is a separate setting from the runtime needed to start the IDE. Fix startup first. Once the workbench opens, inspect the project’s installed JRE configuration only if builds or launches then report a Java version problem.
If the message appeared while installing Java rather than opening Eclipse, follow the Java vendor’s installer recovery instructions for that specific installer error. An installer failure and an Eclipse launcher failure happen at different stages, so a remedy for one should not be applied to the other without matching symptoms.
Do not place a downloaded jvm.dll in the Windows system directory. That file must match the runtime release and architecture, and a loose copy can leave the Java installation internally inconsistent. Repairing the owning JDK or runtime restores files from one supported package.
Conclusion
Use the error path to identify the selected runtime, match its architecture to Eclipse, and set the actual javaw.exe path. Repair the vendor installation when its runtime files are missing or damaged.
For package choices, see the Eclipse IDE packages and Oracle Java downloads. The Eclipse launcher documentation explains runtime selection, and CodeForGeek’s Java and JavaScript comparison distinguishes the two languages if that is the source of the confusion.
FAQ
These answers address common questions about Java and the launcher message.
What does JVM mean?
JVM means Java Virtual Machine. It runs Java programs, and on Windows Eclipse loads a Java runtime that includes jvm.dll.
How do I tell whether Eclipse is using Java?
Check the path in the startup error and the -vm setting in eclipse.ini. The configured Java executable must exist and be compatible with Eclipse.
Should I download jvm.dll by itself?
No. Repair or reinstall the Java runtime from its vendor so its files and architecture match.
Does 64-bit Windows mean I have 64-bit Java?
No. Check the architecture of the installed Eclipse and Java builds, then use compatible architectures.




