random lost of cursor on VNC

[fredmo]

Windows Version

Microsoft Windows [version 10.0.26200.8737]

WSL Version

2.7.9.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

No response

Distro Version

Ubuntu 26.04

Other Software

Dear WSL,

By using, VNC ( TightVNC ) , I am regularly losing the mouse Cursor.
It is still here, there is reaction, but not visible.

And the only way to restore is to do a wsl.exe--shutdown , and relaunch wsl.

Could you please track this issue ?

Thank you.
Frédéric

Repro Steps

Difficult to say / to reproduce , maybe due to " alt tab " between VNC and Windows apps.

Expected Behavior

having a command shell as workaround to restore the visibility of the cursor.
and not having at all the issue.

Actual Behavior

Dear WSL,

By using, VNC ( TightVNC ) , I am regularly losing the mouse Cursor.
It is still here, there is reaction, but not visible.

And the only way to restore is to do a wsl.exe--shutdown , and relaunch wsl.

Could you please track this issue ?

Thank you.
Frédéric

Diagnostic Logs

No response

[github-actions]

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise, please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.

If this is a networking issue, please use .\collect-wsl-logs.ps1 -LogProfile networking instead, following the instructions in Collect WSL logs for networking issues

Once completed please upload the output files to this GitHub issue.

See Collect WSL logs (recommended method).

If you choose to email these logs instead of attaching them to the bug, please send them to wsl-gh-logs@microsoft.com with the GitHub issue number in the subject, and include a link to your GitHub issue comment in the message body, and reply with '/emailed-logs'.