java.lang.UnsatisfiedLinkError: no jnicudnn in java.library.path

Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Samebug tips

Expert tip

When installing an APK, it automatically extracts the libraries of the right arch type and has them available for System.loadLibrary. But, if you're trying to load a non-standard library, the installer won't know your app has 32bit native code.


This is a sub-class of the LinkageError class and indicates that the JVM cannot find an appropriate native-language definition of a method declared as native. Compile a 64-bit version of your .dylib file.

Solutions on the web

via GitHub by Felix333
, 9 months ago
via GitHub by wmeddie
, 1 year ago
via GitHub by jfolt
, 1 year ago
no cuda in java.library.path
via GitHub by jfolt
, 1 year ago
no jnicuda in java.library.path
via GitHub by jjYBdx4IL
, 2 years ago
via GitHub by 8man
, 2 years ago
java.lang.UnsatisfiedLinkError: C:\Users\egonzalez\AppData\Local\Temp\javacpp112622691285046\jnicudnn.dll: Can't find dependent libraries
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.lang.ClassLoader.loadLibrary0(
at java.lang.ClassLoader.loadLibrary(
at java.lang.Runtime.load0(
at java.lang.System.load(

Users with the same issue

48 times, 4 weeks ago
Once, 1 month ago
Once, 6 months ago
Once, 1 year ago
14 times, 1 year ago

Write tip

Know the solutions? Share your knowledge to help other developers to debug faster.