> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/rdm/knowledge-base/troubleshooting-articles/microsoft-rdp-missing-mapped-drives.md).

# Microsoft RDP missing mapped drives

Microsoft RDP missing mapped drives in Remote Desktop Manager occur when running as administrator with UAC enabled, fixed via Group Policy or remapping drives.

Mapped network drives are not available in RDP sessions even though you have selected All drives; or are not displayed in the dialog when attempting to add Specific Drives using the More button.

This problem happens when you start Remote Desktop Manager with elevated privileges (Run as administrator). Mapped drives are not available from an elevated prompt when UAC is configured to Prompt for credentials in Windows.

This issue is not caused by Remote Desktop Manager, you will need to apply a fix on all workstations from which you must launch Remote Desktop Manager with elevated privileges.

### Solution

#### Method 1

1. Click on ***Windows Start***, type ***Run*** and open the app.
2. Type ***gpedit.msc*** to open the ***Local Group Policy Editor*** and ***allow*** the app to make changes.
3. Locate the following ***Group Policy*** path:

   Local Computer Policy\Windows Settings\Security Settings\Local Policies\Security Options
4. Configure the following policy to ***Prompt for consent***:

   User Account Control: Behaviour of the elevation prompt for administrators in Admin Approval Mode

#### Method 2

Map the required drives again in the elevated session. A good solution would be to create a batch/command file that starts by mapping the drives again, then launches Remote Desktop Manager


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.devolutions.net/rdm/knowledge-base/troubleshooting-articles/microsoft-rdp-missing-mapped-drives.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.