When I attempt to delete the old files I get an 0x8007045D error. However, one outdated version of x-file and one of y-file still remain in the old folder location on the laptop. When I went to the laptop to see what happened, one x-file and one y-file now correctly appears in the same folder the desktop moved the files to and with the correct modification date finally attached to the files. The phone and desktop however still correctly showed only one x-file and one y-file.įrom the desktop I decided to move x-file a y-file to a new folder. In other words, the laptop could push modifications made to x-file and y-file to the Cryptomator vault in pCloud, but the laptop is unable to pull modifications (made by the desktop or phone) from the vault in pCloud.Īs I started conducting experiments I noticed duplicates of x-file and y-file appear on the laptop, with the exact same filename and the exact same outdated modification date. I’m not sure if it is because x-file and y-file were open on my laptop when Windows decided to apply and update and reboot the laptop, or perhaps it was something else I’m not aware of.Ĭuriously however, if I modified x-file or y-file on my laptop, the files would get updated on the phone and desktop. One day I noticed that modifications I made to two particular files (we will call them x-file and y-file) on my desktop or phone would correctly update between the desktop and the phone, but they were not getting updated on my laptop. I have a FUSE Cryptomator vault in a pCloud drive that I access from 3 different devices (an Android phone phone, a Win 10 Pro desktop, and a Win 10 Pro laptop). A better error message would be great, if the app could identify the cause. Our staff won’t be as logical when creating folders, if it throws an error they will call me or start trying to create more new folders. I’d still like some input here from anyone that can clarify why the issue occurs. This evening all the files were in-sync and Dropbox was indicating ‘up to date’. The only difference I can see between doing it this evening and this afternoon was during the afternoon I had a number of large files (1.5GB approx.) syncing at the same time as the creation of the new folders, presummably creating a queue and blocking the I/O. I repeated this 3 times and renamed the folder again after it had just been renamed, each time it worked as desired and didn’t cause an issue. Just an update: This evening I created a New Folder and was able to rename it without the error appearing. Does anyone know if this issue can be resolved? The error reported above must have something to so with syncing to Dropbox. I was able to create the folder, overtype the default name New Folder and then rename it again without any errors. I created a vault on the local C drive, not synced with dropbox and the above mentioned behaviour did not occur. Is this normal behavour or is there something going wrong? I know the staff won’t understand this and it will find it frustrating. My assumption is the folder is locked while it is being encrypted, and maybe due to the syncing with Dropbox, but this is just a guess. If I wait for about a minute, I can then rename the folder. I have a shared folder on Dropbox synced to my PC (Windows 11), in that share I have created a vault and mapped it to the drive letter I: Each time I create a new folder under the I: drive Windows automatically names it ‘New Folder’, when I over type this, or try to rename it to something else I receive the error message 0x8007045D The request could not be performed because of an I/O Device error. I’m running into an issue and wondered if someone can let me know if this is normal behaviour, please? I’m new to Cryptomator and testing it for a possible rollout within our company.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |