Leon
June 26, 2021, 4:25am
1
Hi,
I set a folder as mount point, and has it mounted at startup. I have Cryptomator in my startup folder.
Sometime, I get error from Cryptomator that it fails to mount. On inspection, I noted the folder has became a link/junctions.
I noted that when Cryptomator successfully mount, it did change the folder to a junction, and reverse the process when un-mount. Perhaps this process did not get executed?
Please specify the error message or provide log file. (If you are on debug mode, remove personal information from log file before posting it)
Leon
June 27, 2021, 1:54pm
3
It just happened again… I am unable to mount. I have confirmed that the folder is now a Junction. I the deleted the Junction and re-create the folder. Still I am not able to mount with the attached error.
Cryptomator error 20210627.log (1.6 KB)
Leon
June 27, 2021, 11:19pm
4
This happened another time… I made a small modification of a Excel file, save it, exit excel, shutdown. After I reboot, I am not about to mount.
Even after I have deleted the Junction, and re-create the folder, I still cannot mount. I need to re-start Cryptomator for it to mount.
The error msg is similar to the one posted above.
infeo
June 28, 2021, 8:37am
5
Yes.
This is a known issue when the system is shutdown/ put into standby without locking your vaults:
opened 10:26AM - 16 Nov 19 UTC
closed 03:13PM - 02 Mar 23 UTC
type:upstream-bug
os:windows
state:has-workaround
mount:dokany
I'm running into an issue when re-opening a vault that I had opened before witho… ut properly terminating Cryptomator before windows shutdown.
When I properly shut down Cryptomator before a reboot/shutdown of windows, everything works just fine but I still get a dialog box with the message: "Tresor in Gebrauch" (vault in use) although nothing is accessing the folder at that point in time (windows is finicky/strange when it comes to open files imo). Choosing to retry the operation works just fine however.
Also when I delete and re-create the folder I can unlock the vault just fine.
I gathered the following log files:
- initial unlock into a fresh new folder with a clean shut down: [cryptomator3.log](https://github.com/cryptomator/cryptomator/files/3854063/cryptomator3.log)
- next boot: unlocking works just fine, shutting down windows without shutting down cryptomator: [cryptomator2.log](https://github.com/cryptomator/cryptomator/files/3854064/cryptomator2.log)
- next windows session - unlocking fails:
[cryptomator1.log](https://github.com/cryptomator/cryptomator/files/3854065/cryptomator1.log)
- stopping cryptomator, restarting it and I still get the same issue (trying twice). Then I delete the folder and create it anew and unlocking works: [cryptomator0.log](https://github.com/cryptomator/cryptomator/files/3854067/cryptomator0.log)
I hope this helps - if not I'm happy to gather additional debug information if needed.
### System Setup
* Operating system and version: Windows 10
* Cryptomator version: 1.4.15
* Drive: Dokany
### Steps to Reproduce
1. Unlock a vault to a folder (in my case C:\Users\Christian\Documents\Cryptomator)
2. Minimize Cryptomator to tray
3. Access some files and reboot windows without shutting down Cryptomator first
4. After the next boot try to open the vault again.
1 Like