Michael
February 22, 2019, 11:29am
2
2 Suggestions:
switch the adapter to webdav and try again.
use Cyberduck to access your vault online directly. Then delete the files/folders that are corrupt. After that, start the dropbox sync. After the sync the deleted files/folder should be gone in your local vault
Fyi:
opened 05:44AM - 25 Nov 18 UTC
closed 10:25AM - 12 Apr 19 UTC
type:bug
os:windows
state:has-workaround
misc:filesystem
## Issue Checklist
Before creating a new issue make sure that you
- searched… existing (and closed) issues: https://github.com/cryptomator/cryptomator/issues
- searched the knowledge base: https://community.cryptomator.org/c/kb
- have read the support guide: https://github.com/cryptomator/cryptomator/blob/develop/SUPPORT.md
- have read the contribution guide: https://github.com/cryptomator/cryptomator/blob/develop/.github/CONTRIBUTING.md
- have read the code of conduct: https://github.com/cryptomator/cryptomator/blob/develop/.github/CODE_OF_CONDUCT.md
## Basic Info
I'm using Windows Pro 64 bit in version: 1803
I'm running Cryptomator in version: 1.4.0
(You can check the version in the Cryptomator settings.)
## Description
After using FreeFileSync to sync files from hard disk to the Cryptomator vault, I saw that two temporary FFS files couldn't be deleted from the vault. i.e. AJPI_2016.qbw.56f1.ffs_tmp. When trying to manually delete these files from File Explorer, they disappear then reappear when the screen is refreshed. I tried closing the vault and re-opening without success. I then tried to delete the whole containing folder, but that also reappears. I now have six temporary files because I retried syncing several times.
The log is showing i.e. getFileInformation(): Invalid handle to /Finance/Quickbooks/AJPI_2016.qbw.56f1.ffs_tmp.
I have also closed FreeFileSync completely and there is currently no syncing to a cloud service.
## Attachments (optional)
The log file has quite a lot in it just from the one delete action when in debug mode.
[cryptomator log delete issue 181125.txt](https://github.com/cryptomator/cryptomator/files/2612854/cryptomator.log.delete.issue.181125.txt)
and a thread from infeo how to deal with that:
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…