Vault Empty After Updating to Cryptomator 1.19.2 (Mac)

Help Desktop App
1

Hi all,

I’m hoping someone can help.

I’ve just updated to Cryptomator 1.19.2 on my Mac (running Tahoe 26.4.1). During the update, it mentioned a change in file locations, which didn’t seem like a big issue since I still have all my files.

However, when I unlock/decrypt my vault, it appears empty. I haven’t made any major changes to my Mac, and all my encrypted Cryptomator files are still there.

I should add that I’m seeing this error referenced here: Error 91OE:Q3PE:8MFL · cryptomator/cryptomator · Discussion #3969 · GitHub . My vault is stored on iCloud.

The symptoms are:

  • I navigate to the correct vault folder

  • Enter my password

  • Then I get the error mentioned in the GitHub post, and the vault shows as empty

Also worth noting: I can access and decrypt my files on my iPhone via iCloud with no issues, so the data itself seems intact.

Does anyone know what I might be missing or what could have caused this?

Thanks in advance.

–

Just to update on this (4th May 2026)

I’ve been looking further into this and wanted to share some additional findings.

I understand that using FUSE on macOS is also recommended, and I will consider this, but my setup has been working fine without it up until now.

From what I can tell, my setup is valid, but it depends on three layers all behaving nicely:

  1. Cryptomator

  2. macOS (Tahoe 26.4.1 in my case)

  3. iCloud file handling

It seems like one of these has changed, most likely iCloud’s file streaming or macOS filesystem behaviour.

Additional details from my testing:

  • I can confirm the vault works perfectly when copied locally to my desktop on macOS

  • I can also access and decrypt all files on my iPhone via iCloud with no issues

  • The encrypted files are definitely present in the vault (I can see them in Finder)

This seems to point to an issue with iCloud/macOS rather than the vault itself.

When opening the vault directly from iCloud on my Mac, it appears empty and I see repeated errors in the logs:

PROPFIND request failed, returning 500. Reason: java.io.UncheckedIOException

From testing, this looks like it may be related to how iCloud is handling file availability (possibly not fully downloaded) or a WebDAV mount issue introduced in recent versions (Cryptomator 1.19.2 or macOS Tahoe 26.4.1).

So far:

  • Local copy of the vault > works

  • iCloud-hosted vault on Mac > shows empty + errors

  • iPhone via iCloud > works

Has anyone else seen this behaviour recently, or found a reliable fix?

Thanks again for any help.

2

Same problem on Windows, all directories are there but no file left, it is scary…

3

Hello,

Thanks for sharing, that’s really interesting that you’re seeing the same issue on Windows 11.

Are you syncing your vault via OneDrive? It would be helpful to confirm, as this might point to a broader cloud-sync related issue rather than something specific to macOS or iCloud.

Are you also seeing similar errors in your logs (e.g. PROPFIND / I/O related errors)?

It does seem like this kind of setup depends on three layers all behaving properly:

  1. Cryptomator
  2. The operating system (macOS Tahoe / Windows 11)
  3. The cloud provider (iCloud, OneDrive, Google Drive, etc.)

It looks like something in that chain has changed, possibly how cloud providers handle file streaming/on-demand files, or how the OS interacts with them.

At the moment, I’m not entirely confident using Cryptomator with cloud storage in this way, especially across different providers.

I know using FUSE is often recommended (especially on macOS), but I’m not particularly keen on introducing that into my setup if it can be avoided, since things were working fine without it previously.

Would be good to compare setups and see what’s common.

Thanks

4

Personaly, I use the last version of cryptomator (v.1.19.2) on Windows 11 on local drive (no cloud)