> 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/da/knowledge-base/troubleshooting-articles/mouse-cursor-invisible-in-remote-desktop-manager.md).

# Musemarkøren er usynlig i Remote Desktop Manager

En usynlig musemarkør i sessioner i Remote Desktop Manager er et kendt problem i Microsoft Edge WebView2 Runtime, der rettes ved at deaktivere Skjul markør under indtastning.

Musemarkøren kan blive usynlig, mens De bruger Remote Desktop Manager, selv om den forbliver synlig og fungerer alle andre steder i operativsystemet.

Denne funktionsmåde skyldes et [kendt problem](https://github.com/MicrosoftEdge/WebView2Feedback/issues/5687) i Microsoft Edge WebView2 Runtime (version 152.0.4191.x), som Remote Desktop Manager bruger til nogle af sine komponenter. WebView2 beholder fejlagtigt musemarkøren markeret som skjult, når den er blevet skjult af indstillingen ***Skjul markør under indtastning***, så markøren forbliver usynlig i hele programvinduet.

På tidspunktet for skrivningen er der ikke udgivet en officiel rettelse af Microsoft. En varig løsning afhænger af, at Microsoft leverer en opdateret WebView2 Runtime.

### Løsning

Deaktivér den Windows-indstilling, der udløser WebView2-fejlen:

1. Åbn Windows Kontrolpanel, og gå til egenskaberne for ***Mus***.
2. På fanen **Markørindstillinger** skal De deaktivere ***Skjul markør under indtastning*** og klikke på ***Anvend***.
3. Genstart Remote Desktop Manager.

Det deaktiverer den mekanisme, som WebView2 misbruger, så markøren forbliver synlig i Remote Desktop Manager. Når Microsoft leverer en rettet runtime, kan De aktivere denne valgmulighed igen, hvis De foretrækker det.

{% hint style="info" %}
Hvis deaktivering af denne indstilling ikke løser problemet, eller for opdateringer om denne WebView2-fejl, kan De se [problemet i Microsoft Edge WebView2Feedback](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/da/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.