No more access to encrypted data. Password not accepted.

[Stefan86]

Hello dear community. I have the following problem. I have encrypted my data using Cryptomator v. 1.531 at a cloud provider. A week ago I could no longer access the data. My password is not accepted. An update to version 1.6x unfortunately only brings the message window that an update of the database must be performed. When I confirm this and enter the password, the password is not accepted either. Enclosed is the corresponding log.

Does anyone have any idea how I can get my data?

13:32:04.946 [main] INFO  org.cryptomator.launcher.Cryptomator - Starting Cryptomator 1.5.13 on Windows 10 10.0 (amd64)
13:32:07.750 [JavaFX Application Thread] INFO  o.c.ui.launcher.FxApplicationStarter - JavaFX Runtime started.
13:32:09.130 [JavaFX Application Thread] WARN  o.cryptomator.ui.fxapp.FxApplication - has visible stages: true
13:32:10.165 [main] INFO  org.cryptomator.launcher.Cryptomator - Starting Cryptomator 1.5.13 on Windows 10 10.0 (amd64)
13:32:10.305 [main] INFO  org.cryptomator.launcher.Cryptomator - Found running application instance. Shutting down...
13:39:01.490 [JavaFX Application Thread] INFO  o.c.w.k.WindowsProtectedKeychainAccess - Unable to load existing keychain file, creating new keychain.
13:39:02.485 [App Scheduled Executor 01] INFO  o.c.common.settings.SettingsProvider - Settings saved to C:\Users\user\AppData\Roaming\Cryptomator\settings.json
13:39:43.303 [App Background Thread 003] INFO  org.cryptomator.common.vaults.Vault - Storing file name length limit of 220
13:39:44.217 [App Background Thread 003] INFO  com.dokany.java.DokanyMount - Dokany API/driver version: 141 / 400
13:39:44.308 [App Scheduled Executor 01] INFO  o.c.common.settings.SettingsProvider - Settings saved to C:\Users\ user \AppData\Roaming\Cryptomator\settings.json
13:39:50.222 [App Background Thread 003] WARN  o.c.frontend.dokany.MountFactory - Mounting timed out.
13:39:50.222 [App Background Thread 003] INFO  o.c.ui.unlock.UnlockWorkflow - Unlock of 'U_Sammlung' succeeded.
13:40:59.890 [JavaFX Application Thread] WARN  o.cryptomator.ui.fxapp.FxApplication - has visible stages: false
13:45:19.411 [main] INFO  org.cryptomator.launcher.Cryptomator - Starting Cryptomator 1.5.13 on Windows 10 10.0 (amd64)
13:45:19.528 [main] INFO  org.cryptomator.launcher.Cryptomator - Found running application instance. Shutting down...
13:45:19.541 [JavaFX Application Thread] WARN  o.cryptomator.ui.fxapp.FxApplication - has visible stages: true
13:45:31.263 [App Scheduled Executor 02] INFO  o.c.common.settings.SettingsProvider - Settings saved to C:\Users\ user \AppData\Roaming\Cryptomator\settings.json
13:45:53.663 [App Background Thread 006] INFO  org.cryptomator.common.vaults.Vault - Storing file name length limit of 220
13:45:54.671 [App Scheduled Executor 01] INFO  o.c.common.settings.SettingsProvider - Settings saved to C:\Users\ user \AppData\Roaming\Cryptomator\settings.json
13:46:17.306 [JavaFX Application Thread] WARN  o.cryptomator.ui.fxapp.FxApplication - has visible stages: false
14:25:08.858 [JavaFX Application Thread] WARN  o.cryptomator.ui.fxapp.FxApplication - has visible stages: true
14:51:16.391 [JavaFX Application Thread] WARN  o.cryptomator.ui.fxapp.FxApplication - has visible stages: false
14:51:58.843 [JavaFX Application Thread] WARN  o.cryptomator.ui.fxapp.FxApplication - has visible stages: true
14:52:09.674 [App Scheduled Executor 02] INFO  o.c.common.settings.SettingsProvider - Settings saved to C:\Users\ user \AppData\Roaming\Cryptomator\settings.json
14:52:30.701 [App Background Thread 006] INFO  org.cryptomator.common.vaults.Vault - Storing file name length limit of 220
14:52:31.704 [App Scheduled Executor 01] INFO  o.c.common.settings.SettingsProvider - Settings saved to C:\Users\ user \AppData\Roaming\Cryptomator\settings.json
14:52:37.650 [JavaFX Application Thread] WARN  o.cryptomator.ui.fxapp.FxApplication - has visible stages: false

Translated with www.DeepL.com/Translator (free version)

[Michael]

Hi.

@Stefan86

o.c.frontend.dokany.MountFactory - Mounting timed out.

Have you tried this?

[1.5.15 / 1.5.16] Cannot mount vault: Mount Timed Out

Hey Community, since the issue still pops out from time to time, I decided to write a short post about a problem of Cryptomator 1.5.15 & 1.5.16 on Windows systems. The Problem You cannot unlock your vault, a cryptic error message is displayed with the request to contact us. Use the following checklist, to see if you are in the right topic: You are using Windows 10 Cryptomator version is 1.5.15 or 1.5.16 In the general preferences, tab “virtual volume”, the option “Dokany” is selecte…

I recommend to switch to WinFSP and try again to open your vault. If this is the solution, please then update your cryptomator to the latest version

[infeo]

@Stefan86

My password is not accepted.

According to the log file your password was accepted. Are you sure the password was rejected or were you unable to access the data after unlock? (aka the password window closes after clicking the unlock button)