I’ve been experiencing an issue for some time where the Cryptomator app closes by itself. The problem occurs as follows:
When I start Windows Explorer, it suddenly takes a very long time to load. Once it finally opens, everything looks normal — my Cryptomator drive (with its assigned drive letter) is visible. However, when I try to access the Cryptomator drive, I receive an error message saying “Drive not available.”
When I then check the system tray, I notice that the Cryptomator icon has disappeared. If I restart the Cryptomator app, the icon reappears, but I first get an error message saying that the vault is already in use . After I disconnect the drive in Windows Explorer and remount it in Cryptomator, everything works again.
This issue currently occurs on both my Windows 11 notebook and a Windows 11 virtual machine .
Is this a known issue? Version 1.17.1
taras
December 14, 2025, 9:15pm
2
Sorry you’re not getting any responses (I’ve had the same experience here)
I have this issue too since upgrading to Windows 11. Cryptomator will just… vanish. Unlike you, I can just relaunch it and it’s fine.
Sometimes it also simply won’t start on boot, too, regardless of how I try to make it launch (using the option in-app, placing a shortcut in the start menu folder, creating a task in Task Scheduler.. anything). This is on v1.18.0.
infeo
December 16, 2025, 8:45am
3
There exists an a bug ticket on the issue tracker regarding unexpected crashes in virtual/remote environments, see
opened 01:49AM - 12 Dec 24 UTC
os:windows
misc:gui
### Please agree to the following
- [X] I have searched [existing issues](htt… ps://github.com/cryptomator/cryptomator/issues?q=) for duplicates
- [X] I agree to follow this project's [Code of Conduct](https://github.com/cryptomator/cryptomator/blob/develop/.github/CODE_OF_CONDUCT.md)
### Summary
Cryptomator crashes after a few hours on Windows.
### What software is involved?
- Operating System: Windows 11
- Cryptomator: 1.14.2
### Volume Type
WinFsp
### Steps to Reproduce
1. Launch Cryptomator.
2. Unlock some vaults.
2. Wait for a few hours.
### Expected Behavior
Cryptomator remains stable.
### Actual Behavior
Cryptomator crashes after a few hours.
### Reproducibility
Always
### Relevant Log Output
```shell
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ffaad2ab3d6, pid=5912, tid=6036
#
# JRE version: OpenJDK Runtime Environment Zulu22.32+21-CRaC-CA (22.0.2+9) (build 22.0.2+9)
# Java VM: OpenJDK 64-Bit Server VM Zulu22.32+21-CRaC-CA (22.0.2+9, mixed mode, tiered, compressed oops, compressed class ptrs, g1 gc, windows-amd64)
# Problematic frame:
# C [awt.dll+0xdb3d6]
#
# No core dump will be written. Minidumps are not enabled by default on client versions of Windows
#
# If you would like to submit a bug report, please visit:
# http://www.azul.com/support/
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
--------------- S U M M A R Y ------------
Command Line: -Djpackage.app-version=1.14.2.5384 --enable-preview --enable-native-access=org.cryptomator.jfuse.win,org.cryptomator.integrations.win -Xss5m -Xmx256m -Dcryptomator.appVersion=1.14.2 -Dfile.encoding=utf-8 -Djava.net.useSystemProxies=true -Dcryptomator.logDir=@{localappdata}/Cryptomator -Dcryptomator.pluginDir=@{appdata}/Cryptomator/Plugins -Dcryptomator.settingsPath=@{appdata}/Cryptomator/settings.json;@{userhome}/AppData/Roaming/Cryptomator/settings.json -Dcryptomator.p12Path=@{appdata}/Cryptomator/key.p12;@{userhome}/AppData/Roaming/Cryptomator/key.p12 -Dcryptomator.ipcSocketPath=@{localappdata}/Cryptomator/ipc.socket -Dcryptomator.mountPointsDir=@{userhome}/Cryptomator -Dcryptomator.loopbackAlias=cryptomator-vault -Dcryptomator.showTrayIcon=true -Dcryptomator.buildNumber=msi-5384 -Dcryptomator.integrationsWin.autoStartShellLinkName=Cryptomator -Dcryptomator.integrationsWin.keychainPaths=@{appdata}/Cryptomator/keychain.json;@{userhome}/AppData/Roaming/Cryptomator/keychain.json -Djavafx.verbose= --module-path=C:\Program Files\Cryptomator\app\mods -XX:ErrorFile=@{userhome}/cryptomator_crash.log -Djpackage.app-path=C:\Program Files\Cryptomator\Cryptomator.exe -Djdk.module.main=org.cryptomator.desktop org.cryptomator.desktop/org.cryptomator.launcher.Cryptomator
Host: 13th Gen Intel(R) Core(TM) i7-13700K, 4 cores, 7G, Windows 11 , 64 bit Build 22621 (10.0.22621.3958)
Time: Wed Dec 11 18:28:41 2024 Windows 11 , 64 bit Build 22621 (10.0.22621.3958) elapsed time: 14657.101104 seconds (0d 4h 4m 17s)
--------------- T H R E A D ---------------
Current thread (0x00000276f9acb8f0): JavaThread "AWT-EventQueue-0" [_thread_in_native, id=6036, stack(0x000000c6a5600000,0x000000c6a5b00000) (5120K)]
Stack: [0x000000c6a5600000,0x000000c6a5b00000], sp=0x000000c6a5afedc0, free space=5115k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C [awt.dll+0xdb3d6] (no source info available)
C [awt.dll+0xdcc12] (no source info available)
C 0x00000276ea5bcf87 (no source info available)
The last pc belongs to native method entry point (kind = native) (printed below).
Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
j sun.awt.Win32GraphicsDevice.initNativeScale(I)V+0 java.desktop@22.0.2
j sun.awt.Win32GraphicsDevice.initScaleFactors()V+60 java.desktop@22.0.2
j sun.awt.Win32GraphicsDevice.displayChanged()V+16 java.desktop@22.0.2
j sun.awt.Win32GraphicsEnvironment.displayChanged()V+271 java.desktop@22.0.2
j sun.awt.windows.WToolkit.lambda$displayChanged$4()V+15 java.desktop@22.0.2
j sun.awt.windows.WToolkit$$Lambda+0x00000000328678b8.run()V+0 java.desktop@22.0.2
j java.awt.event.InvocationEvent.dispatch()V+47 java.desktop@22.0.2
j java.awt.EventQueue.dispatchEventImpl(Ljava/awt/AWTEvent;Ljava/lang/Object;)V+21 java.desktop@22.0.2
j java.awt.EventQueue$4.run()Ljava/lang/Void;+32 java.desktop@22.0.2
j java.awt.EventQueue$4.run()Ljava/lang/Object;+1 java.desktop@22.0.2
J 7107 c2 java.security.AccessController.doPrivileged(Ljava/security/PrivilegedAction;Ljava/security/AccessControlContext;)Ljava/lang/Object; java.base@22.0.2 (17 bytes) @ 0x00000276eae70f24 [0x00000276eae70ec0+0x0000000000000064]
j java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Ljava/security/PrivilegedAction;Ljava/security/AccessControlContext;Ljava/security/AccessControlContext;)Ljava/lang/Object;+18 java.base@22.0.2
j java.awt.EventQueue.dispatchEvent(Ljava/awt/AWTEvent;)V+46 java.desktop@22.0.2
j java.awt.EventDispatchThread.pumpOneEventForFilters(I)V+81 java.desktop@22.0.2
j java.awt.EventDispatchThread.pumpEventsForFilter(ILjava/awt/Conditional;Ljava/awt/EventFilter;)V+35 java.desktop@22.0.2
j java.awt.EventDispatchThread.pumpEventsForHierarchy(ILjava/awt/Conditional;Ljava/awt/Component;)V+11 java.desktop@22.0.2
j java.awt.EventDispatchThread.pumpEvents(ILjava/awt/Conditional;)V+4 java.desktop@22.0.2
j java.awt.EventDispatchThread.pumpEvents(Ljava/awt/Conditional;)V+3 java.desktop@22.0.2
j java.awt.EventDispatchThread.run()V+9 java.desktop@22.0.2
v ~StubRoutines::call_stub 0x00000276ea5b100d
siginfo: EXCEPTION_ACCESS_VIOLATION (0xc0000005), reading address 0x000000000000007f
```
### Anything else?
_No response_
1 Like
taras
January 1, 2026, 7:33pm
4
Ah, thanks very much - that would explain it.