Darn. In general, Java always throws a really meaningful exception, but according to this SO thread, it can be surpressed/hidden sometimes. We need this exception to find the root problem.
A way which can reveal it, is using the buildkit-releases of Cryptomator. What you need to is:
- Install a JDK 14 ( I suggest AdoptJDK)
- Download
buildkit-win.zipfrom our release page - Extract zip-archive
- Open the file
launcher-win.batwith a text editor and add the following line after-Xmx512m ^:
-Dprism.verbose=true ^
- Save the change and start this file with a double click