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
{{ message }}
Repository navigation
mirror.exe - Access denied if mounted without mount manager #1337
Hi there, I'm developing with dokany and met this issue which I am seeking advice in finding the root cause.
I have been trying mirror.exe with mounting to another folder: .\mirror.exe /r .\target\ /l "D:\dokany\x64\Release\dest\" /e /d /s
However, every time I try to open the file inside, it always return access denied error. By chance, I found enabling the mount manager will instantly fix the issue.
Now I'm really curious about the actual root cause and I have tried looking at the logs for a while now but totally got no clue. Here's the log I capture from mirror.exe output: log.txt
I do have a theory that since my dest is a reparse point to a device not registered by mount manager, so Windows block accessing the file inside?
Can I ask for tips with this? Thank you in advance
Hi thank you @The009 for your tip, but unfortunately, I still can't access while running mirror on Administrator console without setting mount manager. At this point I'm looking into the code. I think without mount manager, dokany.dll creates a reparse point to the a device owned by the driver. Perhaps the reparse point is owned by something at kernel level, blocking me a user from accessing it?
Activity
The009 commentedon Aug 7, 2026
Windows requires elevated privileges to do this. Make sure you run your application as Administrator :)
DongKat commentedon Aug 10, 2026
Hi thank you @The009 for your tip, but unfortunately, I still can't access while running mirror on Administrator console without setting mount manager. At this point I'm looking into the code. I think without mount manager, dokany.dll creates a reparse point to the a device owned by the driver. Perhaps the reparse point is owned by something at kernel level, blocking me a user from accessing it?
The009 commentedon Aug 18, 2026
Try absolute paths.
DongKat commentedon Aug 24, 2026
I tried the second suggestion as well, but unfortunately I’m still seeing the same issue. Do you have any other suggestions for what I could check?