In der neuen cryptomator Version 1.5.6 (also die aktuelle) steht unter “entsperren” “Tresoroptionen”.
Unter “Laufwerksoptionen” steht ganz unten unter “Einhaengepunkt” “Pfad selbst waehlen”. Dort habe ich den Pfad eingetragen.
Fuer mich sieht das Problem nach einem Problem mit Zugriffsrechten aus.
Sehr interessant - leider habe ich diese Option bei mir nicht. Am Ende nach Z: habe ich keine Möglichkeit, einen Pfad einzugeben.
Very interesting - unfortunately I do not have this option with me. At the end after Z: I have no possibility to enter a path.
Just wanted to report that it seems the latest update (1.5.7) fixed my problems, can use the Dokany vault and it mounts/remounts with no errors now.
Unfortunately, the issue still persists for me with 1.5.7 and the updated Dokany.
Same for me!
The problem that occurred in version 1.5.6 still exists in version 1.5.7.
After opening the vault, the drive cannot be accessed a few minutes later (latest Dokany version is installed). You can avoid this problem by specifying a fixed path.
Same here. 
Updated Dokany and Cryptomator, drive letter is assigned but vault is not accessible (from minute 1 as far as I can tell).
Only solution that works for me at the moment: unlock the vault manually. A fixed path does not work for me, I need drive letters assigned to the vaults.
Nevermind, I spoke too soon. Cryptomator was working fine, just restarted my computer and now it’s back to not working again - looks like the drive times out even while I have the folder open and viewing the files - then I just get the popup ex. “c:/ not accessible”
Hi, I am having the same problem. FYI, I was messing around with trying to use Controlled Folder Access on Windows 10, but Cryptomator and Dokany complained/don’t seem to play well with it, so I disabled Controlled Folder Access, then troubles started (not sure if it is related). I am also trying to use Adobe Illustrator in the folder, again, not sure if it’s related. I also reinstalled both Cryptomator and Dokany.
Here is the full log.
I think here is what is happening just when the error runs:
17:48:34.476 [Thread-16951] TRACE o.c.frontend.dokany.ReadWriteAdapter - (3590) readFile(): Successful closed REOPENED file /Documents/Germany/Apartment Search/bewerbungen/lothar-bucher-str/WOHNUNGS-BEWERBUNGSBOGEN.pdf.
17:48:36.610 [Thread-16952] TRACE o.c.frontend.dokany.ReadWriteAdapter - zwCreateFile() is called for /Documents/Germany/Apartment Search/bewerbungen/lothar-bucher-str with the following parameters:
CreateDisposition -- OPEN_EXISTING
createOptions -- EnumIntegerSet(elements=[FILE_SYNCHRONOUS_IO_NONALERT, FILE_NON_DIRECTORY_FILE])
accessMasks -- EnumIntegerSet(elements=[SYNCHRONIZE])
fileAccessMasks -- EnumIntegerSet(elements=[])
fileAttributes -- EnumIntegerSet(elements=[]).
17:48:36.611 [Thread-16952] DEBUG o.c.frontend.dokany.ReadWriteAdapter - Ressource /Documents/Germany/Apartment Search/bewerbungen/lothar-bucher-str is a Directory and cannot be opened as a file.
17:48:36.615 [Thread-16953] TRACE o.c.frontend.dokany.ReadWriteAdapter - zwCreateFile() is called for / with the following parameters:
CreateDisposition -- OPEN_EXISTING
createOptions -- EnumIntegerSet(elements=[FILE_DIRECTORY_FILE, FILE_SYNCHRONOUS_IO_NONALERT])
accessMasks -- EnumIntegerSet(elements=[SYNCHRONIZE])
fileAccessMasks -- EnumIntegerSet(elements=[])
fileAttributes -- EnumIntegerSet(elements=[]).
17:48:36.615 [Thread-16953] TRACE o.c.frontend.dokany.ReadWriteAdapter - Try to open / as Directory.
17:48:36.616 [Thread-16953] TRACE o.c.frontend.dokany.ReadWriteAdapter - (3593) / opened successful with handle 3593.
17:48:36.616 [Thread-16954] TRACE o.c.frontend.dokany.ReadWriteAdapter - (3593) getFileInformation() is called for /.
17:48:36.616 [Thread-16954] TRACE o.c.frontend.dokany.ReadWriteAdapter - (3593) Filesize of / is 4096.
17:48:36.616 [Thread-16954] TRACE o.c.frontend.dokany.ReadWriteAdapter - (3593) File Information successful read from /.
17:48:36.617 [Thread-16957] TRACE o.c.frontend.dokany.ReadWriteAdapter - (3593) cleanup() is called for /.
17:48:36.617 [Thread-16958] TRACE o.c.frontend.dokany.ReadWriteAdapter - (3593) closeFile() is called for /.
17:48:36.651 [Thread-16959] TRACE o.c.frontend.dokany.ReadWriteAdapter - zwCreateFile() is called for /Documents/Germany/Apartment Search/bewerbungen/lothar-bucher-str with the following parameters:
CreateDisposition -- OPEN_EXISTING
createOptions -- EnumIntegerSet(elements=[])
accessMasks -- EnumIntegerSet(elements=[])
fileAccessMasks -- EnumIntegerSet(elements=[])
fileAttributes -- EnumIntegerSet(elements=[]).
Update: changing to a fixed mount point seems to fix it (even in read/write mode). I noticed in the log file that additional options and masks are now given to zwCreateFile(), e.g.
18:56:55.101 [Thread-114361] TRACE o.c.frontend.dokany.ReadWriteAdapter - Try to open / as Directory.
18:56:55.101 [Thread-114361] TRACE o.c.frontend.dokany.ReadWriteAdapter - (3494) / opened successful with handle 3494.
18:56:55.101 [Thread-114362] TRACE o.c.frontend.dokany.ReadWriteAdapter - (3494) getFileInformation() is called for /.
18:56:55.101 [Thread-114362] TRACE o.c.frontend.dokany.ReadWriteAdapter - (3494) Filesize of / is 4096.
18:56:55.101 [Thread-114362] TRACE o.c.frontend.dokany.ReadWriteAdapter - (3494) File Information successful read from /.
18:56:55.101 [Thread-114363] TRACE o.c.frontend.dokany.ReadWriteAdapter - (3494) cleanup() is called for /.
18:56:55.101 [Thread-114364] TRACE o.c.frontend.dokany.ReadWriteAdapter - (3494) closeFile() is called for /.
18:56:55.102 [Thread-114365] TRACE o.c.frontend.dokany.ReadWriteAdapter - zwCreateFile() is called for /Documents with the following parameters:
CreateDisposition -- OPEN_EXISTING
createOptions -- EnumIntegerSet(elements=[FILE_SYNCHRONOUS_IO_NONALERT])
accessMasks -- EnumIntegerSet(elements=[GENERIC_READ])
fileAccessMasks -- EnumIntegerSet(elements=[])
fileAttributes -- EnumIntegerSet(elements=[]).
If you are comfortable modifying the registry, you can get a drive letter assigned to the fixed path.
Assume you want to use drive D: and your mountpoint folder is C:\Cryptomator-D.
The following registry script will assign drive D: to the mount:
REGEDIT4
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run]
“D Drive”=“subst D: C:\Cryptomator-D”
Adjust this for your actual drive and folder.
This is what I am using until this issue is resolved. Note a system restart will be needed to assign the drive letter.
Unfortunately, it doesn’t work.
It works once but after a restart Cryptomator won’t unlock the vaults. I tried setting a timeout in the script as well, didn’t help. (I didn’t put a new string value in the registry but used a script in autostart.) I also tried the script without autostart. Same problem. Works once, then Cryptomator won’t unlock the vaults.
Even if I unmount the drive, I cannot unlock the vaults manually.
I need to change the mountpoint folders, then it will work again.
When my Windows got updated to “October 29, 2020—KB4580364 (OS Builds 19041.610 and 19042.610)”, the automatic unlocking of the vaults was working again.
When Windows got updated to “November 10, 2020—KB4586781 (OS Builds 19041.630 and 19042.630)”, it stopped working again.
I have the same problem:
Vault unlocks successfully and locks after 2-3min. automatically for unclear reasons, unclean, leaving the Driveletter visible in File Explorer without the usual content information.
All Versions (Cryptomator 1.5.8 & Dokane) up to date and current Windows Patchlevel as I write (pretty fresh Install). Tries completed Uninstall, reboot and install of both Dokane & Cryptomator.
Used Windows Version: Win 10 PRO 2004. Exactly the same Setup with Version 1909 works without a problem.
This log element looks suspicious:
09:07:50.035 [App Background Thread 003] WARN o.c.frontend.dokany.MountFactory - Mounting timed out.
Several locking and unlocking events with loosing access to the Vault are logged here:
Log:
09:07:32.302 [main] INFO org.cryptomator.launcher.Cryptomator - Starting Cryptomator 1.5.8 on Windows 10 10.0 (amd64)
09:07:34.635 [JavaFX Application Thread] INFO o.c.ui.launcher.FxApplicationStarter - JavaFX Runtime started.
09:07:34.641 [JavaFX Application Thread] INFO org.cryptomator.jni.FunctionsLoader - loaded WinFunctions.dll
09:07:36.409 [JavaFX Application Thread] WARN o.c.keychain.KeychainManager - LOAD
09:07:36.411 [JavaFX Application Thread] INFO o.c.k.WindowsProtectedKeychainAccess - Unable to load existing keychain file, creating new keychain.
09:07:42.031 [App Background Thread 003] INFO com.dokany.java.DokanyDriver - Dokany version: 140
09:07:42.032 [App Background Thread 003] INFO com.dokany.java.DokanyDriver - Dokany driver version: 400
09:07:50.035 [App Background Thread 003] WARN o.c.frontend.dokany.MountFactory - Mounting timed out.
09:07:50.036 [App Background Thread 003] INFO o.c.ui.unlock.UnlockWorkflow - Unlock of ‘xxx’ succeeded.
09:07:50.123 [JavaFX Application Thread] INFO o.cryptomator.ui.common.VaultService - Revealed xxx
09:32:07.850 [App Background Thread 005] INFO com.dokany.java.DokanyDriver - Unmount and shutdown: K:
09:32:12.852 [App Background Thread 005] WARN o.cryptomator.frontend.dokany.Mount - Dokany driver will be canceled now…
09:32:12.853 [App Background Thread 005] WARN o.cryptomator.frontend.dokany.Mount - Dokany driver for drive K:: canceled.
09:32:12.857 [JavaFX Application Thread] INFO o.cryptomator.ui.common.VaultService - Locked xxx
09:32:22.167 [App Background Thread 005] INFO com.dokany.java.DokanyDriver - Dokany version: 140
09:32:22.167 [App Background Thread 005] INFO com.dokany.java.DokanyDriver - Dokany driver version: 400
09:32:30.168 [App Background Thread 005] WARN o.c.frontend.dokany.MountFactory - Mounting timed out.
09:32:30.168 [App Background Thread 005] INFO o.c.ui.unlock.UnlockWorkflow - Unlock of ‘xxx’ succeeded.
09:32:30.227 [JavaFX Application Thread] INFO o.cryptomator.ui.common.VaultService - Revealed xxx
09:35:27.663 [App Background Thread 003] INFO com.dokany.java.DokanyDriver - Unmount and shutdown: K:
09:35:32.665 [App Background Thread 003] WARN o.cryptomator.frontend.dokany.Mount - Dokany driver will be canceled now…
09:35:32.666 [App Background Thread 003] WARN o.cryptomator.frontend.dokany.Mount - Dokany driver for drive K:: canceled.
09:35:32.667 [JavaFX Application Thread] INFO o.cryptomator.ui.common.VaultService - Locked xxx
09:35:46.644 [App Background Thread 003] INFO com.dokany.java.DokanyDriver - Dokany version: 140
09:35:46.644 [App Background Thread 003] INFO com.dokany.java.DokanyDriver - Dokany driver version: 400
09:35:54.647 [App Background Thread 003] WARN o.c.frontend.dokany.MountFactory - Mounting timed out.
09:35:54.648 [App Background Thread 003] INFO o.c.ui.unlock.UnlockWorkflow - Unlock of ‘xxx’ succeeded.
09:35:54.713 [JavaFX Application Thread] INFO o.cryptomator.ui.common.VaultService - Revealed xxx
09:37:11.339 [App Background Thread 001] INFO com.dokany.java.DokanyDriver - Unmount and shutdown: K:
09:37:16.341 [App Background Thread 001] WARN o.cryptomator.frontend.dokany.Mount - Dokany driver will be canceled now…
09:37:16.341 [App Background Thread 001] WARN o.cryptomator.frontend.dokany.Mount - Dokany driver for drive K:: canceled.
09:37:16.342 [JavaFX Application Thread] INFO o.cryptomator.ui.common.VaultService - Locked xxx
Please investigate.
Thought I join in to this thread. Same problem here on all my Win 10 machines using the 2004 windows version. Vault is inaccessible after some minutes and the drive letter is still in use in the explorer.
My workaround until this is fixed is to mount the vault with another drive letter. After it happens I switch back to the letter I wanted to use in the first place and most of the time it just works after that but assigning the drive letter I want to use directly after the Windows start has a high chance of failing after a minute or so.
Thanks for checking out the issue. Other than that I really like Cryptomator. Nice work, guys. ^^
Hi,
same problem here. I never had any problems this far. But since 3 days ago, the drive is not reachable after around 2 minutes after dislocking. I deleted cryptomator and did a new clean install. There it told me, that dokany is outdated (I had a version from 01/19), so I installed the current version. Now with the newest dokany and the newest cryptomator (1.58) the problem is still the same.
Here is the log
Blockquote
19:23:48.839 [main] INFO org.cryptomator.launcher.Cryptomator - Starting Cryptomator 1.5.8 on Windows 10 10.0 (amd64)
19:23:51.419 [JavaFX Application Thread] INFO o.c.ui.launcher.FxApplicationStarter - JavaFX Runtime started.
19:23:51.428 [JavaFX Application Thread] INFO org.cryptomator.jni.FunctionsLoader - loaded WinFunctions.dll
19:23:55.326 [JavaFX Application Thread] WARN o.c.keychain.KeychainManager - LOAD
19:23:57.515 [JavaFX Application Thread] INFO o.cryptomator.ui.fxapp.UpdateChecker - Current version: 1.5.8, lastest version: 1.5.8
19:23:57.966 [App Background Thread 004] INFO com.dokany.java.DokanyDriver - Dokany version: 140
19:23:57.966 [App Background Thread 004] INFO com.dokany.java.DokanyDriver - Dokany driver version: 400
19:24:05.970 [App Background Thread 004] WARN o.c.frontend.dokany.MountFactory - Mounting timed out.
19:24:05.970 [App Background Thread 004] INFO o.c.ui.unlock.UnlockWorkflow - Unlock of ‘Tapyon-Tresor’ succeeded.
19:24:05.975 [App Background Thread 004] WARN o.c.keychain.KeychainManager -
19:24:06.116 [JavaFX Application Thread] INFO o.cryptomator.ui.common.VaultService - Revealed Tapyon-Tresor
Blockquote
for me it worked to change the drive mount from dokany to webdav. I would prefer to use dokany.
If there is a solutions meanwhile, please let me know
BR, tapy
WIN10 Build 19041.vb_release.191206-1406
Older PC
Experiencing this issue as well, immediately after mounting the drive I get a windows error that that drive X:\ is not accessible and nothing showing up in Explorer. Tried reinstalling cryptomator and dokany, restarting, the whole nine, still nothing.
If you have problems using Dokany, you can either switch to WebDAV in the general preferences or use Winfsp (WinFSP: How to use it)
Hello there,
Just frustrating as the stability and simplicity is what attracted me, and I did pay ferrit.
Series of events:
Open Cryptomator one day. Unlocks fine. No drive mounted. Cryptomator says so.
Unmount. Remount. No drive, no access. (Start freaking out a little bit)
Reinstall Cryptomator. Still no access.
Reinstall dokany. Still no access.
Switch to WebDAV
No access. Reinstall WebDAV, no access
uninstall/reinstall Dokany. No access
Uninstall all. Reinstall both, restarting each time. Still no access.
Remember Cyberduck can access cryptomator filesystem. Recover data. Recrypt in stable vera archive, reupload copy, copy local.
The latest version broke it, and then I switched to cyberduck, then switched to another secure storage method, because I can’t have this “breaking” and then wait for a fix. Is the unreleased vs supposed to let the archves work again. I can’t really keep switching back and forth. At this rate, the Dropbox Vault is sounding more and more appealing, even though it is not as secure, as I have no image previews in Cryptomator either, and can’t seem to generate them. Now free of relying on Cryptomator, kind of lost faith. No update should break primary functionality of software, which is to access my data.
Just my opinion…
TS
Instead of reinstalling stuff a million times, have you considered following any suggestions of people trying to help you?
Or at least to post information that allow someone to find out what is causing your problem?
How so? What version did break what exactly?
Instead of reinstalling stuff a million times, have you considered following any suggestions of people trying to help you?
No. That is not my aim here, if it ever was.
Or at least to post information that allow someone to find out what is causing your problem?
Also no, there is enough information here to help the next lost data soul.