Error 09TB:8LNC:8MQR #3607

tvcmn · 2024-11-07T19:10:43Z

tvcmn
Nov 7, 2024

OS: Mac OS X / 15.1
App: 1.14.1 / dmg-5378

Description:
when try to open my vault

Details:

Error Code 09TB:8LNC:8MQR
org.cryptomator.integrations.mount.MountFailedException: org.cryptomator.jfuse.api.FuseMountFailedException: fuse_loop() returned prematurely with non-zero exit code -1
	at [email protected]/org.cryptomator.frontend.fuse.mount.FuseTMountProvider$FuseTMountBuilder.mount(FuseTMountProvider.java:132)
	at [email protected]/org.cryptomator.common.mount.Mounter.mount(Mounter.java:172)
	at [email protected]/org.cryptomator.common.vaults.Vault.unlock(Vault.java:163)
	at [email protected]/org.cryptomator.ui.keyloading.KeyLoadingStrategy.use(KeyLoadingStrategy.java:79)
	at [email protected]/org.cryptomator.ui.unlock.UnlockWorkflow.call(UnlockWorkflow.java:76)
	at [email protected]/org.cryptomator.ui.unlock.UnlockWorkflow.call(UnlockWorkflow.java:34)
	at [email protected]/javafx.concurrent.Task$TaskCallable.call(Unknown Source)
	at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
	at java.base/java.util.concurrent.CompletableFuture$UniAccept.tryFire(Unknown Source)
	at java.base/java.util.concurrent.CompletableFuture$Completion.run(Unknown Source)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.base/java.lang.Thread.run(Unknown Source)
Caused by: org.cryptomator.jfuse.api.FuseMountFailedException: fuse_loop() returned prematurely with non-zero exit code -1
	at [email protected]/org.cryptomator.jfuse.api.Fuse.mount(Fuse.java:130)
	at [email protected]/org.cryptomator.frontend.fuse.mount.FuseTMountProvider$FuseTMountBuilder.mount(FuseTMountProvider.java:129)
	... 12 more

asealey · 2024-11-29T16:56:57Z

asealey
Nov 29, 2024

This happened to me after upgrading to 1.14.2. I solved it by reinstalling fuse-t via homebrew

1 reply

TheBlinded Jan 15, 2025

Tried reinstalling fuse-it with homebrew but did not solve the problem. Other vaults are opened without any problems.

n0lz · 2024-12-23T16:17:06Z

n0lz
Dec 23, 2024

I have the same issue with version 1.14.2. On one system (MacBook Pro M1 Pro; macOS 15.2) I can open the vault. On the second system (Mac mini M2 Pro; macOS 15.2) I can't open the vault. Both have Cryptomator 1.14.2 and Fuse-T 1.0.44 installed

0 replies

bh11 · 2025-01-03T12:55:23Z

bh11
Jan 3, 2025

Same here, macOS 15.2 on Intel, Cryptomator 1.14.2 and Fuse-T 1.0.44.
The problem usually occurs after Cryptomator has been running for at least a few hours, maybe days.
Other vaults which are already open cannot be locked any more.
Re-starting Cryptomator doesn't help.
After quitting Cryptomator, I can see a number of CSExattrCryptoService processes (Finder subprocesses). After killing them, Cryptomator works normally again.

0 replies

airfl0w-0x1c · 2025-01-20T14:40:36Z

airfl0w-0x1c
Jan 20, 2025

I had the same issues mentioned here on MacBook Pro M2 Pro; macOS 15.2. Restarting or reinstalling via brew FUSE-T didn't help.

I have solved with:

brew uninstall fuse-t
Installing latest fuse-t (1.0.44) via mac-os installer: https://www.fuse-t.org/downloads
Make sure fuse-t-0 is available under network (locations) in Finder

0 replies

jd2476 · 2025-02-14T09:25:59Z

jd2476
Feb 14, 2025

Had the same issue but after upgrade to 1.15.1. Reinstalled fuse-t with homebrew didn't help.. Uninstalling & installing fuse-t from https://www.fuse-t.org/downloads also didn't work. Removing the vault from the vaults list and re-adding did work though. I'm not sure if it's due to the fuse-t reinstall from the website or not though.

3 replies

overheadhunter Apr 11, 2025
Maintainer

Removing the vault from the vaults list and re-adding did work though.

During re-adding a new "vault id" is generated, leading to a different path to which fuse-t mounts. This may be a hint: Sometimes a faulty unmount may lead to the old mount point being stuck, blocking re-mounts.

@infeo fyi

karlacio Apr 28, 2025

"Very" compatible with my workaround below

headstrongpete Oct 28, 2025

This.

Davelortenco · 2025-03-21T03:38:32Z

Davelortenco
Mar 21, 2025

Same issue here when upgrading from 1.7.5 (I used it for a long time without issues) to 1.15.1, on mac 13.2.

I tried all of the ideas above to get access to my vault without success. I even tried uninstall fuse-T and Cryptomator completely and installing over again in different order. Nothing.

I came back to 1.7.5 and everything works flawlessly again with the last fuse.t (1.0.47)

1- What is the actual risk for the vault of not updating and continue with 1.7.5 ?
2- What can be the last version with high probability of success ? (trying them all is not the way)

0 replies

karlacio · 2025-04-28T10:55:14Z

karlacio
Apr 28, 2025

Same here:
Mac Sequoia 15.3.2

Cryptomator 1.15.2 (dmg-5577)

Up to last week it worked today no more.

Tried:

reinstall fuse-t
restart mac
mount using webdav (applescript)

but no way to mount.

PS why this problem is discussed here and is not in Issues?

0 replies

karlacio · 2025-04-28T11:10:47Z

karlacio
Apr 28, 2025

On Macos with fuse-t if I change the mount point from "Automatically pick a suitable location" to a folder I select it works again.

Seem a problem on creating/using the random mount point used as default.

2 replies

ghost May 2, 2025

thanks, it did work for me, with similar approach I change the default volume type to "FUSE-T (Experimental)" instead of automatic from the Preferences in virtual drive tab,
and set volume type to "FUSE-T Experimental" instead of "Default (FUSE-T (Experimental))" from vault options and I did leave the mount point to automatically pick a suitable location (selecting a folder didn't work)

it did work with me without reinstalling fuse-t from the website or via homebrew (im using fuse-t from homebrew)

I'm using:
MacOS Sequoia 15.4
Cryptomator 1.15.2 (dmg-5577)
FUSE-T 1.0.47

Alchemyst0x Jun 29, 2025

Thanks - this fixed the issue for me as well, also on macOS. Tried reinstalling FUSE-T from both Homebrew and directly from the FUSE-T .pkg. The only thing that fixed it was changing the default mount point from automatic to one I selected manually.

sw_vers
ProductName:		macOS
ProductVersion:		15.5
BuildVersion:		24F74

Cryptomator version 1.17.0 (dmg-5789)
FUSE-T version 1.0.47

Adding an excerpt of the logs that just shows the error -> me messing with the settings -> finally reading this comment and changing the default mount point, and it starts working normally again:

01:34:15.042 [main] INFO  o.c.common.settings.SettingsProvider - Settings loaded from /Users/USER_NAME/Library/Application Support/Cryptomator/settings.json
01:34:15.111 [main] INFO  org.cryptomator.common.Environment - user.home: /Users/USER_NAME
01:34:15.111 [main] INFO  org.cryptomator.common.Environment - java.library.path: :/Applications/Cryptomator.app/Contents/app:/Users/USER_NAME/Library/Java/Extensions:/Library/Java/Extensions:/Network/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java:.
01:34:15.111 [main] INFO  org.cryptomator.common.Environment - user.language: en
01:34:15.111 [main] INFO  org.cryptomator.common.Environment - user.region: null
01:34:15.111 [main] INFO  org.cryptomator.common.Environment - logback.configurationFile: null
01:34:15.111 [main] INFO  org.cryptomator.common.Environment - cryptomator.settingsPath: /Users/USER_NAME/Library/Application Support/Cryptomator/settings.json
01:34:15.111 [main] INFO  org.cryptomator.common.Environment - cryptomator.ipcSocketPath: /Users/USER_NAME/Library/Application Support/Cryptomator/ipc.socket
01:34:15.111 [main] INFO  org.cryptomator.common.Environment - cryptomator.integrationsWin.keychainPaths: null
01:34:15.111 [main] INFO  org.cryptomator.common.Environment - cryptomator.integrationsWin.windowsHelloKeychainPaths: null
01:34:15.111 [main] INFO  org.cryptomator.common.Environment - cryptomator.p12Path: /Users/USER_NAME/Library/Application Support/Cryptomator/key.p12
01:34:15.111 [main] INFO  org.cryptomator.common.Environment - cryptomator.logDir: /Users/USER_NAME/Library/Logs/Cryptomator
01:34:15.111 [main] INFO  org.cryptomator.common.Environment - cryptomator.loopbackAlias: null
01:34:15.111 [main] INFO  org.cryptomator.common.Environment - cryptomator.mountPointsDir: /Users/USER_NAME/Library/Application Support/Cryptomator/mnt
01:34:15.111 [main] INFO  org.cryptomator.common.Environment - cryptomator.minPwLength: null
01:34:15.111 [main] INFO  org.cryptomator.common.Environment - cryptomator.appVersion: 1.17.0
01:34:15.111 [main] INFO  org.cryptomator.common.Environment - cryptomator.buildNumber: dmg-5789
01:34:15.111 [main] INFO  org.cryptomator.common.Environment - cryptomator.pluginDir: /Users/USER_NAME/Library/Application Support/Cryptomator/Plugins
01:34:15.112 [main] INFO  org.cryptomator.common.Environment - cryptomator.showTrayIcon: true
01:34:15.112 [main] INFO  org.cryptomator.common.Environment - cryptomator.disableUpdateCheck: null
01:34:15.112 [main] INFO  o.cryptomator.launcher.Cryptomator - Starting Cryptomator 1.17.0 on Mac OS X 15.5 (aarch64)
01:34:15.704 [main] INFO  org.cryptomator.ipc.Server - Spawning IPC server listening on socket /Users/USER_NAME/Library/Application Support/Cryptomator/ipc.socket
01:34:15.931 [JavaFX Application Thread] INFO  o.cryptomator.launcher.Cryptomator - JavaFX runtime started after 1114ms
01:34:18.102 [App Scheduled Executor 02] INFO  o.c.common.settings.SettingsProvider - Settings saved to /Users/USER_NAME/Library/Application Support/Cryptomator/settings.json
01:34:22.911 [JavaFX Application Thread] INFO  o.cryptomator.ui.fxapp.UpdateChecker - Current version: 1.17.0, latest version: 1.17.0
01:34:23.918 [App Scheduled Executor 02] INFO  o.c.common.settings.SettingsProvider - Settings saved to /Users/USER_NAME/Library/Application Support/Cryptomator/settings.json
01:35:03.918 [JavaFX Application Thread] INFO  o.c.ui.unlock.UnlockWorkflow - Unlock of 'VAULT_NAME' failed.
01:35:03.919 [JavaFX Application Thread] ERROR o.c.ui.unlock.UnlockWorkflow - Unlock failed for technical reasons.
org.cryptomator.integrations.mount.MountFailedException: org.cryptomator.jfuse.api.FuseMountFailedException: fuse_loop() returned prematurely with non-zero exit code -1
	at [email protected]/org.cryptomator.frontend.fuse.mount.FuseTMountProvider$FuseTMountBuilder.mount(FuseTMountProvider.java:133)
	at [email protected]/org.cryptomator.common.mount.Mounter.mount(Mounter.java:172)
	at [email protected]/org.cryptomator.common.vaults.Vault.unlock(Vault.java:179)
	at [email protected]/org.cryptomator.ui.keyloading.KeyLoadingStrategy.use(KeyLoadingStrategy.java:108)
	at [email protected]/org.cryptomator.ui.unlock.UnlockWorkflow.call(UnlockWorkflow.java:82)
	at [email protected]/org.cryptomator.ui.unlock.UnlockWorkflow.call(UnlockWorkflow.java:37)
	at [email protected]/javafx.concurrent.Task$TaskCallable.call(Unknown Source)
	at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
	at java.base/java.util.concurrent.CompletableFuture$UniAccept.tryFire(Unknown Source)
	at java.base/java.util.concurrent.CompletableFuture$Completion.run(Unknown Source)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.base/java.lang.Thread.run(Unknown Source)
Caused by: org.cryptomator.jfuse.api.FuseMountFailedException: fuse_loop() returned prematurely with non-zero exit code -1
	at [email protected]/org.cryptomator.jfuse.api.Fuse.mount(Fuse.java:130)
	at [email protected]/org.cryptomator.frontend.fuse.mount.FuseTMountProvider$FuseTMountBuilder.mount(FuseTMountProvider.java:130)
	... 12 common frames omitted
01:36:50.745 [App Scheduled Executor 01] INFO  o.c.common.settings.SettingsProvider - Settings saved to /Users/USER_NAME/Library/Application Support/Cryptomator/settings.json
01:36:51.913 [App Scheduled Executor 01] INFO  o.c.common.settings.SettingsProvider - Settings saved to /Users/USER_NAME/Library/Application Support/Cryptomator/settings.json
01:36:56.986 [App Scheduled Executor 01] INFO  o.c.common.settings.SettingsProvider - Settings saved to /Users/USER_NAME/Library/Application Support/Cryptomator/settings.json
01:37:05.458 [JavaFX Application Thread] INFO  o.cryptomator.ui.fxapp.UpdateChecker - Current version: 1.17.0, latest version: 1.17.0
01:37:06.465 [App Scheduled Executor 01] INFO  o.c.common.settings.SettingsProvider - Settings saved to /Users/USER_NAME/Library/Application Support/Cryptomator/settings.json
01:37:10.791 [App Scheduled Executor 01] INFO  o.c.common.settings.SettingsProvider - Settings saved to /Users/USER_NAME/Library/Application Support/Cryptomator/settings.json
01:37:13.033 [App Scheduled Executor 02] INFO  o.c.common.settings.SettingsProvider - Settings saved to /Users/USER_NAME/Library/Application Support/Cryptomator/settings.json
01:40:37.357 [App Scheduled Executor 02] INFO  o.c.common.settings.SettingsProvider - Settings saved to /Users/USER_NAME/Library/Application Support/Cryptomator/settings.json
01:40:42.884 [App Background Thread 005] WARN  org.cryptomator.common.vaults.Vault - Unable to add Vault to quick access area: Desired implementation not available.
01:40:42.885 [JavaFX Application Thread] INFO  o.c.ui.unlock.UnlockWorkflow - Unlock of 'VAULT_NAME' succeeded.
01:41:30.291 [App Scheduled Executor 01] INFO  o.c.common.settings.SettingsProvider - Settings saved to /Users/USER_NAME/Library/Application Support/Cryptomator/settings.json

Cuberick-Orion · 2025-09-30T07:30:57Z

Cuberick-Orion
Sep 30, 2025

Restarting the macOS solved the issue.

0 replies

deFractal · 2025-11-15T03:12:32Z

deFractal
Nov 15, 2025

This bug persists in Cryptomator 1.18.0 with FUSE-T 1.0.49 on macOS Sequoia 15.7.2.

I found another potential workaround, described below, as the above recommended ones didn't work in my case.

But first, some logs:

Error Code 09TB:8LNC:8MQR
org.cryptomator.integrations.mount.MountFailedException: org.cryptomator.jfuse.api.FuseMountFailedException: fuse_loop() returned prematurely with non-zero exit code -1
	at [email protected]/org.cryptomator.frontend.fuse.mount.FuseTMountProvider$FuseTMountBuilder.mount(FuseTMountProvider.java:133)
	at [email protected]/org.cryptomator.common.mount.Mounter.mount(Mounter.java:172)
	at [email protected]/org.cryptomator.common.vaults.Vault.unlock(Vault.java:179)
	at [email protected]/org.cryptomator.ui.keyloading.KeyLoadingStrategy.use(KeyLoadingStrategy.java:109)
	at [email protected]/org.cryptomator.ui.unlock.UnlockWorkflow.call(UnlockWorkflow.java:82)
	at [email protected]/org.cryptomator.ui.unlock.UnlockWorkflow.call(UnlockWorkflow.java:37)
	at javafx.graphics@25/javafx.concurrent.Task$TaskCallable.call(Unknown Source)
	at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
	at java.base/java.util.concurrent.CompletableFuture$UniAccept.tryFire(Unknown Source)
	at java.base/java.util.concurrent.CompletableFuture$Completion.run(Unknown Source)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.base/java.lang.Thread.run(Unknown Source)
Caused by: org.cryptomator.jfuse.api.FuseMountFailedException: fuse_loop() returned prematurely with non-zero exit code -1
	at [email protected]/org.cryptomator.jfuse.api.Fuse.mount(Fuse.java:130)
	at [email protected]/org.cryptomator.frontend.fuse.mount.FuseTMountProvider$FuseTMountBuilder.mount(FuseTMountProvider.java:130)
	... 12 more

Concurrent with the failure to mount the volume, ~/Library/Logs/fuse-t/fuse-t.log gets appended with:

time="2025-11-14T19:25:58-08:00" level=info msg="comm socket: 64"
time="2025-11-14T19:25:58-08:00" level=info msg="montor socket: 66"
time="2025-11-14T19:25:58-08:00" level=info msg="Server version 1.0.49 (70ae0b15a0f0c31681bfa10c133c87886dfcc6e7) running at [::1]:52200"
time="2025-11-14T19:25:58-08:00" level=info msg="Mounting: /Users/USERNAME/Library/Application Support/Cryptomator/mnt/VAULT NAME"
time="2025-11-14T19:25:58-08:00" level=info msg="mount [-o noauto,nostreams -t smbfs //Guest@fuse-t._smb._tcp.local/VAULT%20NAME /Users/USERNAME/Library/Application Support/Cryptomator/mnt/VAULT NAME]"
time="2025-11-14T19:26:28-08:00" level=error msg="exit status 68"
time="2025-11-14T19:26:28-08:00" level=warning msg="receiveRequest error: read unix ->: use of closed network connection"
time="2025-11-14T19:27:10-08:00" level=info msg="comm socket: 65"
time="2025-11-14T19:27:10-08:00" level=info msg="montor socket: 69"
time="2025-11-14T19:27:10-08:00" level=warning msg="Failed to listen: 52200"
time="2025-11-14T19:27:10-08:00" level=info msg="Server version 1.0.49 (70ae0b15a0f0c31681bfa10c133c87886dfcc6e7) running at [::1]:52201"
time="2025-11-14T19:27:10-08:00" level=info msg="Mounting: /Users/USERNAME/Library/Application Support/Cryptomator/mnt/VAULT NAME"
time="2025-11-14T19:27:10-08:00" level=info msg="mount [-o noauto,nostreams -t smbfs //Guest@fuse-t-1._smb._tcp.local/VAULT%20NAME /Users/USERNAME/Library/Application Support/Cryptomator/mnt/VAULT NAME]"
time="2025-11-14T19:27:12-08:00" level=error msg="ioctl: code 1310840"
time="2025-11-14T19:27:12-08:00" level=error msg=Lock
time="2025-11-14T19:27:12-08:00" level=error msg=Lock
time="2025-11-14T19:27:12-08:00" level=error msg=Lock
time="2025-11-14T19:27:12-08:00" level=error msg=Lock
time="2025-11-14T19:27:12-08:00" level=error msg=Lock
time="2025-11-14T19:27:12-08:00" level=error msg=Lock
time="2025-11-14T19:27:12-08:00" level=error msg=Lock
time="2025-11-14T19:27:12-08:00" level=error msg=Lock
time="2025-11-14T19:27:15-08:00" level=error msg=Lock
time="2025-11-14T19:27:15-08:00" level=error msg=Lock
time="2025-11-14T19:27:15-08:00" level=error msg=Lock
time="2025-11-14T19:27:15-08:00" level=error msg=Lock
time="2025-11-14T19:27:15-08:00" level=error msg=Lock
time="2025-11-14T19:27:15-08:00" level=error msg=Lock
time="2025-11-14T19:27:15-08:00" level=error msg=Lock
time="2025-11-14T19:27:15-08:00" level=error msg=Lock
time="2025-11-14T19:27:15-08:00" level=error msg=Lock
time="2025-11-14T19:27:15-08:00" level=error msg=Lock
time="2025-11-14T19:27:15-08:00" level=error msg=Lock
time="2025-11-14T19:27:15-08:00" level=error msg=Lock
time="2025-11-14T19:27:15-08:00" level=error msg=Lock
time="2025-11-14T19:27:15-08:00" level=error msg=Lock
time="2025-11-14T19:27:15-08:00" level=error msg=Lock
time="2025-11-14T19:27:15-08:00" level=error msg=Lock
time="2025-11-14T19:27:15-08:00" level=error msg=Lock
time="2025-11-14T19:27:15-08:00" level=error msg=Lock
time="2025-11-14T19:27:15-08:00" level=error msg=Lock
time="2025-11-14T19:27:15-08:00" level=error msg=Lock
time="2025-11-14T19:27:15-08:00" level=error msg=Lock
time="2025-11-14T19:27:15-08:00" level=error msg=Lock
time="2025-11-14T19:27:16-08:00" level=error msg=Lock
time="2025-11-14T19:27:16-08:00" level=error msg=Lock
time="2025-11-14T19:27:16-08:00" level=error msg=Lock
time="2025-11-14T19:27:16-08:00" level=error msg=Lock
time="2025-11-14T19:27:16-08:00" level=error msg=Lock
time="2025-11-14T19:27:16-08:00" level=error msg=Lock
time="2025-11-14T19:27:16-08:00" level=error msg=Lock
time="2025-11-14T19:27:16-08:00" level=error msg=Lock
time="2025-11-14T19:27:16-08:00" level=error msg=Lock
time="2025-11-14T19:27:16-08:00" level=error msg=Lock
time="2025-11-14T19:27:16-08:00" level=error msg=Lock
time="2025-11-14T19:27:16-08:00" level=error msg=Lock
time="2025-11-14T19:27:16-08:00" level=error msg=Lock
time="2025-11-14T19:27:16-08:00" level=error msg=Lock
time="2025-11-14T19:27:16-08:00" level=error msg=Lock
time="2025-11-14T19:27:16-08:00" level=error msg=Lock
time="2025-11-14T19:27:16-08:00" level=error msg=Lock
time="2025-11-14T19:27:16-08:00" level=error msg=Lock
time="2025-11-14T19:27:21-08:00" level=error msg=Lock
time="2025-11-14T19:27:21-08:00" level=error msg=Lock
time="2025-11-14T19:27:21-08:00" level=error msg=Lock
time="2025-11-14T19:27:21-08:00" level=error msg=Lock
time="2025-11-14T19:27:21-08:00" level=error msg=Lock
time="2025-11-14T19:27:21-08:00" level=error msg=Lock
time="2025-11-14T19:27:21-08:00" level=error msg=Lock
time="2025-11-14T19:27:21-08:00" level=error msg=Lock
time="2025-11-14T19:27:54-08:00" level=error msg="error: connection error: EOF"
time="2025-11-14T19:27:54-08:00" level=info msg="Unmounting: /Users/USERNAME/Library/Application Support/Cryptomator/mnt/VAULT NAME"
time="2025-11-14T19:27:54-08:00" level=info msg="Parent process has died"
time="2025-11-14T19:27:54-08:00" level=info msg="unmount [-f /Users/USERNAME/Library/Application Support/Cryptomator/mnt/VAULT NAME]"
time="2025-11-14T19:27:54-08:00" level=info msg="unmount [-f /Users/USERNAME/Library/Application Support/Cryptomator/mnt/VAULT NAME]"
time="2025-11-14T19:27:54-08:00" level=error msg="exit status 1"
time="2025-11-14T19:27:54-08:00" level=error msg="exit status 1"

If I re-attempt to mount the vault, thousands of lines are appended to the log at the rate of more than ten per second, mostly just repeating around 108 – 144 lines ending msg=Lock per line ending msg="sendRequest error: write unix ->: use of closed network connection".

I don't know enough about SMB to be sure whether it's significant, but in SMB, ioctl code 1310840, or 0x140078, corresponds to FSCTL_SRV_REQUEST_RESUME_KEY.

I finally got this working, at least once. What didn't work:

removing and reinstalling Cryptomator,
removing and reinstalling FUSE-T,
explicitly setting volume type to "FUSE-T Experimental" (as opposed to Default),
explicitly setting the full mount directory path (as opposed automatically),
removing and re-adding the vault,
restarting the Mac, or
mounting and altering the volume on Cryptomator for Windows, unmounting it, then attempting to mount it again on Cryptomator for Mac.

Notably, running a vault health check shows no problems with the vault.

What did work:

reverting the full mount directory path to automatic, and
deleting the (empty) mountpoint folder, then mounting the vault again.

However, it is then necessary to delete the empty mountpoint folder before mounting the vault, each time I mount the vault.

@skymatic Is there any more information necessary before turning this discussion into an issue? Please let us know what else might be helpful to find the cause of the bug.

@macos-fuse-t Might this be a bug in FUSE-T, not Cryptomator?

0 replies

mipurp · 2025-11-21T07:38:49Z

mipurp
Nov 21, 2025

Cryptomator works on my Mac with OS 26.1 and an Intel processor (Cryptomator: 1.18.0 / macFUSE 5.1.2).

For the past 4 days, it has not been working on my other Mac with OS 26.1 and an M4 processor (Cryptomator: 1.18.0 /
FUSE-T 1.0.49).

Reinstalling Cryptomator and Fuse-T, as well as remounting the vault, did not work for me either.

A workaround that works with a lot of patience is as follows:

Start Cryptomator
Change the virtual drive in the Cryptomator settings and in the vault options to WebDAV
Exit Cryptomator
Open Cryptomator and connect to the vault
Change the virtual drive in the Cryptomator settings and in the vault options to Fuse-T (Experimental)
Exit Cryptomator
Open Cryptomator and connect the vault

This isn't really a solution, because I have to repeat the whole workaround the next day. I've had this problem repeatedly in the past, especially after macOS updates.

Since I rely on my data, I probably won't continue using Cryptomator. It's too unreliable for me.

0 replies

caiiiou · 2025-11-24T07:07:00Z

caiiiou
Nov 24, 2025

I deleted the homebrew version of fuse-t and installed the package from the fuse site directly and it worked. I suspect that is the issue but it might not be.

2 replies

mipurp Nov 25, 2025

Thank you! I did the same and now everything is working perfectly again.

yondelev Dec 11, 2025

I've never used the Homebrew version, and I'm still having this issue with the latest software (Cryptomator 1.18.0, FUSE-T 1.0.49, MacOS Tahoe 26.1). Setting both the Cryptomator default volume type and vault volume type to FUSE-T (from automatic), as suggested by someone earlier, seemed to fix it for a while, but now I'm sometimes having the issue again when I try to unlock a vault (both automatically when Cryptomator starts and manually). The only other thing I changed was storing passwords with Touch ID instead of Keychain, and the issue seemed to start happening again immediately after, but I can't consistently reproduce the issue, so I'm unsure if it's related.

Error Code 09TB:8LNC:8MQR
org.cryptomator.integrations.mount.MountFailedException: org.cryptomator.jfuse.api.FuseMountFailedException: fuse_loop() returned prematurely with non-zero exit code -1
	at [email protected]/org.cryptomator.frontend.fuse.mount.FuseTMountProvider$FuseTMountBuilder.mount(FuseTMountProvider.java:133)
	at [email protected]/org.cryptomator.common.mount.Mounter.mount(Mounter.java:172)
	at [email protected]/org.cryptomator.common.vaults.Vault.unlock(Vault.java:179)
	at [email protected]/org.cryptomator.ui.keyloading.KeyLoadingStrategy.use(KeyLoadingStrategy.java:109)
	at [email protected]/org.cryptomator.ui.unlock.UnlockWorkflow.call(UnlockWorkflow.java:82)
	at [email protected]/org.cryptomator.ui.unlock.UnlockWorkflow.call(UnlockWorkflow.java:37)
	at javafx.graphics@25/javafx.concurrent.Task$TaskCallable.call(Unknown Source)
	at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
	at java.base/java.util.concurrent.CompletableFuture$UniAccept.tryFire(Unknown Source)
	at java.base/java.util.concurrent.CompletableFuture$Completion.run(Unknown Source)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.base/java.lang.Thread.run(Unknown Source)
Caused by: org.cryptomator.jfuse.api.FuseMountFailedException: fuse_loop() returned prematurely with non-zero exit code -1
	at [email protected]/org.cryptomator.jfuse.api.Fuse.mount(Fuse.java:130)
	at [email protected]/org.cryptomator.frontend.fuse.mount.FuseTMountProvider$FuseTMountBuilder.mount(FuseTMountProvider.java:130)
	... 12 more

Uh oh!

Error 09TB:8LNC:8MQR #3607

Uh oh!

Uh oh!

Replies: 12 comments · 8 replies

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

overheadhunter Apr 11, 2025 Maintainer

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Replies: 12 comments 8 replies

overheadhunter Apr 11, 2025
Maintainer