Map a Local Folder to Windows RDP Without Sharing Your Entire Drive

Remote Desktop drive redirection lets a Windows session access files from the computer in front of you. That convenience also creates a trust boundary: applications on the remote desktop may be able to see redirected locations. Choose a minimum-access method for each transfer.
Pick the right transfer path
If you only need one document, a company-approved encrypted transfer service may be safer than leaving your local drive attached to a remote session. For ongoing work, create a dedicated transfer directory and keep private documents, browser exports, and credential databases elsewhere.
Enable redirection consciously
In classic Remote Desktop Connection, open Show Options > Local Resources > More under Local devices and resources. Select the devices or drives you actually need, then reconnect. The redirected resource should appear in the remote File Explorer when the Windows host and organization policies allow it. Other RDP clients may expose different controls.
Understand why it may be unavailable
Administrators can disable drive redirection through policy. If a drive does not appear, check client selection, reconnect, and ask the administrator whether the feature is intentionally restricted. Avoid random policy or registry edits that weaken a managed environment.
Safe file-transfer checklist
- Prepare a folder containing only the files required for the task.
- Open the remote session and confirm the correct target.
- Copy one harmless file first and check its destination permissions.
- Disable redirection afterward, and delete temporary copies according to policy.
Important: Redirection does not make an independent backup. Verify critical files by opening them at their final destination before removing originals.
FAQ: Does disconnecting delete files I copied?
No. Any independent copies you created on the remote host remain until removed by an authorized process.


