Search found 5 matches
- 09 Apr 2017, 21:22
- Forum: Feature Requests and Bug Reports
- Topic: Filebot fails to load on windows 10 after latest "creators" update
- Replies: 15
- Views: 9133
Re: Filebot fails to load on windows 10 after latest "creators" update
FileBot 4.7.9 (r4984) JNA Native: 5.1.0 MediaInfo: 0.7.93 7-Zip-JBinding: 9.20 Chromaprint: 1.4.2 Extended Attributes: OK Unicode Filesystem: OK Script Bundle: 2017-04-03 (r494) Groovy: 2.4.10 JRE: Java(TM) SE Runtime Environment 1.8.0_121 JVM: 64-bit Java HotSpot(TM) 64-Bit Server VM CPU/MEM: 8 ...
- 09 Apr 2017, 20:52
- Forum: Feature Requests and Bug Reports
- Topic: Filebot fails to load on windows 10 after latest "creators" update
- Replies: 15
- Views: 9133
Re: Filebot fails to load on windows 10 after latest "creators" update
I installed the standalone x64 file, not the store version.
- 09 Apr 2017, 20:30
- Forum: Feature Requests and Bug Reports
- Topic: Filebot fails to load on windows 10 after latest "creators" update
- Replies: 15
- Views: 9133
- 09 Apr 2017, 20:18
- Forum: Feature Requests and Bug Reports
- Topic: Filebot fails to load on windows 10 after latest "creators" update
- Replies: 15
- Views: 9133
Re: Filebot fails to load on windows 10 after latest "creators" update
Already tried the above stages. Doesnt work 
It worked just fine for many months prior to this specific windows update. I'm running the latest updates + latest java.
Maybe should i reinstall my nvidia drivers again?
It worked just fine for many months prior to this specific windows update. I'm running the latest updates + latest java.
Maybe should i reinstall my nvidia drivers again?
- 09 Apr 2017, 18:10
- Forum: Feature Requests and Bug Reports
- Topic: Filebot fails to load on windows 10 after latest "creators" update
- Replies: 15
- Views: 9133
Filebot fails to load on windows 10 after latest "creators" update
I've installed the creators update. Filebot doesnt even load the GUI. I managed to get the log file. I'm running the latest version and even reinstalled. # # A fatal error has been detected by the Java Runtime Environment: # # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ffc6314fd0c, pid ...