Page 1 of 1

Could not initialize class com.sun.jna.Native

Posted: 15 Jun 2021, 13:54
by yudicihuy
hello guys, newbie here. recently i started to invest a media server with plex then i found this tool for renaming my messed up collection.
i found a 5 years old thread about this error, and they suggest installing 64 bit java. i've done it but still no luck. so im here posting this.

my file path : https://pastebin.com/dl/xCqbvjF1
my system information : https://pastebin.com/dl/452xinvj
logs : https://pastebin.com/dl/qfmBcWtt
screen capture : https://snipboard.io/U9Kcqf.jpg

hope you guys can help me

Re: Could not initialize class com.sun.jna.Native

Posted: 15 Jun 2021, 15:54
by rednoah
FileBot does not require you to install Java, and does not use the Java runtime you may or may not have installed. FileBot also does not use JavaFX on Windows by default, so it's most strange that you get JavaFX related error message in your logs.


:?: Please open CMD and run filebot -script fn:sysenv and filebot -script fn:sysinfo to see if the console output can give us any clues.


:arrow: Please try the latest portable package to see if that works better for you: https://get.filebot.net/filebot/BETA/


EDIT:

Also, this is most strange:

Code: Select all

OS: Windows 11 (amd64)
Also, this indicates that some application files are missing, executables, libraries, configuration files, etc, which would also explain all the other unusual issues as well:

Code: Select all

Tools: NONE

Re: Could not initialize class com.sun.jna.Native

Posted: 16 Jun 2021, 03:47
by yudicihuy
thx for the reply,

the beta version 4.9.3 portable looks works. it says done renaming 'N' files. will check the output later this night

this the information you need:
sysenv : https://pastebin.com/dl/j3fDbjwh
sysinfo : https://pastebin.com/dl/LjrMUr4v

my system is core i3 8100T, 16gb ram and windows10. the OS itself always update with the latest version.
i dont know why is it called 64bit amd & win11

Re: Could not initialize class com.sun.jna.Native

Posted: 16 Jun 2021, 04:08
by rednoah
The GUI app and the command-line tool are giving us different sysinfo, even though it's running the same code. Most strange indeed. My educated guess is that some weird program unrelated to FileBot that is hooking itself into Windows libraries and GUI processes and then intercepts and messes with FileBot <=> Windows system calls in strange and unexpected ways. Something like intrusive 3rd party Windows theme libraries, but could be anything.