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
Describe the bug
Versions v1.10.2 to v1.11.0-beta.2 are apparently incompatible with Windows 11. Instead of showing mounted content, Windows Explorer asks for inserting drive.
I guess the problem is on Dokany side. beta.3 and beta.4, wich use Dokany v2.0.4.1000, mount encrypted folders, however they are affected with #155
To Reproduce
Steps to reproduce the behavior:
Create a new encrypted folder, provide drive and password.
Provide password to mount the folder.
Windows Explorer window appears together with message: 'Please insert a disk into Removable Disk (X:)
Expected behavior
Windows Explorer window appears with mounted decrypted content (empty if exactly followed 'To Reproduce').
Desktop (please complete the following information):
OS: Windows 11 Pro 22H2, build 22621.1485, experience Windows Feature Experience Pack 1000.22639.1000.0
Processor architecture: x64
Encfs4win version: v1.10.2 and v1.11.0-beta.2
Dokany version: v1.3.1.1000 (modern)
The text was updated successfully, but these errors were encountered:
I did not see this problem with a new install on Win11x64.
I tried with the v1.11.0-beta.4 and it works fine (except the bad file sizes/dates bug)
v1.10.2 is what I'm using now and works. it's using Dokany v131
Describe the bug
Versions v1.10.2 to v1.11.0-beta.2 are apparently incompatible with Windows 11. Instead of showing mounted content, Windows Explorer asks for inserting drive.
I guess the problem is on Dokany side. beta.3 and beta.4, wich use Dokany v2.0.4.1000, mount encrypted folders, however they are affected with #155
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Windows Explorer window appears with mounted decrypted content (empty if exactly followed 'To Reproduce').
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: