MS Office creates tmp-files on cryptomator vault

[pizbuin]

Having version 1.4.15 installed for a while on different PCs/Windows versions I see the following problem:

Windows 10: MS Office 2010 creates tmp-files of opened documents, spreadsheets, presentations, and these files do not disappear after closing the application. So tmp-files are piling up in the working directory where the office file(s) are opened. I have to delete them manually.

Windows 7: Not seen the problem above but I can’t open and modify a Kee pass file anymore ! I have to copy the file to a local directory where I may modify it and then I can copy it back to the cryptomator vault. Kee Pass 1.x claims about missing permissions to store the file after modification.

Any ideas on these two issues ?

I’ve seen a similar topic here but I think it’s not the same problem. I’m allowed to store the office files after modification.

[Michael]

Office issue:
Please check and update your dokany version (I guess you are using dokany)

See here

OneDrive temp files appear and remain when working on MS Office documents

Whenever I work on MS Office documents within the Cryptomator storage (that is synchronized with OneDrive) temp files appear in the folder and remain there even after closing the corresponding MS Office file. In order to get rid of these temp files I have to delete them manually. This behavior started with version 1.4.11. If I roll the software back to 1.4.10 everything works as expected again. The attached screenshot should clarify what these temp files are that I’m talking about. P.S. The sys…

Keepass issue:
Let me stress that there is no additional security by storing your already encrypted keepass file in an encrypted Cryptomator vault. So there is no need to store a keepass database in a Cryptomator vault.
But, your issue might a write protection.
See here

Windows: How to remove write protection from a file inside a vault

Hey Folks, since i read recently several reports about problems with write protected files, I’ll post a short guide how to “unprotect” them. First of all: This is a known issue (see bug report #776) and only related to Dokany. If you are using WinFSP, this guide does not change anything. So, let’s assume you have created a vault myVault and it is stored under the path D:\path\to\myVault ( NOT the location of your unlocked vault). Open a terminal Change to the encrypted vault: cd "D:\path\to…