-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't recover files to network drives. #711
Comments
What have you configured as the recovery fodler? |
I see, the intended behavioure in such cases is to ask for a folder to recover to, |
Hi David, the recovery function is asking for a folder to recover to. This behaviour is totally fine, but it would be great if the recovery path would be set to the actual network share. So it is okay, that it asks for the recovery location, but the prefilled recovery location does not represent the actual network share, but a location on the C: drive. Would it be possible, that the prefilled recovery location is set to the network drive, so that I just could click on recover and the file would be saved to the location I selected in the sandbox application (in this case Firefox)? I also attached a screencast of the current behaviour, probably this helps. 2021-04-05_15h58_52.mp4As you can see, I select the network drive (X:) as location to save to, Sandboxie then opens the recovery dialog, which is prefilled with \device\mup\NAME_OF_SHARE\PATH_TO_FILE. As a result, the file is saved to C: instead of the network share. Intended would be that Sandboxie prefills the recovery path with X:\PATH_TO_FILE. Best regards, |
Hi,
every time I try to save and recover files to a network share, the files is not recovered to the network share itself, but to a destination beginning with \device\mup\NAME_OF_SHARE\FOLDER. The file then can be found under C:\device\mup\NAME_OF_SHARE\FOLDER but not on the share itself.
Please also see the screenshot attached:
Is this a misconfiguration on my side?
Best,
Tom
The text was updated successfully, but these errors were encountered: