Vault unlocks and assigns drive letter, but later the drive cannot be opened

Version 1.5.6 64-Bit Win10 Using dukany to map a drive to the vault.

The app opens and I unlock the fault. It assigns a drive letter. I can open Windows Explorer and see t he drive and its contents.

I go about my business and sometime later I re-open Windows Explorer. The drive is there but is “inaccessible”. I try to access the mapped drive and get an error message.

I open the app and lock and re-unlock the vault, and it works fine.

Is there a timeout feature that causes the vault to silently lock but not tell the app that I need to re-unlock?

1 Like

No. The vault should stay mounted as long as you do not lock it or close the app.
Did you check the log file? Anything suspicious there?

Having the same problem. Thought it was because I had closed the window (even though it was still running and showing the icon on the system tray). But even if I just minimize the window, still have this same error. I have latest version already of Dokany

Same question here: did you check the logfile? Anything in there that might help to identify the cause of that behaviour?

Sorry am not sure what I should be looking exactly at but replicated error (created new dokany vault in desktop) and this is what shows up in the log:

16:24:42.521 [main] INFO  org.cryptomator.launcher.Cryptomator - Starting Cryptomator 1.5.6 on Windows 10 10.0 (amd64)
16:24:42.535 [main] DEBUG org.cryptomator.logging.DebugMode - Debug mode enabled
16:24:42.537 [main] DEBUG org.cryptomator.launcher.IpcFactory - [Client] Failed to connect.
16:24:42.616 [main] DEBUG org.cryptomator.launcher.IpcFactory - [Server] Wrote IPC port 57334 to C:\Users\...\AppData\Roaming\Cryptomator\ipcPort.bin
16:24:42.618 [main] DEBUG o.c.launcher.IpcProtocolImpl - Received launch args: 
16:24:42.619 [main] DEBUG org.cryptomator.launcher.Cryptomator - Did not find running application instance. Launching GUI...
16:24:42.734 [main] DEBUG o.c.ui.traymenu.TrayIconController - initialized tray icon
16:24:42.743 [main] DEBUG org.cryptomator.common.CommonsModule - Starting App Background Thread 001
16:24:42.744 [App Background Thread 001] DEBUG o.c.ui.launcher.FxApplicationStarter - Starting JavaFX runtime...
16:24:42.747 [main] DEBUG org.cryptomator.common.CommonsModule - Starting App Background Thread 002
16:24:42.993 [JavaFX Application Thread] INFO  o.c.ui.launcher.FxApplicationStarter - JavaFX Runtime started.
16:24:43.002 [JavaFX Application Thread] INFO  org.cryptomator.jni.FunctionsLoader - loaded WinFunctions.dll
16:24:43.096 [JavaFX Application Thread] TRACE o.cryptomator.ui.fxapp.FxApplication - FxApplication.start()
16:24:43.568 [JavaFX Application Thread] DEBUG org.cryptomator.ui.common.FontLoader - Loaded family: Font Awesome 5 Free Solid
16:24:43.628 [JavaFX Application Thread] DEBUG o.c.u.m.MainWindowTitleController - init MainWindowTitleController
16:24:43.756 [JavaFX Application Thread] DEBUG o.c.u.m.MainWindowController - init MainWindowController
16:24:44.121 [JavaFX Application Thread] DEBUG o.cryptomator.ui.fxapp.FxApplication - Showing MainWindow
16:24:48.635 [JavaFX Application Thread] DEBUG org.cryptomator.common.CommonsModule - Starting App Background Thread 003
16:24:48.636 [JavaFX Application Thread] DEBUG o.cryptomator.ui.fxapp.UpdateChecker - Checking for updates...
16:25:01.204 [JavaFX Application Thread] WARN  o.cryptomator.ui.fxapp.UpdateChecker - Error checking for updates
java.io.IOException: Unexpected HTTP response code 503
	at org.cryptomator.ui.fxapp.UpdateCheckerTask.call(UpdateCheckerTask.java:39)
	at org.cryptomator.ui.fxapp.UpdateCheckerTask.call(UpdateCheckerTask.java:20)
	at javafx.concurrent.Task$TaskCallable.call(Task.java:1425)
	at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
	at javafx.concurrent.Service.lambda$executeTask$6(Service.java:725)
	at java.base/java.security.AccessController.doPrivileged(Unknown Source)
	at javafx.concurrent.Service.lambda$executeTask$7(Service.java:724)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.base/java.lang.Thread.run(Unknown Source)
16:25:07.796 [JavaFX Application Thread] DEBUG o.c.u.a.AddVaultWelcomeController - AddVaultWelcomeController.createNewVault()
16:25:35.469 [JavaFX Application Thread] DEBUG org.cryptomator.common.CommonsModule - Starting App Background Thread 004
16:25:35.475 [App Background Thread 004] DEBUG o.c.c.common.ReseedingSecureRandom - Seeding CSPRNG with 55 bytes...
16:25:35.475 [App Background Thread 004] DEBUG o.c.c.common.ReseedingSecureRandom - Seeded CSPRNG.
16:25:35.877 [App Background Thread 004] DEBUG o.cryptomator.cryptofs.ReadonlyFlag - Vault opened for read and write.
16:25:36.193 [App Background Thread 004] TRACE o.c.cryptofs.fh.FileHeaderHolder - Generating file header for C:\Users\...\Desktop\Testing\d\WH\YPYFQZO6X5N2MAQALSVI74GBKNU4DC\OmAL1Eidhtoh6Z-YFrAnWhfZPTGD-PebB4jc.c9r
16:25:36.194 [App Background Thread 004] TRACE o.c.cryptofs.fh.OpenCryptoFile - First channel for this openFile. Initializing file size...
16:25:36.201 [App Background Thread 004] TRACE o.c.cryptofs.ch.CleartextFileChannel - org.cryptomator.cryptofs.ch.CleartextFileChannel@c7b8294 - Writing file header.
16:25:36.274 [App Background Thread 004] INFO  o.c.u.a.CreateNewVaultPasswordController - Created vault at C:\Users\...\Desktop\Testing

the only WARN message said that the update check failed.
Actually I’m unsure how the update check might cause a conflict with the accessibility of the vault, but can you please deactivate the update check for testing purposes and give feedback if this does influence the issue?

Besides that I cannot see anything in the log that shows that the vault is not accessible.

Just tried to open Cryptomator for the first time today and got the error, I think the below log is the right one and more representative of the error since it has the other WARN messages, sorry am a noob at this haha.

09:41:35.544 [main] INFO  org.cryptomator.launcher.Cryptomator - Starting Cryptomator 1.5.6 on Windows 10 10.0 (amd64)
09:41:35.553 [main] DEBUG org.cryptomator.logging.DebugMode - Debug mode enabled
09:41:35.554 [main] DEBUG org.cryptomator.launcher.IpcFactory - [Client] Failed to connect.
09:41:35.631 [main] DEBUG org.cryptomator.launcher.IpcFactory - [Server] Wrote IPC port 51491 to C:\Users\...\AppData\Roaming\Cryptomator\ipcPort.bin
09:41:35.632 [main] DEBUG o.c.launcher.IpcProtocolImpl - Received launch args: 
09:41:35.633 [main] DEBUG org.cryptomator.launcher.Cryptomator - Did not find running application instance. Launching GUI...
09:41:35.764 [main] DEBUG o.c.ui.traymenu.TrayIconController - initialized tray icon
09:41:35.771 [main] DEBUG org.cryptomator.common.CommonsModule - Starting App Background Thread 001
09:41:35.771 [App Background Thread 001] DEBUG o.c.ui.launcher.FxApplicationStarter - Starting JavaFX runtime...
09:41:35.774 [main] DEBUG org.cryptomator.common.CommonsModule - Starting App Background Thread 002
09:41:36.018 [JavaFX Application Thread] INFO  o.c.ui.launcher.FxApplicationStarter - JavaFX Runtime started.
09:41:36.041 [JavaFX Application Thread] INFO  org.cryptomator.jni.FunctionsLoader - loaded WinFunctions.dll
09:41:36.125 [JavaFX Application Thread] TRACE o.cryptomator.ui.fxapp.FxApplication - FxApplication.start()
09:41:36.572 [JavaFX Application Thread] DEBUG org.cryptomator.ui.common.FontLoader - Loaded family: Font Awesome 5 Free Solid
09:41:36.630 [JavaFX Application Thread] DEBUG o.c.u.m.MainWindowTitleController - init MainWindowTitleController
09:41:36.748 [JavaFX Application Thread] DEBUG o.c.u.m.MainWindowController - init MainWindowController
09:41:37.178 [JavaFX Application Thread] DEBUG o.cryptomator.ui.fxapp.FxApplication - Showing MainWindow
09:41:38.207 [JavaFX Application Thread] WARN  o.c.keychain.KeychainManager - LOAD
09:41:38.208 [JavaFX Application Thread] DEBUG o.c.k.WindowsProtectedKeychainAccess - Attempting to load keychain from C:\Users\...\AppData\Roaming\Cryptomator\keychain.json
09:41:39.096 [JavaFX Application Thread] DEBUG org.cryptomator.common.CommonsModule - Starting App Background Thread 003
09:41:39.096 [JavaFX Application Thread] DEBUG o.cryptomator.ui.fxapp.FxApplication - Showing UnlockWindow for Testing
09:41:39.097 [JavaFX Application Thread] DEBUG o.c.common.vaults.VaultStats - stop recording stats
09:41:39.099 [JavaFX Application Thread] DEBUG o.c.ui.launcher.AppLifecycleListener - Allow quitting without prompt: false
09:41:39.121 [App Background Thread 003] DEBUG o.cryptomator.cryptofs.ReadonlyFlag - Vault opened for read and write.
09:41:39.578 [App Background Thread 003] INFO  com.dokany.java.DokanyDriver - Dokany version: 130
09:41:39.578 [App Background Thread 003] INFO  com.dokany.java.DokanyDriver - Dokany driver version: 400
09:41:39.578 [App Background Thread 003] DEBUG o.c.frontend.dokany.MountFactory - Mounting on D:\: ...
09:41:39.579 [App Background Thread 003] DEBUG org.cryptomator.common.CommonsModule - Starting App Background Thread 004
09:41:41.235 [JavaFX Application Thread] DEBUG o.cryptomator.ui.fxapp.FxApplication - Showing Preferences
09:41:41.634 [JavaFX Application Thread] DEBUG org.cryptomator.common.CommonsModule - Starting App Background Thread 005
09:41:41.636 [JavaFX Application Thread] DEBUG o.cryptomator.ui.fxapp.UpdateChecker - Checking for updates...
09:41:42.582 [App Background Thread 003] TRACE o.cryptomator.frontend.dokany.Mount - Mounting still in progress.
09:41:43.138 [JavaFX Application Thread] INFO  o.cryptomator.ui.fxapp.UpdateChecker - Current version: 1.5.6, lastest version: 1.5.6
09:41:47.583 [App Background Thread 003] WARN  o.c.frontend.dokany.MountFactory - Mounting timed out.
09:41:47.583 [App Background Thread 003] INFO  o.c.ui.unlock.UnlockWorkflow - Unlock of 'Testing' succeeded.
09:41:47.591 [App Background Thread 003] WARN  o.c.keychain.KeychainManager - 
09:41:47.593 [App Background Thread 003] DEBUG org.cryptomator.common.CommonsModule - Starting App Background Thread 006
09:41:47.593 [JavaFX Application Thread] DEBUG o.c.common.vaults.VaultStats - start recording stats
09:41:47.642 [Thread-13] TRACE o.c.frontend.dokany.ReadWriteAdapter - zwCreateFile() is called for / with the following parameters:
	CreateDisposition -- OPEN_EXISTING
	createOptions -- EnumIntegerSet(elements=[])
	accessMasks -- EnumIntegerSet(elements=[])
	fileAccessMasks -- EnumIntegerSet(elements=[])
	fileAttributes -- EnumIntegerSet(elements=[]).

Your dokany version is outdated.
Please update your dokany installation to the latest one.


(DokanSetup_redist.exe)

If this does not solve the issue, does the mounting timeout also occur if you switch the vault volume type to WebDAV?

Thanks for the link. I installed the latest release1.4.0.1000 via DokanSetup_redist.exe and restarted my computer for good measure. Still having the mounting error though but noticed the version didn’t update in the logs?

13:33:41.994 [JavaFX Application Thread] WARN  o.c.keychain.KeychainManager - LOAD
13:33:41.994 [JavaFX Application Thread] DEBUG o.c.k.WindowsProtectedKeychainAccess - Attempting to load keychain from C:\Users\...\AppData\Roaming\Cryptomator\keychain.json
13:33:42.588 [JavaFX Application Thread] DEBUG org.cryptomator.common.CommonsModule - Starting App Background Thread 004
13:33:42.588 [JavaFX Application Thread] DEBUG o.cryptomator.ui.fxapp.FxApplication - Showing UnlockWindow for Testing
13:33:42.589 [JavaFX Application Thread] DEBUG o.c.common.vaults.VaultStats - stop recording stats
13:33:42.591 [JavaFX Application Thread] DEBUG o.c.ui.launcher.AppLifecycleListener - Allow quitting without prompt: false
13:33:42.617 [App Background Thread 004] DEBUG o.cryptomator.cryptofs.ReadonlyFlag - Vault opened for read and write.
13:33:43.066 [App Background Thread 004] INFO  com.dokany.java.DokanyDriver - Dokany version: 130
13:33:43.066 [App Background Thread 004] INFO  com.dokany.java.DokanyDriver - Dokany driver version: 400
13:33:43.067 [App Background Thread 004] DEBUG o.c.frontend.dokany.MountFactory - Mounting on D:\: ...
13:33:43.067 [App Background Thread 004] DEBUG org.cryptomator.common.CommonsModule - Starting App Background Thread 005
13:33:46.069 [App Background Thread 004] TRACE o.cryptomator.frontend.dokany.Mount - Mounting still in progress.
13:33:51.071 [App Background Thread 004] WARN  o.c.frontend.dokany.MountFactory - Mounting timed out.
13:33:51.071 [App Background Thread 004] INFO  o.c.ui.unlock.UnlockWorkflow - Unlock of 'Testing' succeeded.
13:33:51.078 [App Background Thread 004] WARN  o.c.keychain.KeychainManager - 
13:33:51.079 [App Background Thread 004] DEBUG org.cryptomator.common.CommonsModule - Starting App Background Thread 006

However after updating, it seems same problem with WebDAV has been fixed. Will observe…

In relation to my previous reply - I looked into uninstalling dokany and reinstalling it again as I suspect it did not install/update properly.

It seems I have a problem in uninstalling it completely/cleanly in that I cannot seem to delete the dokan1.sys file that it generates (referred to this thread also). I was able the dokan1.dll file though.

However unlike the last user who posted there, I already did a registry clean up, made sure I had the right permissions, tried using Unlocker/LockHunter programs (could not delete, even at restart), booted in safe mode to try and delete it there, tried deleting via CMD…I can’t delete it! I don’t know what to do.

Getting quite frustrated now as I feel like this has to do with my cryptomator problems

In general, dokan1.sys is removed from the system if you uninstall Dokany and perform a reboot. The other way is to use the troubelshooting dialogue and load an “tiny windows” from where you can change files in your normal windows:

  1. Open the troubelshoot dialogue by entering the power menu, hold the key Left Shift down and click on Restart
  2. From there click “Troubleshoot”, “Advanced Options” and finally “Command Prompt”
  3. You may have to authenticate yourself, but after a reboot and Windows command prompt opens
  4. Now you only need to delete the driver file. But you may need to try out different drive letters, because sometimes your actual windows is not mounted on C. Hence, for the letters A to Z try out the following command where [$] needs to replaced with a drive letter:
del [$]:\Windows\System32\drivers\dokan1.sys`

I advise against such clean ups, see here.


Okay, if everythings sober on the system again, there is currently only one thing I can say: You are not the only one, see e.g. Autostart working but mounting of drives fails (without an error message). According to your log files, the vault is mounted. But maybe not correctly integrated into the system. You can try to remove the the flag CURRENT_SESSION and see if this changes something, but be aware of the its implications:
Cryptomator on Windows: Accessing your vault with admin priviliges

Found a way to delete the file and reinstall Dokany before installing Cryptomator. Alas, even removing “CURRENT_SESSION” doesn’t seem to work for me. Just thought I’d give it a shot since this guy got it to work by uninstalling and reinstalling. In any case, hope a fix or workaround comes out soon.

I habe the same problem. The app opens and I unlock the fault. It assigns a drive letter. I can open Windows Explorer and see t he drive and its contents.
After 2-3 minutes the drive is there but is “inaccessible”. What is the best fix for the problem now? Update Dokany or to use WebDAV?

Not an option for me unfortunately as WebDAV does not work reliably. MS Word and Excel keep crashing when I work on a file that is stored in a vault.

Same problem here. Version 1.5.6, 64 bit, Windows 10, Dokany.

Uninstalled and reinstalled Cryptomator and Dokany several times, rebooting after each step. Deleted dokan1.dll from Windows\system32 and from Progams\Cryptomator. Also updated Dokay and made sure that correct versions showed up in the log file for Dokany (140) and Dokany driver (400). Also tried using the CURRENT_SESSION flag.

Still the same behaviour. After reboot Cryptomator starts and volume is mounted and accessible, but after 1-2 minutes it is gone. This also happens while copying or having files opened.

Now gone back to version 1.4.12. This was the last version without automount problems, at least for me. Troubles started with 1.4.15 latest, as far as I can tell.

Sorry for my english, I’m not a native speaker. It’s also my first post, so comments on what to improve are welcome.

I am having the same problem also. Vault is opened and I can assess the files as they are listed in Explorer. However, if I try to go and open another vault, Cyrptomator is hidden out of view and it will not come up so you can enter the credentials to open another vault. And since Cryptomator will not come into focus you cannot access the window to lock the opened vault.

However, I am on V1.4.15 as well waiting for the bugs to be worked out on the current version. I hesitate to upgrade but if this issue is not in the current version possibly that is where I need to go.
I run Win 10.

I experienced the same problem. Deactivate the virus software did not change anything. I updated dokan software which made things worse, the program reported about a keychain problem. I removed cryptomator and installed it again, now the keychain problem disappeared. However, the same problem: neither the assigned drive nor the webdav folder could be accessed.
No indication of a problem in the log file.
I installed a new subfolder in my documents folder and choosed that as a fixed path for cryptomator. That worked out well.
(system win 10-64 home, version 2004 (the latest))

A new subfolder within an existing encrypted folder? Or a new encrypted folder?
Thanks!

Not sure I understand your question. My encrypted folder is in a cloudstorage. I created a not encrypted subfolder in my documents section. I used the third option in cryptomator “choose your own path” (in the german version) and saved the path there. After opening the “Tresor” (not sure how it is named in the english version) the encrypted folder is mapped into this one (the files are seen decrypted). Is that what you wanted to know?

Vielen Dank für die Erläuterung. Jetzt verstehe ich, was Du gemacht hast. Ich habe bei mir nur keine dritte Option. Wo findest Du die? Beim geschlossenen Tresor kann ich als “Einhängepunkt” nur zwischen “Automatisch” und “zugewiesenen Laufwerksbuchstaben” wählen. Einen Pfad kann ich nicht angeben.

Thank you very much for the explanation. Now I understand what you’ve done. I just don’t have a third option with me. Where do you find them? When the vault is closed, the only “mount point” I can choose is between “automatic” and “assigned drive letter”. I can’t specify a path.

© 2020 Skymatic GmbH • Privacy PolicyImpressum