You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But entering any OneDrive folder is extremely slow (like 3-5 seconds wait time to go from folder to folder) and in Cryptomator it's faster but still 2-3 seconds to go from folder to folder or to refresh any preview thumbnails or to scroll Windows Explorer.
I'm using pretty much one of the fastest NVMe in existence (ESR01TBMFCT-E8GBTOEM4) and without OneDrive or Cryptomator everything works fine.
I have about 250 GB in OneDrive (about 100,000 files) and about 60 GB in Cryptomator.
One video file seems to be somehow corrupted and clicking "Delete" key doesn't do anything.
After about 5 minutes it finally reacted with this (it's that laggy and slow that it literally takes 5 minutes for these popups to appear):
I think to solve this you need to work with Microsoft Windows Explorer team, OneDrive team and Cryptomator team. Because it's all connected and crappy. Also, when I enable "Windows Search Indexer" (I had to disable this yesterday to drastically improve performance) then it hangs my Windows Explorer forever. I have to restart computer to fix this because ending this process in Ctrl + Alt + Del doesn't help, it returns and makes 1 core of processor be at 100% load all the time and Windows Explorer completely doesn't work.
From other software that can be interfering I have PowerToys (however, I disabled all modules except file handle, alt + space search and image resizer). Other than that I don't have any software, it's a pretty clean computer.
Expected Behavior
To work.
Actual Behavior
Doesn't work.
Reproducibility
Always
Relevant Log Output
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered:
Since I have at the moment a direct comparison to the good old boxcryptor classic with the same data inside:
every action within cryptomator is much much slower. Even simple things within the explorer like file sorting within a sub folder by name, date...
Windows 11
cryptomator 1.10 and same in 1.11
winsfsp (local)
encrypted folder size: some tens of GB
Dropbox
NVMe SSD
fast notebook CPU
Please agree to the following
Summary
Volume is very slow
What software is involved?
Volume Type
WinFsp (Local Drive)
Steps to Reproduce
I don't know what are steps to reproduce.
But entering any OneDrive folder is extremely slow (like 3-5 seconds wait time to go from folder to folder) and in Cryptomator it's faster but still 2-3 seconds to go from folder to folder or to refresh any preview thumbnails or to scroll Windows Explorer.
I'm using pretty much one of the fastest NVMe in existence (ESR01TBMFCT-E8GBTOEM4) and without OneDrive or Cryptomator everything works fine.
I have about 250 GB in OneDrive (about 100,000 files) and about 60 GB in Cryptomator.
One video file seems to be somehow corrupted and clicking "Delete" key doesn't do anything.
After about 5 minutes it finally reacted with this (it's that laggy and slow that it literally takes 5 minutes for these popups to appear):
I think to solve this you need to work with Microsoft Windows Explorer team, OneDrive team and Cryptomator team. Because it's all connected and crappy. Also, when I enable "Windows Search Indexer" (I had to disable this yesterday to drastically improve performance) then it hangs my Windows Explorer forever. I have to restart computer to fix this because ending this process in Ctrl + Alt + Del doesn't help, it returns and makes 1 core of processor be at 100% load all the time and Windows Explorer completely doesn't work.
From other software that can be interfering I have PowerToys (however, I disabled all modules except file handle, alt + space search and image resizer). Other than that I don't have any software, it's a pretty clean computer.
Expected Behavior
To work.
Actual Behavior
Doesn't work.
Reproducibility
Always
Relevant Log Output
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: