Autostart working but mounting of drives fails (without an error message)

Hi,

I use Cryptomator 1.5.6 (Dokany) on Windows 10, Version 1909.
“Unlock vault when starting computer” is enabled.

Cryptomator starts automatically but fails to mount the drives at least every second time.
There is no error message.
I get the windows saying “Unlocked XYZ successfully! Your fault is now accessible”.
When I click reveal vault, I get an error message in Windows Explorer.

Manually locking and unlocking the vault helps every time. I can access my data without any problems after manually locking/unlocking the vault.

This is what the end of the log files looks like after mounting the drives failed:

	CreateDisposition -- OPEN_EXISTING
	createOptions -- EnumIntegerSet(elements=[])
	accessMasks -- EnumIntegerSet(elements=[])
	fileAccessMasks -- EnumIntegerSet(elements=[])
	fileAttributes -- EnumIntegerSet(elements=[]).
09:20:32.716 [Thread-858887] TRACE o.c.frontend.dokany.ReadWriteAdapter - (190576) cleanup() is called for /Dokumente/desktop.ini.
09:20:32.716 [Thread-858889] TRACE o.c.frontend.dokany.ReadWriteAdapter - (190575) cleanup() is called for /Dokumente/desktop.ini.
09:20:32.717 [Thread-858888] TRACE o.c.frontend.dokany.ReadWriteAdapter - Try to open / as Directory.
09:20:32.719 [Thread-858888] TRACE o.c.frontend.dokany.ReadWriteAdapter - (190578) / opened successful with handle 190578.
09:20:32.790 [Thread-858890] TRACE o.c.frontend.dokany.ReadWriteAdapter - (190576) closeFile() is called for /Dokumente/desktop.ini.
09:20:32.792 [Thread-858891] TRACE o.c.frontend.dokany.ReadWriteAdapter - (190575) closeFile() is called for /Dokumente/desktop.ini.
09:20:32.862 [Thread-858892] TRACE o.c.frontend.dokany.ReadWriteAdapter - (190578) getFileInformation() is called for /.
09:20:32.863 [Thread-858892] TRACE o.c.frontend.dokany.ReadWriteAdapter - (190578) Filesize of / is 4096.
09:20:32.863 [Thread-858892] TRACE o.c.frontend.dokany.ReadWriteAdapter - (190578) File Information successful read from /.
09:20:32.865 [Thread-858893] TRACE o.c.frontend.dokany.ReadWriteAdapter - (190578) cleanup() is called for /.
09:20:32.939 [Thread-858894] TRACE o.c.frontend.dokany.ReadWriteAdapter - (190578) closeFile() is called for /.
09:20:33.966 [Thread-515] INFO  com.dokany.java.DokanyDriver - Unmount and shutdown: M:\
09:20:34.068 [Thread-9] INFO  com.dokany.java.DokanyDriver - Unmount and shutdown: E:\
09:20:34.071 [Thread-13] INFO  com.dokany.java.DokanyDriver - Unmount and shutdown: M:\
09:20:34.073 [Thread-506] INFO  com.dokany.java.DokanyDriver - Unmount and shutdown: E:\
09:20:34.095 [App Background Thread 003] TRACE o.c.frontend.dokany.ReadWriteAdapter - unmounted() is called.
09:20:34.193 [ShutdownTasks] DEBUG org.cryptomator.common.ShutdownHook - Running graceful shutdown tasks...
09:20:34.196 [App Background Thread 006] TRACE o.c.frontend.dokany.ReadWriteAdapter - unmounted() is called.
09:20:34.211 [ShutdownTasks] DEBUG o.cryptomator.frontend.dokany.Mount - Unmounting drive E:\: ...
09:20:34.211 [ShutdownTasks] INFO  com.dokany.java.DokanyDriver - Unmount and shutdown: E:\
09:20:35.250 [ShutdownTasks] DEBUG o.cryptomator.frontend.dokany.Mount - Unmounted drive E:\: successfully.
09:20:35.263 [ShutdownTasks] DEBUG o.cryptomator.frontend.dokany.Mount - Unmounting drive M:\: ...
09:20:35.264 [ShutdownTasks] INFO  com.dokany.java.DokanyDriver - Unmount and shutdown: M:\
09:20:35.264 [ShutdownTasks] DEBUG o.cryptomator.frontend.dokany.Mount - Unmounted drive M:\: successfully.

I appreciate your help. Thanks!

According to the log file, your vault opened without a problem.

Do you have admin rights on the computer where the error occurs? If yes, can you please test the following:

  1. Start your Computer with the setting, that your vaults are unlocked at startup.
  2. Check if they are inaccessible
  3. If so, open an elevated terminal, (aka one with admin rights) and try to navigate to the vault

For example, if your vault is mounted at E:\, you just need to enter E: to change the current terminal directory to the vault location.

Yes, I have admin rights.

As I said, the problem occurs very often, but not every time.

  1. Done

  2. In Windows File Explorer, both drives are inaccessible.

  3. I am not exactly sure what you want me to do here. I have opened the Windows Command Prompt both without and with admin rights. In both cases, the system wasn’t able to find the drive.

Edit: As I said, if I manuall lock and unlock the vault again, the drives are mounted without any problems every time. The problem only occurs on auto-start.

It looks like other people are reporting the same or a very similar issue:
[Vault unlocks and assigns drive letter, but later the drive cannot be opened]

© 2020 Skymatic GmbH • Privacy PolicyImpressum