Replies: 2 comments 3 replies
|
Hi @dkocher, is there any chance to get some short-term feedback, please? This bug is really annoying, and I can't believe that I'm the only one experiencing this. I bought Mountain Duck specifically for this functionality, since Cryptomator's own app has been prone to crashes. However, losing information or not being able to access it anymore is killing my primary use case. |
3 replies
|
I will see that we can provide a fix for the next bugfix update and keep this thread updated. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I'd like to re-open issue #17966 or a new one covering the following issues:
OS: Windows 11 25H2 x64 (latest patches)
Settings in Mountain Duck: See screenshot

I've been experiencing the same behavior as in #17966 with Mountain Duck on my local Cryptomator vault:
I have not tried to delete something for hopefully obvious reasons.
I have this issue with both my existing Cryptomator vault and also one created from scratch (using latest Cryptomator). No difference.
It all started with Mountain Duck version 5.2.1 release, and it's still persistent with the latest 5.3.0 release. The last version which has worked for me without issues was 5.2.0.
I assume something has been broken between 5.2.0 and 5.2.1 which I had hoped to be fixed in 5.3.0, but it hasn't (so far).
Stack Trace information:
All reactions