Recycle bin on substed drives

I've created a substed drive on Windows 7. When I delete a file, it doesn't go to the recycle bin, instead it is deleted permanently.

Recycle bin properties do not show this drive at all.

Any hack to send the files from substed drives to the recycle bin?

Solution 1:

1. Browse to C:\users\.
2. Right-click on one of the folders in this location (I chose saved games) and click properties.
3. Select the Location tab.
4. Click Move, browse to to root of the mapped drive, and click Select Folder.
5. When asked "move all content?" it's your decision, I prefer "No".

A $RECYCLE.BIN is created in the mapped drive and the drive is in the list shown in the properties of recyclebin.

If you move the location back to C:\users..., the mapped drive is removed from the list of drives that are covered by recycle bin. But the Recyclebin itself remains in the mapped drive. Allowing you to access deleted files from other drives, only.

Source: Microsoft

Solution 2:

According to various sources, the recycle bin indeed seems to not be available for that kind of drive.

Solution 3:

I faced the same issue and since I did not find any (for me) suitable solution, I began playing and trying around a little... I copied the $Recycle.bin folder from one drive to my substed drive and this seems to be an easy and working solution.

Solution 4:

There is an approach that does not require you to redirect one of the "Users" folders. I don't know why, but I was unable to get that approach to work, and I found it was really messy to undo.

This REG file is based on the information compiled from this TechNet article, which discusses how to enable the Recycle Bin. The example maps the virutal Q drive to folder "OneDrive - Test", and enables the Recycle Bin on the Q drive. Change the paths and name to suit your situation.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\DOS Devices]
"Q:"="\\??\\C:\\Users\\Tony\\OneDrive - Test"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FolderDescriptions\{9147E464-33A6-48E2-A3C9-361EFD417DEF}]
"RelativePath"="Q:\\"
"Category"=dword:00000004
"Name"="Q_Mapped_OneDrive"

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\BitBucket\KnownFolder\{9147E464-33A6-48E2-A3C9-361EFD417DEF}]
"MaxCapacity"=dword:0000c7eb
"NukeOnDelete"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Explorer\FolderDescriptions\{9147E464-33A6-48E2-A3C9-361EFD417DEF}]
"RelativePath"="Q:\\"
"Category"=dword:00000004
"Name"="Q_Mapped_OneDrive"

[HKEY_CURRENT_USER\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Explorer\BitBucket\KnownFolder\{9147E464-33A6-48E2-A3C9-361EFD417DEF}]
"MaxCapacity"=dword:0000c7eb
"NukeOnDelete"=dword:00000000

If you only have one such mapped drive, then you can get away with the GUID {9147E464-33A6-48E2-A3C9-361EFD417DEF}. If you have multiple mapped drives, then each should be matched to its own GUID from your favorite GUID generator.