Cursor disapearing in RDM

We have the same issue since RDM 2026.2.18.0.
RDM is published as a Citrix published application from Windows Server 2025 and Citrix VDA Version 2607 LTSR.

Hello,

Thank you for contacting us on this matter! We investigated the issue with the mouse cursor not being visible in Remote Desktop Manager.

Our current investigation indicates that the behavior may be related to the optional Windows update KB5120998, potentially in combination with the Microsoft Edge WebView2 Runtime. The timing of this update corresponds with the reports we are currently investigating; however, the root cause has not yet been fully confirmed.

As a first diagnostic test, could you please check whether KB5120998 is installed on an affected workstation? If it is installed and your organization's IT policies allow it, please uninstall the update using the following steps:

Settings → Windows Update → Update history → Uninstall updates

After uninstalling KB5120998, please restart the workstation and let us know whether the mouse cursor becomes visible again in Remote Desktop Manager.

If uninstalling the update does not resolve the issue, or if removing it is not possible in your environment, could you please provide us with the following information:

Your Windows display language (for example, German, Danish, English, etc.).

Your Microsoft Edge WebView2 Runtime version. You can find this by opening the following folder and providing us with the version/folder name shown there:
C:\Program Files (x86)\Microsoft\EdgeWebView\Application

While the issue is present, please press Ctrl+Shift+Win+B once. This resets the Windows graphics stack. Please let us know whether the cursor becomes visible afterward.

These results will help us confirm whether the recent Windows update is involved and determine the appropriate next steps.

Best regards,

One of our team members tried the procedure, and he still experiences the bug. Here is some of the info he gathers :

Diagnostic Remote Desktop Manager
=================================

Date : 2026-09-03 15:53:10
Ordinateur : XXXXXX
Utilisateur : XXXXXX

Mise à jour recherchée : KB5120998
Mise à jour installée : NON

Langue d'affichage Windows : français (Canada)
Code de langue : fr-CA

Version Microsoft Edge WebView2 Runtime : 152.0.4191.53
Dossier WebView2 : C:\Program Files (x86)\Microsoft\EdgeWebView\Application

Test graphique à effectuer pendant que le problème est présent :
Ctrl + Shift + Windows + B

Le curseur devient visible après le test : OUI / NON

One of our team members tried the procedure, and he still experiences the bug. Here is some of the info he gathers :

Diagnostic Remote Desktop Manager
=================================

Date : 2026-09-03 15:53:10
Ordinateur : XXXXXX
Utilisateur : XXXXXX

Mise à jour recherchée : KB5120998
Mise à jour installée : NON

Langue d'affichage Windows : français (Canada)
Code de langue : fr-CA

Version Microsoft Edge WebView2 Runtime : 152.0.4191.53
Dossier WebView2 : C:\Program Files (x86)\Microsoft\EdgeWebView\Application

Test graphique à effectuer pendant que le problème est présent :
Ctrl + Shift + Windows + B

Le curseur devient visible après le test : NON

@burm003adm

Hello,

Thank you for your feedback.

The cause is not Remote Desktop Manager itself, but a bug in the Microsoft Edge WebView2 Runtime (version 152.0.4191.x), which RDM uses for some of its components. WebView2 incorrectly keeps the mouse pointer flagged as hidden, so the pointer remains invisible across the whole application window.

The runtime updates itself silently outside Windows Update, which is why the behaviour appears unchanged in the Microsoft updates. Microsoft is tracking it here: https://github.com/MicrosoftEdge/WebView2Feedback/issues/5687

We would appreciate it if you could test the following steps, which could be a working temporary workaround:

• Open the Control Panel and go to Mouse.
• Switch to the Pointer Options tab.
• Uncheck "Hide pointer while typing" and confirm with OK.

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

Two things would help us a lot while we follow up with Microsoft:

• Is the affected machine touch-capable (touchscreen or pen input)?
• Do other applications that use WebView2 - for example, classic Outlook - show the same behaviour?

Thank you for your collaboration.

Best regards,

Hi, the workaround with the mouse "Hide pointer while typing" is working for me. Thanks, I just thought first it was an april fools joke, but then again its not april, just another day with Microsofts Bugs.

Hello,

Thank you for your patience while we investigated the disappearing mouse pointer issue.

We found the root cause: it is not caused by Remote Desktop Manager itself, but by a bug in the Microsoft Edge WebView2 Runtime (version 152.0.4191.x), which RDM relies on for some of its components. WebView2 incorrectly keeps the mouse pointer flagged as hidden, and once that happens, the pointer stays invisible across the whole application window.

The WebView2 Runtime updates itself silently in the background, outside of Windows Update, which is why this started happening without any changes on your end.

Workaround to test
While we wait for Microsoft to ship a fixed runtime, the following steps have worked as a temporary fix for other affected customers:

1. Open the Control Panel and search for Mouse.
2. Switch to the Pointer Options tab.
3. Uncheck "Hide pointer while typing" and click OK.

This disables the mechanism that WebView2 is misusing, so the pointer stays visible in RDM. Once Microsoft releases a fix, you're free to re-enable that option if you'd prefer to keep it on.
Could you let us know if this resolves the issue on your end?

One more thing that would help
Since this is a Microsoft-side bug affecting multiple WebView2 applications, not just RDM, the more people report it directly on Microsoft's GitHub thread, the more likely it is to get prioritized on their end. If you have a moment, adding a comment there would genuinely help move this forward: https://github.com/MicrosoftEdge/WebView2Feedback/issues/5687#issuecomment-5541422822
Please don't hesitate to reach out if you have any questions or if the workaround doesn't help.
Since we cannot assist further, I am now closing this case.
If you would like to open a new case with us, please send an email to service@devolutions.net
Want to get even more out of your Devolutions products? Explore our free Masterclasses and unlock advanced workflows at your own pace.

Best regards,