Page 1 of 1

After creators update filebot wont open

Posted: 17 Apr 2017, 13:41
by extrizyo
Hi,

i have the windows 10 store version of filebot.

After updating my windows with the creators update filebot won't open anymore.

If i click on the icon nothing happens , no error message, nothing ..

Any ideas how to fix this? ive already uninstalled it , rebooted pc and reinstalled the program but no succes.

Re: After creators update filebot wont open

Posted: 17 Apr 2017, 15:31
by rednoah
Please open CMD and type filebot -script fn:sysinfo and see what it says. Maybe the console output will give us some hints as to why it's not working.

Re: After creators update filebot wont open

Posted: 18 Apr 2017, 18:19
by extrizyo

Re: After creators update filebot wont open

Posted: 18 Apr 2017, 19:37
by rednoah
1.
Looks good. Now run just filebot to launch the GUI and see if the console shows any errors.


2.
Are sure that FileBot is not opening? Or is it just not opening within the visible screen bounds?
https://www.howtogeek.com/howto/windows ... ard-trick/

Re: After creators update filebot wont open

Posted: 19 Apr 2017, 01:34
by shreyas1122
hi, i have the same problem. i looked at the task manager and confirmed that the software is indeed not running.
so dragging the window on screen is not an option.

EDIT: there appears some error with the java run time env.

screenshot : http://tinypic.com/r/sm97xk/9

Re: After creators update filebot wont open

Posted: 19 Apr 2017, 02:48
by rednoah
Thanks for the crash report. Direct3D is crashing the JVM. Turning off Direct3D will probably work around the problem. Alternatively, updating your graphics drivers might be a solution as well.

Run this command and then try again:

Code: Select all

setx J2D_D3D false

Code: Select all

filebot
See FAQ for details.

Re: After creators update filebot wont open

Posted: 22 Apr 2017, 06:44
by extrizyo
after disabling Direct3D filebot starts but shutsdown after 2 secs.

I'm on the latest nvidia drivers.

Re: After creators update filebot wont open

Posted: 22 Apr 2017, 06:54
by rednoah
Are you using Rivatuner?

@see viewtopic.php?f=10&t=4980

Re: After creators update filebot wont open

Posted: 22 Apr 2017, 20:55
by Species
I was having the same problem. FileBot would not launch after creators update. After a reboot, I was notified that there was a Java update available. FileBot worked after applying the Java update.

Re: After creators update filebot wont open

Posted: 23 Apr 2017, 09:56
by rednoah
Installing, updating or uninstalling Java has no effect on the Windows Store version of FileBot because that version has it's own private JRE and does not use the one installed on the system.

Re: After creators update filebot wont open

Posted: 29 Apr 2017, 02:31
by Species
I should have mentioned, I am not running the windows store version.

Re: After creators update filebot wont open

Posted: 29 Apr 2017, 03:05
by rednoah
Please purchase FileBot from the Windows Store. It'll probably work out of the box.

Re: After creators update filebot wont open

Posted: 02 May 2018, 09:49
by jetbootz
C:\Users\darre>filebot -script fn:sysinfo
Error during startup
java.lang.ExceptionInInitializerError
at net.filebot.Main.main(Main.java:108)
Caused by: net.sf.ehcache.CacheException: java.io.IOException: Unable to acquire cache lock: C:\Users\darre\AppData\Roaming\FileBot\cache
at net.filebot.CacheManager.<init>(CacheManager.java:36)
at net.filebot.CacheManager.<clinit>(CacheManager.java:22)
... 1 more
Caused by: java.io.IOException: Unable to acquire cache lock: C:\Users\darre\AppData\Roaming\FileBot\cache
at net.filebot.CacheManager.acquireDiskStore(CacheManager.java:124)
at net.filebot.CacheManager.<init>(CacheManager.java:33)
... 2 more

Re: After creators update filebot wont open

Posted: 02 May 2018, 09:51
by jetbootz
I am able to get this using CMD
but I have no idea what it means. please help

Re: After creators update filebot wont open

Posted: 02 May 2018, 11:25
by rednoah
I've not seen this one before. Unfortunately, I can't reply in detail right now because I'm on my phone.

The error means that FileBot can't access its own files. That doesn't make sense. It might indicate a severe issue with your hard disk about to die, or Windows NTFS / filesystem abstraction layer somehow being broken or interfered with. Very strange indeed.