> 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/mouse-cursor-invisible-in-remote-desktop-manager.md).

# Mouse cursor invisible in Remote Desktop Manager

Mouse cursor invisible in Remote Desktop Manager sessions is a known Microsoft Edge WebView2 Runtime issue, fixed by disabling Hide pointer while typing.

The mouse pointer may become invisible while using Remote Desktop Manager, even though it remains visible and functional everywhere else in the operating system.

This behavior is caused by a [known issue](https://github.com/MicrosoftEdge/WebView2Feedback/issues/5687) in the Microsoft Edge WebView2 Runtime (version 152.0.4191.x), which Remote Desktop Manager uses for some of its components. WebView2 incorrectly keeps the mouse pointer flagged as hidden once it has been hidden by the ***Hide pointer while typing*** setting, causing the pointer to stay invisible across the whole application window.

At the time of writing, no official fix has been released by Microsoft. A permanent resolution depends on Microsoft shipping an updated WebView2 Runtime.

### Solution

Disable the Windows setting that triggers the WebView2 bug:

1. Open the Windows Control Panel and go to the ***Mouse*** properties.
2. In the **Pointer Options** tab, disable ***Hide pointer while typing*** and click ***Apply***.
3. Restart Remote Desktop Manager.

This disables the mechanism that WebView2 is misusing, so the pointer stays visible in Remote Desktop Manager. Once Microsoft ships a fixed runtime, you can re-enable this option if you prefer.

{% hint style="info" %}
If disabling this setting does not resolve the issue, or for updates on this WebView2 bug, see the [Microsoft Edge WebView2Feedback issue](https://github.com/MicrosoftEdge/WebView2Feedback/issues/5687).
{% endhint %}


---

# 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/mouse-cursor-invisible-in-remote-desktop-manager.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.