Explorer hanging for long periods of time with no drives displaying

Please agree to the following

• I have searched existing issues for duplicates
• I agree to follow this project's Code of Conduct

Summary

Explorer appears to hang for long periods of time when cryptomator is running

What software is involved?

• Operating System: Windows 11 (BitLocker + EUFI secure boot enabled)
• Cryptomator: 1.8.0 (msi-4440)
• Explorer Window

I have a total of 8 crypto drives, 3 are unlocked (those 3 are located within OneDrive which is on a local HD). OneDrive is set to download + keep ALL files locally. If I load explorer while Cryptomator is running, the side panel "spin" for a long long time before any left panel drives show up and it takes a very long time for explorer to eventually respond. If I quit Cryptomator then explorer goes back to normal fast behaviour and everything works as expected.

I enabled debug logging and I noticed that Cryptomator is scanning the directory structures of my system. I only use the Windows system virus scanner, and I disabled that as well as the indexer yet the files still appear to being scanned (according to the debug log). I'm not sure if this is just an automatic thing that happens internet to Cryptomator or not as I can't find any process outside of Cryptomator that is accessing it. I'm not even certain if the scanning is related to the explorer hanging.

OneCommander (alternative to explorer) will launch fast and all drives are accessible.

Any ideas as to what's wrong?

Volume Type

None

Steps to Reproduce

1. Launch Cryptomator
2. Unlock at least one drive (when all are locked issue is not present)
3. Launch Windows Explorer

Expected Behavior

Instantly open (as it normally would when Cryptomator is closed)

Actual Behavior

Wait and wait and wait until eventually it displays the drives/folders.

Reproducibility

Always

Relevant Log Output

https://gist.githubusercontent.com/robin-raymond/b463f2d65f33c4e348900db7b167c9cb/raw/663887773b01fdcfca3a4fe00b57afd3ba0e3150/cyrptomator.log

(had to create a gist as log made issue too long)

Anything else?

No response