Cryptomator 1.5.0 not showing GUI

Hi,

I installed Cryptomator 1.5.0 on my Laptops -> Everything OK.
I also Upgraded Cryptomator on my desktop to 1.5.0 … Error ??
Removed Cryptomator and Docan driver.
Reboot desktop.
Update to lasted Windows Patches -> OK
Windows 10 version 1909 build 18363.778 -> update 2020-04

Error in errorlog:

23:07:42.356 [main] INFO  org.cryptomator.launcher.Cryptomator - Starting Cryptomator 1.5.0 on Windows 10 10.0 (amd64)
23:07:42.356 [main] DEBUG org.cryptomator.logging.DebugMode - Debug mode enabled
23:07:42.356 [main] DEBUG org.cryptomator.launcher.IpcFactory - [Client] Failed to connect.
23:07:42.700 [main] DEBUG org.cryptomator.launcher.IpcFactory - [Server] Wrote IPC port 50138 to C:\Users\jan\AppData\Roaming\Cryptomator\ipcPort.bin
23:07:42.700 [main] DEBUG o.c.launcher.IpcProtocolImpl - Received launch args: 
23:07:42.700 [main] DEBUG org.cryptomator.launcher.Cryptomator - Did not find running application instance. Launching GUI...
23:07:42.950 [main] DEBUG o.c.ui.traymenu.TrayIconController - initialized tray icon
23:07:42.950 [main] DEBUG org.cryptomator.launcher.IpcFactory - [Server] Shut down

settings.json file
Jason.file

"directories": [
    {
      "id": "uh2I-LCUFXp3",
      "path": "X:\\",
      "unlockAfterStartup": false,
      "revealAfterMount": true,
      "usesIndividualMountPath": false,
      "usesReadOnlyMode": false,
      "mountFlags": ""
    }
  ],
  "askedForUpdateCheck": false,
  "checkForUpdatesEnabled": true,
  "startHidden": false,
  "port": 42427,
  "numTrayNotifications": 3,
  "preferredGvfsScheme": "DAV",
  "debugMode": true,
  "preferredVolumeImpl": "WEBDAV",
  "theme": "LIGHT",
  "uiOrientation": "LEFT_TO_RIGHT",
  "licenseKey": ""
}

I used cryptomator for many years … but this is not funny anymore.
At this moment I lost ALL data !!!

Question:
ANY idea why Cryptomator is not running ??

First and foremost: You did not loose any data.

This is a quite unspecific error description. Assuming from the thread topic, i assume that Cryptomator does not start. My first question is, if these lines are the complete log file?

In the normal case, after the message of initializing the tray icon you have two more messages:

23:47:43.096 [main] DEBUG o.cryptomator.ui.launcher.UiLauncher - Hiding application...
23:47:43.104 [main] DEBUG org.cryptomator.common.CommonsModule - Starting App Background Thread 001

Here may be a hint what caused the immidiate shutdown of the application. I can imagine that our graphical framework crashed for some reason.

Btw: WRITING IN CAPITAL LETTERS DOES NOT HELP IN ANY WAY.

Hi,

  1. yes correct … not losing data . I can not access the data … but that is for now the same result.
  2. I don’t understand the remark about writing in capitals?
  3. I checked on my laptop -> Cryptomator successfully upgraded to v1.5.0 ->
    Data is on local HDD and i see in \AppData\Roaming\Cryptomator there is a file ipcPort.bin.
  4. On Virtual Desktop I upgraded to data on local drive X: to Cryptomator v1.5.0 and that is working -> perfectly! -> after that Cryptomator locked all volumes again and I quit Cryptomator to free drive X: Cryptodata.
  5. On physical desktop drive mapping X: to same Cryptodata volume -> Cryptomator will not show gui and this ipcPort.bin file is missing !
  6. I re-installed Cryptomator v1.4.15.exe on physical desktop -> without unlocking data -> Cryptomator screen visible -> ipcPort.bin file available.
    Re-installed Cryptomator v1.5.0 -> no show and ipcPort.bin file is gone!
  7. Created a drive mapping from laptop to desktop -> same cryptodata volume -> aha … I can select the masterkey.crypmotator but selection screen still holds two options Back or Choose.

My conclusion for my configuration is: Cryptomator v1.5.0 works if data is on local disk not on a fileshare ??

I will reboot my laptop now and create drive mapping X: again and start Cryptomator. After that I will upload the logfiles.

huh … I can’t upload logfiles … ok

If I delete settings.json then show is ok
If I mount cryptodata from local hdd then show is ok.

{
  "directories": [
    {
      "id": "TbgOgt0lcNbN",
      "path": "C:\\Data\\Cryptomator-Data-Local-v1-5-0",
      "mountName": "Cryptomator_Data_Local_v1_5_0",
      "winDriveLetter": "J",
      "unlockAfterStartup": false,
      "revealAfterMount": true,
      "usesIndividualMountPath": false,
      "usesReadOnlyMode": false,
      "mountFlags": ""
    }
  ],
  "askedForUpdateCheck": false,
  "checkForUpdatesEnabled": true,
  "startHidden": false,
  "port": 42427,
  "numTrayNotifications": 3,
  "preferredGvfsScheme": "DAV",
  "debugMode": true,
  "preferredVolumeImpl": "DOKANY",
  "theme": "LIGHT",
  "uiOrientation": "LEFT_TO_RIGHT",
  "licenseKey": ""
}

If I mount cryptodata from remote SMB3 enabled Windows 10 pro share drive X: then no show !
This worked in former version 1.4.15.

{
  "directories": [
    {
      "id": "xUhkpiO51laj",
      "path": "X:\\",
      "unlockAfterStartup": false,
      "revealAfterMount": true,
      "usesIndividualMountPath": false,
      "usesReadOnlyMode": false,
      "mountFlags": ""
    }
  ],
  "askedForUpdateCheck": false,
  "checkForUpdatesEnabled": true,
  "startHidden": false,
  "port": 42427,
  "numTrayNotifications": 3,
  "preferredGvfsScheme": "DAV",
  "debugMode": true,
  "preferredVolumeImpl": "DOKANY",
  "theme": "LIGHT",
  "uiOrientation": "LEFT_TO_RIGHT",
  "licenseKey": ""
}

This is tested from my Laptop and from another Physical workstation. Both Windows 10 Pro build 1909 patched 2020-04 -> OS Build 18363.778

If I first mount local data -> show is ok , then add second local data -> show is ok.
If i first mount local data -> show is ok , then add second remote data via drive X: -> no show.

{
  "directories": [
    {
      "id": "FfSyt_8qU-I2",
      "path": "C:\\Data\\Cryptomator-Data-Local-v1-5-0",
      "mountName": "Cryptomator_Data_Local_v1_5_0",
      "winDriveLetter": "Z",
      "unlockAfterStartup": false,
      "revealAfterMount": true,
      "usesIndividualMountPath": false,
      "usesReadOnlyMode": false,
      "mountFlags": ""
    },
    {
      "id": "F_kGiPOMjUB9",
      "path": "X:\\",
      "unlockAfterStartup": false,
      "revealAfterMount": true,
      "usesIndividualMountPath": false,
      "usesReadOnlyMode": false,
      "mountFlags": ""
    }
  ],
  "askedForUpdateCheck": false,
  "checkForUpdatesEnabled": false,
  "startHidden": false,
  "port": 42427,
  "numTrayNotifications": 3,
  "preferredGvfsScheme": "DAV",
  "debugMode": false,
  "preferredVolumeImpl": "DOKANY",
  "theme": "LIGHT",
  "uiOrientation": "LEFT_TO_RIGHT",
  "licenseKey": ""
}

Solution:
Remove setttings.json and mount local data again -> show = ok

Note1:
For now I will restore data on Windows 10 pro workstation to former version 1.4.15 to have a working situation again.

Note2:
I tested cryptomator and data was on Onedrive -> Show ok

Request:
A solution for a remote connected SMB3 Windows 10 Pro data drive.

To restore the original data into cryptodata v1.4.15 delete D and M directory and then restore :slight_smile:

Reversed to Cryptomator v1.4.15. Data available again.

I ordered a donation key to support the Cryptomator project teams to keep up the good work.

Interesting, you’re the second person reporting this behaviour:

Can you confirm this is the same issue? With the “add existing vault” dialog just not doing anything? Maybe you have something in common with @amrods here.

I am having the same issue again. This time I will not try to fix it soon, so you can guide me to provide more information. I am at the step where I try to open Cryptomator after having synced my cloud vaults. I use Dropbox. Cryptomator starts (I see the icon in my dock), but then immediately closes. Nothing new is written in the logs. I’ll wait for your instructions.

BTW I’m using macOS 10.15.4

Can you please run it from Terminal:

/Applications/Cryptomator.app/Contents/MacOS/Cryptomator

It might contain more info than the log does.

Same behavior, Cryptomator doesn’t stay open.

Yes, but does it log anything to stdout?

amrods issue is with macOS 10.15.4
I am isung Windows 10 Pro build 1909 with updates up to 2020-04

I tested something news.
new configuration:
Create new local data disk L: on Windows 10 Virtual Desktop
Restored cryptodate v1.4.15 onto this new drive.

Connected a new Physical Win10 Pro Desktop to this new FileShare drive L:
Tested Cryptomator version 1.4.15 -> working.

Test journal:

  1. Locked all vaults.

  2. removed vaults from Show

  3. Removed Docan Lib version 1.12

  4. rebooted desktop

  5. Installed Cryptomator version 1.5.0 ( as user not admin )
    uac -> Admin username/PW

  6. Accept License

  7. install in default C:\Program Files\Cryptomator Destination location

  8. Select ALL -> Cryptomator / Dokan File Driver / WebDav

  9. Install Dokan Lib 1.3.0.1000 (x64)

  10. only Dokan Core

  11. Install

  12. Launch Cryptomator v1.5.0

  13. Show visible :slight_smile:

  14. Add Vault1 -> Open Existing Vault at Data-Jan-T ( copy of restored data in new LUN )

  15. Warning: Your vault needs to be upgraded to new format -> Upgrade Vault -> I see two Windows, one origional selection window ADD vault and Windows to Upgrade vault

  16. Not possible to click Upgrade Vault -> I have to close ADD Vault first.

  17. Close Window Add Vault.

  18. Click Upgrade Vault … Nothing seems to happen ???

  19. Enable logging

  20. Closed Upgrade Vault windows after 5 minutes -> nothing is happening ??

  21. in tasktray only show/preferences -> I can not quit.
    Have to kill the task

  22. Killed task -> I am not a local admin on my system …

  23. killed task by local admin.

  24. Logged in as local administrator

  25. Checked Drive mappings -> OK

  26. Installed Cryptomator version 1.5.0 as Local Admin

  27. Launch Cryptomator v1.5.0

  28. Show visible :slight_smile:

  29. Add Vault1 -> Open Existing Vault at Data-Jan-T ( copy of restored data in new LUN )

  30. Same issue
    Warning: Your vault needs to be upgraded to new format -> Upgrade Vault -> I see two Windows, one origional selection window ADD vault and Windows to Upgrade vault

  31. Not possible to click Upgrade Vault -> I have to close ADD Vault first.

  32. click Upgrade Vault -> nothing happens …

  33. in tasktray only show/preferences -> I can not quit.
    Have to kill the task -> OK

  34. Copy ALL data from drive T: to local drive

  35. delete all logfiles in \AppData\Roaming\Cryptomator

  36. delete setting.json file

  37. ipcPort.bin file exists

  38. Run Cryptomator.exe version 1.5.0 as Local Admin

  39. Two windows -> ADD Vault Done …Click Done and window … Local-data-Drive-T Upgrade Vault

  40. Click upgrade Vault.

  41. Warning Fully synced -> Yes … Next enter PW -> < password >

  42. Migrate Vault …

  43. Successfully migrated -> unlock your vault …

  44. < password > Unlock … reveal data -> OK Drive A: as vault …

  45. Check data -> Keepass data accessible -> I can open Keepass -> Perfect …

  46. Close Keepass

  47. lock Vault

  48. Remove vault from Cryptomator, and Quit Cryptomator

  49. Delete on remote Drive T: directory D and M and all masterkey.cryptomator* ( 2017 dated ) files

  50. Copy directory D from local migrated Cryptomator to Remote Drive T:

  51. Copy also the masterkey* with ( 2020 dated ) to Remote Drive T:

  52. Launch Cryptomator and Add migrated vault from remote drive T:

  53. After selecting masterkey.cryptomator from remote drive T: with migrated data still not possible to access this data.

  54. stuck in selecting screen to open masterkey.cryptomator

  55. If I select the local drive I can access the data but not lock the vault and Quit Cryptomator ??
    Note: Dokany driver … I will switch to Webdav

  56. no show

16:14:50.819 [main] INFO org.cryptomator.launcher.Cryptomator - Starting Cryptomator 1.5.0 on Windows 10 10.0 (amd64)
16:14:50.819 [main] DEBUG org.cryptomator.logging.DebugMode - Debug mode enabled
16:14:50.819 [main] DEBUG org.cryptomator.launcher.IpcFactory - [Client] Reading IPC port from C:\Users\sa_jan\AppData\Roaming\Cryptomator\ipcPort.bin
16:14:50.819 [main] DEBUG org.cryptomator.launcher.IpcFactory - [Client] Connecting to port 51213…
16:14:53.475 [main] DEBUG org.cryptomator.launcher.IpcFactory - [Client] Failed to connect.
16:14:53.506 [main] DEBUG org.cryptomator.launcher.IpcFactory - [Server] Wrote IPC port 51241 to C:\Users\sa_jan\AppData\Roaming\Cryptomator\ipcPort.bin
16:14:53.506 [main] DEBUG o.c.launcher.IpcProtocolImpl - Received launch args:
16:14:53.506 [main] DEBUG org.cryptomator.launcher.Cryptomator - Did not find running application instance. Launching GUI…
16:14:53.709 [main] DEBUG o.c.ui.traymenu.TrayIconController - initialized tray icon
16:14:53.709 [main] DEBUG org.cryptomator.launcher.IpcFactory - [Server] Shut down
16:15:04.584 [AWT-EventQueue-0] DEBUG org.cryptomator.common.CommonsModule - Starting App Background Thread 001
16:15:04.584 [App Background Thread 001] DEBUG o.c.ui.launcher.FxApplicationStarter - Starting JavaFX runtime…
16:15:05.041 [JavaFX Application Thread] INFO o.c.ui.launcher.FxApplicationStarter - JavaFX Runtime started.
16:15:05.055 [JavaFX Application Thread] INFO org.cryptomator.jni.FunctionsLoader - loaded WinFunctions.dll
16:15:05.225 [JavaFX Application Thread] TRACE o.cryptomator.ui.fxapp.FxApplication - FxApplication.start()
16:15:05.835 [JavaFX Application Thread] DEBUG org.cryptomator.ui.common.FontLoader - Loaded family: Font Awesome 5 Free Solid
16:15:05.968 [JavaFX Application Thread] DEBUG o.c.u.m.MainWindowTitleController - init MainWindowTitleController
16:15:06.167 [JavaFX Application Thread] DEBUG o.c.u.m.MainWindowController - init MainWindowController
16:15:12.376 [JavaFX Application Thread] DEBUG o.cryptomator.ui.fxapp.FxApplication - Showing Preferences

ipcPort.bin is gone !!

question:
any idea why this is not working if I use remote connected disk L: ?

Where can I upoad the logfile for you to debug what’s going on?

Tomorrow we will release the first bugfix version with more verbose logging in the “add vault” dialog. Hopefully this will shed some light on this issue.

That would be nice.
Are you interested in the logfiles i have saved ?
How to hand over?

Not yet, but I’m interested in the log files you’re going to have when re-attempting to add a vault with 1.5.1. You can send them via PN in this forum.

He means to send a private message(PM). (He made a typo)

Click on the user picture and then on message button in the right upper corner of the popup box.

I think I found the solution.

I added a new disk and created a brand new share on my W10Pro workstation
I created a new drive mapping R: from another workstation.
and a brand new Vault on the new empty mapped Drive R:
This worked :slight_smile:
Unlock vault / lock vault / removed vault / added vault … yes … working
Reboot system and unlock vaults again …
I also mounted the local vault ( already worked )

{
  "directories": [
    {
      "id": "NdaL1TFoYKhL",
      "path": "C:\\dataT",
      "mountName": "dataT",
      "winDriveLetter": "J",
      "unlockAfterStartup": false,
      "revealAfterMount": true,
      "usesIndividualMountPath": false,
      "usesReadOnlyMode": false,
      "mountFlags": ""
    },
    {
      "id": "Pz7e-qPIZehO",
      "path": "X:\\DataJan151",
      "mountName": "DataJan151",
      "winDriveLetter": "R",
      "unlockAfterStartup": false,
      "revealAfterMount": true,
      "usesIndividualMountPath": false,
      "usesReadOnlyMode": false,
      "mountFlags": ""
    }
  ],
  "askedForUpdateCheck": false,
  "checkForUpdatesEnabled": true,
  "startHidden": false,
  "port": 42427,
  "numTrayNotifications": 3,
  "preferredGvfsScheme": "DAV",
  "debugMode": true,
  "preferredVolumeImpl": "WEBDAV",
  "theme": "LIGHT",
  "uiOrientation": "LEFT_TO_RIGHT",
  "licenseKey": ""
}

Started copy data from old Vault to new remote Vault … long file name issues …
image

aha …
skip these files and stop coping.

Changed share names to smaller dir
This is working … for some time but again errors

.strange filename try again … no success …
I will skip this one …

Again file name is not valid or too long
aha … this is a filename I recognise
Name is like aaa bbb ccc ddd 000. eee-fff.ggg-hhh.xlsx

Note:
When I created a new Vault data-Jan-1.5.1 Cryptomator could not handle the . between 1 and 5 and 5 and 1
Had to change name into Data-Jan-151 to create Vault

Question:
Is it possible that this version of Cryptomator can not handle the dot.s in a filename ??
I see more filenames with dot’s in name but these are shorter ??

Continue checking … on source drive … aha … I see file has not the excel icon and file is an Excel sheet

Possible cause:
Data is corrupted before or during migration ?
I will check … Source data is on local drive … so not a SMB3 issue :slight_smile:
I will go back to version 1.4.15 and check if data is corrupted before migration, that will explain.
Pitty … I can;t find the upgrade.log anymore as I installed and reinstalled several times to debug.
Checked: Data is not corrupted before migration but i have a long filename issue.

Question:
Is there a tool to check upfront if cryptomator can read all data, before upgrade vault to latest version?

I created a new Local volume and restored the version 6 data.
Opening with Cryptomator 1.4.15 … Checked -> I removed the long filenamed files -> OK
Upgrade to version 1.5.0 -> successfully
Reveal local dive -> working …
Upgrade to version 1.5.1 -> OK
Reveal local dive -> working …
removed vault and quit Cryptomator.

Switch to other Desktop
Installed v1.5.1
I can create a lot of local vaults

If I try to mount masterkey from remote drive X: stuck again in selectionscreen.

image

image

Notice! NewVault2 = X:\ but NewVault2 is already occupied and incorrect!

If I remove ALL local vaults and add only remote vault
image

Stuck in selection screen. I can close this screen but can not unlock remote Vault.

To recover from this ( no show ) just delete json.setting file.

11:33:19.000 [main] INFO  org.cryptomator.launcher.Cryptomator - Starting Cryptomator 1.5.1 on Windows 10 10.0 (amd64)
11:33:19.924 [JavaFX Application Thread] INFO  o.c.ui.launcher.FxApplicationStarter - JavaFX Runtime started.
11:33:19.938 [JavaFX Application Thread] INFO  org.cryptomator.jni.FunctionsLoader - loaded WinFunctions.dll
11:33:40.241 [JavaFX Application Thread] DEBUG org.cryptomator.logging.DebugMode - Debug mode enabled
11:33:41.242 [App Scheduled Executor 01] DEBUG o.c.common.settings.SettingsProvider - Attempting to save settings to C:\Users\jan\AppData\Roaming\Cryptomator\settings.json
11:33:41.250 [App Scheduled Executor 01] INFO  o.c.common.settings.SettingsProvider - Settings saved to C:\Users\jan\AppData\Roaming\Cryptomator\settings.json
11:33:43.431 [JavaFX Application Thread] DEBUG org.cryptomator.common.CommonsModule - Starting App Scheduled Executor 02
11:33:43.995 [JavaFX Application Thread] DEBUG org.cryptomator.common.CommonsModule - Starting App Background Thread 003
11:33:43.997 [JavaFX Application Thread] DEBUG o.cryptomator.ui.fxapp.UpdateChecker - Checking for updates...
11:33:44.432 [App Scheduled Executor 01] DEBUG o.c.common.settings.SettingsProvider - Attempting to save settings to C:\Users\jan\AppData\Roaming\Cryptomator\settings.json
11:33:44.434 [App Scheduled Executor 01] INFO  o.c.common.settings.SettingsProvider - Settings saved to C:\Users\jan\AppData\Roaming\Cryptomator\settings.json
11:33:44.627 [JavaFX Application Thread] INFO  o.cryptomator.ui.fxapp.UpdateChecker - Current version: 1.5.1, lastest version: 1.4.15
11:35:39.785 [App Scheduled Executor 02] DEBUG o.c.common.settings.SettingsProvider - Attempting to save settings to C:\Users\jan\AppData\Roaming\Cryptomator\settings.json
11:35:39.788 [App Scheduled Executor 02] INFO  o.c.common.settings.SettingsProvider - Settings saved to C:\Users\jan\AppData\Roaming\Cryptomator\settings.json
11:35:44.466 [App Scheduled Executor 01] DEBUG o.c.common.settings.SettingsProvider - Attempting to save settings to C:\Users\jan\AppData\Roaming\Cryptomator\settings.json
11:35:44.468 [App Scheduled Executor 01] INFO  o.c.common.settings.SettingsProvider - Settings saved to C:\Users\jan\AppData\Roaming\Cryptomator\settings.json
11:35:50.589 [JavaFX Application Thread] DEBUG o.c.u.a.AddVaultWelcomeController - AddVaultWelcomeController.chooseExistingVault()
11:35:58.554 [App Scheduled Executor 02] DEBUG o.c.common.settings.SettingsProvider - Attempting to save settings to C:\Users\jan\AppData\Roaming\Cryptomator\settings.json
11:35:58.556 [App Scheduled Executor 02] INFO  o.c.common.settings.SettingsProvider - Settings saved to C:\Users\jan\AppData\Roaming\Cryptomator\settings.json
11:37:19.410 [main] INFO  org.cryptomator.launcher.Cryptomator - Starting Cryptomator 1.5.1 on Windows 10 10.0 (amd64)
11:37:19.420 [main] DEBUG org.cryptomator.logging.DebugMode - Debug mode enabled
11:37:19.421 [main] DEBUG org.cryptomator.launcher.IpcFactory - [Client] Reading IPC port from C:\Users\jan\AppData\Roaming\Cryptomator\ipcPort.bin
11:37:19.421 [main] DEBUG org.cryptomator.launcher.IpcFactory - [Client] Connecting to port 50084...
11:37:19.569 [RMI TCP Connection(2)-127.0.0.1] DEBUG o.c.launcher.IpcProtocolImpl - Received launch args: 
11:37:19.571 [main] INFO  org.cryptomator.launcher.Cryptomator - Found running application instance. Shutting down...
11:37:19.572 [ShutdownTasks] DEBUG org.cryptomator.common.ShutdownHook - Running graceful shutdown tasks...
11:37:24.787 [JavaFX Application Thread] DEBUG o.cryptomator.ui.fxapp.FxApplication - Showing MainWindow

checked with Webdav or dokan -> same result
Checked from 3 different desktops / laptops I have.
Local acces = OK … Remote Windows shared drive unable to unlock remote vault.

Any help to solve this issue is more than welcome.

cheers,
A posionate cryptomator fan :slight_smile:

I checked some blogs and found a workarround .
Cyberduck …
I have no idea what this is … checking … Testing …
waauw …

image

I can technically open my Remote CryptoVault.

For now OK but i still need a Cryptomator solution because Cyberduck is too fancy for normal non technically users /usage.

It looks like the X: vault is the only one that isn’t nested in a subfolder. It’s in the root of the mounted drive.

I’ve never seen this before as usually Cryptomator would make a subfolder with the vault name? Perhaps this causes issues in 1.5.0?

1 Like

THANKS … This is the workarround !!
This behaviour is not seen in 1.4.x
I just upgrade same datastructure from 1.4.15 into 1.5.1
My expection is that upgrading software does not change my setup of the infrastructure.

I map a shared directory, not a complete disk.

Conclusion

Map drive X: to \\servername\drive\dir    ....  works fine for <1.5.0
Map drive X: to \\servername\drive        ....  works fine for >=  1.5.0
  "directories": [
    {
      "id": "t6_ZDfrodf2U",
      "path": "X:\\CryptoDisk-Data-Jan",
      "mountName": "CryptoDisk_Data_Jan",
      "winDriveLetter": "J",

I hope in new release this will be adjusted.

For now a “solution”
Thanks mate

Now you see the strengt of open source and communities.
A happy Cryptomator and Cyberduck user.

Glad this has worked.

Cryptomator uses the folder name to name the vault in the GUI, it has for many versions.
Renaming a vault renames the folder. Cryptomator could not rename drive maps/letters!
I am surprised 1.4 even worked with this setup!

I’d recommend making a folder called Vaults and nesting your vault folders in there.

Example:
Vault at \servername\drive\Vaults\VAULTNAME1
map x: to \servername\drive\Vaults
x: will have a folder called VAULTNAME1 containing your first vault
you could add further vaults with folders VAULTNAME2 VAULTNAME3 etc