Filebot Keeps Crashing after re-imaging

[LoCaLfoO]

I had Filebot setup previously and worked perfect had no issues. Had re-imaged Windows awhile back and had just gotten Filebot reinstalled however it keeps crashing with the error below.
Not sure if the issue is due to me having openJDK 25 installed and Filebot is trying to use the built-in 21.0.4 as shown in the error logs.
A fatal error has been detected by the Java Runtime Environment:

Code: Select all

#
#  EXCEPTION_ILLEGAL_INSTRUCTION (0xc000001d) at pc=0x000002292c402d78, pid=24196, tid=4464
#
# JRE version: OpenJDK Runtime Environment Temurin-21.0.4+7 (21.0.4+7) (build 21.0.4+7-LTS)
# Java VM: OpenJDK 64-Bit Server VM Temurin-21.0.4+7 (21.0.4+7-LTS, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, windows-amd64)
# Problematic frame:
# v  ~StubRoutines::jbyte_disjoint_arraycopy 0x000002292c402d78

Full error log: https://pastebin.com/ri8uVsr8

filebot -script fn:sysinfo
one thing to note below for some reason memory is showing as 8 GB but I have 32 GB see screenshot below


https://postimg.cc/LgFJ810m
---------------------------------

Console Output: Select all

FileBot 5.2.0 (r10714)
JNA Native: 7.0.0
MediaInfo: 25.07
7-Zip-JBinding: 16.02
Tools: fpcalc/1.5.0
Extended Attributes: OK
Unicode Filesystem: OK
Script Bundle: 2025-09-04 (r1016)
Groovy: 4.0.28
JRE: OpenJDK Runtime Environment 21.0.4
JVM: OpenJDK 64-Bit Server VM
CPU/MEM: 32 Core / 8 GB Max Memory / 43 MB Used Memory
OS: Windows 11 (amd64)
STORAGE: NTFS [(C:)] @ 364 GB | NTFS [New Volume] @ 527 GB | NTFS [(E:)] @ 1.3 TB | NTFS [Media] @ 8 TB
DATA: C:\Users\Gurjo\AppData\Roaming\FileBot
Package: MSI
Jan 03, 2026 10:22:00 PM net.sf.ehcache.store.disk.DiskStorageFactory <init>
WARNING: The index for data file C:\Users\Gurjo\AppData\Roaming\FileBot\cache\0\data_1.data is out of date, probably due to an unclean shutdown. Deleting index file C:\Users\Gurjo\AppData\Roaming\FileBot\cache\0\data_1.index
Activate License [PX45637042] on [Sat Jan 03 22:22:00 EST 2026]
License: FileBot License PX45637042 (Valid-Until: 2073-01-08)
Done ?(?????)?

-----

Console Output: Select all

java -version
openjdk version "25" 2025-09-16
OpenJDK Runtime Environment (build 25+36-3489)
OpenJDK 64-Bit Server VM (build 25+36-3489, mixed mode, sharing)

[rednoah]

FileBot for Windows ships with its own JRE and does not use any JRE you may or may not have installed on your system. You could try older versions of FileBot (that might ship with different versions of the JRE) to see if that makes a difference. Please try the latest beta for good measure.

8 GB Max Memory / 43 MB Used Memory means that the FileBot process is configured to a memory limit of 8 GB. That limit is notably a per-process memory limit imposed by the JRE. Much higher than what FileBot will ever actually need or use, but since you have a lot of RAM, the max memory limit is high by default as well.

EXCEPTION_ILLEGAL_INSTRUCTION is definitely an odd one though. It would suggest that there's code that doesn't run on your CPU. If the same code worked on the same hardware previously, then that would be very strange. But if you run the same code on different hardware, then that might explain this particular low-level error.

[LoCaLfoO]

FileBot for Windows ships with its own JRE and does not use any JRE you may or may not have installed on your system. You could try older versions of FileBot (that might ship with different versions of the JRE) to see if that makes a difference. Please try the latest beta for good measure.

8 GB Max Memory / 43 MB Used Memory means that the FileBot process is configured to a memory limit of 8 GB. That limit is notably a per-process memory limit imposed by the JRE. Much higher than what FileBot will ever actually need or use, but since you have a lot of RAM, the max memory limit is high by default as well.

EXCEPTION_ILLEGAL_INSTRUCTION is definitely an odd one though. It would suggest that there's code that doesn't run on your CPU. If the same code worked on the same hardware previously, then that would be very strange. But if you run the same code on different hardware, then that might explain this particular low-level error.

Thanks will try the beta but was just gonna use the docker version on my server good thing you replied easier to figure out what image to use from Docker Hub =).