java.lang.UnsatisfiedLinkError: Native library (com/sun/jna/win32-x86-64/jnidispatch.dll)

Any questions? Need some help?
Post Reply
Carlos81bcn
Posts: 1
Joined: 18 May 2020, 22:43

java.lang.UnsatisfiedLinkError: Native library (com/sun/jna/win32-x86-64/jnidispatch.dll)

Post by Carlos81bcn »

Good night,
I am a newbie with version 4.9.1 of filebot, I bought the program 1 month ago and I am already having problems with the java version.
Can you please indicate which java version is suitable?

I get the following error:

Code: Select all

filebot fn:system
java.lang.UnsatisfiedLinkError: Native library (com/sun/jna/win32-x86-64/jnidispatch.dll) not found in resource path (C:\Program Files\FileBot\jar\filebot.jar)
java.lang.UnsatisfiedLinkError: Native library (com/sun/jna/win32-x86-64/jnidispatch.dll) not found in resource path (C:\Program Files\FileBot\jar\filebot.jar)
        at com.sun.jna.Native.loadNativeDispatchLibraryFromClasspath(Native.java:1032)
        at com.sun.jna.Native.loadNativeDispatchLibrary(Native.java:988)
        at com.sun.jna.Native.<clinit>(Native.java:195)
        at com.sun.jna.platform.win32.Shell32.<clinit>(Shell32.java:45)
        at net.filebot.platform.windows.WinAppUtilities.setAppUserModelID(Unknown Source)
        at net.filebot.platform.windows.WinAppUtilities.initializeApplication(Unknown Source)
        at net.filebot.Main.startUserInterface(Unknown Source)
        at net.filebot.Main.lambda$main$1(Unknown Source)

java.nio.file.InvalidPathException: Illegal char <:> at index 2: fn:system: fn:system
Thanks very much.
Best Regards.
User avatar
rednoah
The Source
Posts: 22923
Joined: 16 Nov 2011, 08:59
Location: Taipei
Contact:

Re: Filebot 4.9.1 message error no rename files.

Post by rednoah »

:?: How did you install FileBot?


:?: What does filebot -script fn:sysinfo say?


:idea: FileBot does not require Java. If you're worried about interference, then having no Java installed is worth a try. Though in this case, something is preventing FileBot from loading libraries, could be anything, but my first thought is a rogue overzealous anti-virus program. It's safe to assume that you will not get this error on a pristine Windows 10 machine.


:idea: Please read How to Request Help.
:idea: Please read the FAQ and How to Request Help.
Post Reply