Thank you very much for all these information.
In fact, I hade several vaults and some were not in a cloud but I have been using them for more than one year without any problem.
I was trying to open a portable KeyPass2 that was stored in this vault, but Windows 10 suddenly stopped recognizing some .exe files that were in the vault in question. I am sure I didn’t change anything on my system since the problem appeared. (Only Windows updates)
So when I try to open some files I get the above message and all the USB hardwares and my system freeze. Yes, I have a vault on an USB stick that am using for over a year like other vaults on the cloud.
I checked my system if I it was contaminated by any malware or a virus, it’s 100% clean ! Because of the “@” that clears the password I thought maybe I was infected. This is just crazy and if you are not able to reproduce the problem that makes me even more sceptical. Using 1.4.0-beta2 without knowing what causes all these bugs is a nosense, isn’t it ? P.S. Please keep in mind I built all my vaults using Cryptomator is 1.32 & 1.3.3. and that the passwords have created with those versions.
There is a conflict between Cryptomator and something on my machine. But what ? This is the question…
EDIT : I wanted to create a new vault with Cryptomator 1.4.0-beta2 and while typing the password, including a character “@”, Cryptomator had again a very strange behaviour as it cleared the field. This makes me totally crazy !
It seems I have no other choise to grudgingly accept that I have no other choice than quitting this software,