Vault Upgrade from 4 to 5 -> Vault does not open anymore

I installed the Cryptomator version today (from 1.4.14 to 1.4.15), after that, a vault upgrade was neccessary. i put in my password, confirming my sync is done, but i can’t pass the “vault upgrade” screen. no warning shown. now i can’t open my files. any help?

crawling through the logfiles, i found this:

Cryptomator0.log:

17:57:48.670 [main] INFO  org.cryptomator.launcher.Cryptomator - Starting Cryptomator 1.4.15 on Windows 10 10.0 (amd64)
17:57:48.673 [main] DEBUG org.cryptomator.logging.DebugMode - Debug mode enabled
17:57:48.674 [main] DEBUG org.cryptomator.launcher.IpcFactory - **[Client] Failed to connect.**
17:57:48.975 [main] DEBUG org.cryptomator.launcher.IpcFactory - [Server] Wrote IPC port 12828 to C:\Users\dee1337\AppData\Roaming\Cryptomator\ipcPort.bin
17:57:48.976 [main] INFO  o.c.launcher.IpcProtocolImpl - Received launch args: 
17:57:48.978 [main] DEBUG org.cryptomator.launcher.Cryptomator - Did not find running application instance. Launching GUI...
17:57:49.529 [JavaFX Application Thread] INFO  org.cryptomator.launcher.Cryptomator - JavaFX application started.
17:57:49.548 [JavaFX Application Thread] DEBUG org.cryptomator.ui.l10n.Localization - Loaded localization default file: /localization/en.txt
17:57:49.548 [JavaFX Application Thread] DEBUG org.cryptomator.ui.l10n.Localization - Detected language "de" and region "DE"
17:57:49.550 [JavaFX Application Thread] TRACE org.cryptomator.ui.l10n.Localization - Attempting to load localization from: /localization/de_DE.txt
17:57:49.550 [JavaFX Application Thread] TRACE org.cryptomator.ui.l10n.Localization - Attempting to load localization from: /localization/de.txt
17:57:49.639 [JavaFX Application Thread] INFO  org.cryptomator.jni.JniModule - loaded WinFunctions.dll
17:57:49.673 [JavaFX Application Thread] INFO  o.c.ui.controllers.MainController - Unable to setPreferencesHandler, probably not supported on this OS.
17:57:50.809 [JavaFX Application Thread] INFO  o.c.ui.controllers.WelcomeController - Current version: 1.4.15, lastest version: 1.4.15
17:58:21.603 [JavaFX Application Thread] ERROR org.cryptomator.ui.util.Tasks - Unhandled exception
org.cryptomator.cryptolib.api.AuthenticationFailedException: Header MAC doesn't match.
	at org.cryptomator.cryptolib.v1.FileHeaderCryptorImpl.decryptHeader(FileHeaderCryptorImpl.java:113)
	at org.cryptomator.ui.model.upgrade.UpgradeVersion4to5.migrate(UpgradeVersion4to5.java:111)
	at org.cryptomator.ui.model.upgrade.UpgradeVersion4to5$1.visitFile(UpgradeVersion4to5.java:87)
	at org.cryptomator.ui.model.upgrade.UpgradeVersion4to5$1.visitFile(UpgradeVersion4to5.java:65)
	at java.base/java.nio.file.Files.walkFileTree(Files.java:2724)
	at org.cryptomator.ui.model.upgrade.UpgradeVersion4to5.upgrade(UpgradeVersion4to5.java:65)
	at org.cryptomator.ui.model.upgrade.UpgradeStrategy.upgrade(UpgradeStrategy.java:74)
	at org.cryptomator.ui.controllers.UpgradeController.lambda$upgrade$0(UpgradeController.java:128)
	at org.cryptomator.ui.util.Tasks.lambda$create$0(Tasks.java:33)
	at org.cryptomator.ui.util.Tasks$TaskImpl.call(Tasks.java:139)
	at javafx.concurrent.Task$TaskCallable.call(Task.java:1425)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.base/java.lang.Thread.run(Thread.java:834)

let me paste a part of upgrade.log, too:

17:58:18.435 [Background Thread 2] INFO  o.c.ui.model.upgrade.UpgradeStrategy - Upgrading E:\GDRIVE\[ VERSCHLUESSELT ]\Verschluesselt from 4 to 5.
17:58:18.598 [Background Thread 2] INFO  o.c.ui.model.upgrade.UpgradeStrategy - Backuped masterkey.
17:58:18.599 [Background Thread 2] INFO  o.c.u.m.upgrade.UpgradeVersion4to5 - Starting migration of E:\GDRIVE\[ VERSCHLUESSELT ]\Verschluesselt\d\22\2J5MUUMSDI5ZJEPIR4GS7RVGNMHMR5\7DJE3HYLXWNFZCT4SFYFDHDWW6CGS4RK5F4KHGCM7ZCQ3AWU...
17:58:18.600 [Background Thread 2] INFO  o.c.u.m.upgrade.UpgradeVersion4to5 - 	Header read
17:58:18.602 [Background Thread 2] INFO  o.c.u.m.upgrade.UpgradeVersion4to5 - 	Skipping already migrated file

last entries (tail):

17:58:21.599 [Background Thread 2] INFO  o.c.u.m.upgrade.UpgradeVersion4to5 - Starting migration of E:\GDRIVE\[ VERSCHLUESSELT ]\Verschluesselt\d\EE\EQBHG4ZBK4CP24QQBUES5COBJU7AVS\WGG2WNO6FZBSQZO7576PAKOMGWCUJCL47D4JQS7PTZW2SW3ZXHF2QTUPP63KQLIX...
17:58:21.599 [Background Thread 2] INFO  o.c.u.m.upgrade.UpgradeVersion4to5 - 	Header read
17:58:21.599 [Background Thread 2] INFO  o.c.u.m.upgrade.UpgradeVersion4to5 - 	Skipping already migrated file
17:58:21.599 [Background Thread 2] INFO  o.c.u.m.upgrade.UpgradeVersion4to5 - Starting migration of E:\GDRIVE\[ VERSCHLUESSELT ]\Verschluesselt\d\EE\EQBHG4ZBK4CP24QQBUES5COBJU7AVS\WSGV44HTOLYVFE5WKVHU2DOOMIPWG43GKAIX7RBLUVLYAEG7HLGIMI26J4DU7UKIRY4QU===...
17:58:21.600 [Background Thread 2] INFO  o.c.u.m.upgrade.UpgradeVersion4to5 - 	Header read

There seems to be something wrong:

  1. Updating from 1.4.14 to 1.4.15 doesn’t require a vault migration
  2. Skipping already migrated file messages in log file indicate that the vault was already migrated

Are there any entries in your upgrade.log file that say one of the following things?

  • Migrating cleartext size X: Truncating to new ciphertext size: Y
  • Migrating cleartext size X: Re-encrypting chunk Y. New ciphertext size: Z

Vault format 4 is ancient. Event the migrator to version 5 is from 2016.

Therefore I strongly suspect your masterkey file (which contains the vault format) has been restored from a rather old revision.

thanks for your answer. no, the log doesn’t offer any other messages than posted above.

edit:
above i have posted a log of my 2nd installation (i thought, a fresh install could fix the problem), but i still have the old log files saved, and there it shows:

10:01:13.666 [Background Thread 2] INFO o.c.ui.model.upgrade.UpgradeStrategy - Upgrading E:\GDRIVE[ VERSCHLUESSELT ]\Verschluesselt from 4 to 5.
10:01:13.812 [Background Thread 2] INFO o.c.ui.model.upgrade.UpgradeStrategy - Backuped masterkey.
10:01:13.814 [Background Thread 2] INFO o.c.u.m.upgrade.UpgradeVersion4to5 - Starting migration of E:\GDRIVE[ VERSCHLUESSELT ]\Verschluesselt\d\22\2J5MUUMSDI5ZJEPIR4GS7RVGNMHMR5\7DJE3HYLXWNFZCT4SFYFDHDWW6CGS4RK5F4KHGCM7ZCQ3AWU…
10:01:13.876 [Background Thread 2] INFO o.c.u.m.upgrade.UpgradeVersion4to5 - Header read
10:01:13.878 [Background Thread 2] INFO o.c.u.m.upgrade.UpgradeVersion4to5 - Migrating cleartext size 6678: Re-encrypting chunk 0. New ciphertext size: 6814
10:01:13.882 [Background Thread 2] INFO o.c.u.m.upgrade.UpgradeVersion4to5 - Reencrypted last block
10:01:13.882 [Background Thread 2] INFO o.c.u.m.upgrade.UpgradeVersion4to5 - Updated header

[…]

10:02:59.440 [Background Thread 2] INFO o.c.u.m.upgrade.UpgradeVersion4to5 - Migrating cleartext size 2100768: Re-encrypting chunk 64. New ciphertext size: 2103976
10:02:59.549 [Background Thread 2] INFO o.c.u.m.upgrade.UpgradeVersion4to5 - Migrating cleartext size 1082644: Re-encrypting chunk 33. New ciphertext size: 1084364

[…] // reinstall

10:08:11.318 [Background Thread 3] INFO o.c.u.m.upgrade.UpgradeVersion4to5 - Starting migration of E:\GDRIVE[ VERSCHLUESSELT ]\Verschluesselt\d\EE\EQBHG4ZBK4CP24QQBUES5COBJU7AVS\WSGV44HTOLYVFE5WKVHU2DOOMIPWG43GKAIX7RBLUVLYAEG7HLGIMI26J4DU7UKIRY4QU===…
10:08:11.318 [Background Thread 3] INFO o.c.u.m.upgrade.UpgradeVersion4to5 - Header read
13:31:53.644 [Background Thread 2] INFO o.c.ui.model.upgrade.UpgradeStrategy - Upgrading E:\GDRIVE[ VERSCHLUESSELT ]\Verschluesselt from 4 to 5.
13:31:53.831 [Background Thread 2] INFO o.c.ui.model.upgrade.UpgradeStrategy - Backuped masterkey.
13:31:53.832 [Background Thread 2] INFO o.c.u.m.upgrade.UpgradeVersion4to5 - Starting migration of E:\GDRIVE[ VERSCHLUESSELT ]\Verschluesselt\d\22\2J5MUUMSDI5ZJEPIR4GS7RVGNMHMR5\7DJE3HYLXWNFZCT4SFYFDHDWW6CGS4RK5F4KHGCM7ZCQ3AWU…
13:31:53.833 [Background Thread 2] INFO o.c.u.m.upgrade.UpgradeVersion4to5 - Header read
13:31:53.834 [Background Thread 2] INFO o.c.u.m.upgrade.UpgradeVersion4to5 - Skipping already migrated file

i found a “solution”: i deinstalled 1.4.15, downloaded/installed Cryptomator 1.1.4 and i can access my files :open_mouth:
just doesn’t seem to work with newer versions.

update: old 1.1.4 “works” but now i have a lot of 0 size files, meaning my files were deleted.
seems i can’t count on cryptomator :frowning: lost a lot of important files.

The files have not been deleted, the format migration removed the file size information from the file header, so this is expected behaviour.

You should however not be able to open a vault of a newer version, unless your masterkey.cryptomator says it is an old version, which was my assumption in the first place:

I urge you to check what “vaultVersion” is stored inside it, what’s its last modification date and why you restored such an old masterkey file associated in a vault that you used to use with Cryptomator 1.4.14.

This is the root cause of your problem!