Related to this question but not identical.
C:\Folder\Symlink\ is a symlink pointing to
Deleting a file through
C:\Folder\Symlink\* bypasses the Recycle Bin, even though both
E: have the Recycle Bin enabled.
This only seems to happen with cross-volume symlinks.
- Using the above symlink structure, create a file
C:\Folder\Symlink\somefile.txtby using either the Delete key or right-click > Delete.
- The prompt comes up for immediate deletion, instead of offering to send the file to the Recycle Bin.
Can anyone else reproduce this, and is there a fix?
Did some more digging and was able to further isolate the issue.
In the list below,
Denied specifies a folder that has access permissions revoked for the current user. All other folders have Full Control. Permissions are not inherited. Each folder has explicit permissions.
E:\Denied\Denied\Target\= Recycle Bin? NO
E:\Allowed\Denied\Target\= Recycle Bin? YES
E:\Allowed\Denied\Denied\Target\= Recycle Bin? NO
E:\Allowed\Allowed\Denied\Target\= Recycle Bin? YES
E:\Denied\Allowed\Denied\Target\= Recycle Bin? YES
E:\Denied\Denied\Allowed\Target\= Recycle Bin? NO
E:\Denied\Denied\Denied\Target\= Recycle Bin? NO
Adding at least two
Denied folders in a row introduces this issue. It seems the shell is not able to see through through more than one consecutive unreadable folder?