General Discussions

[Carl20]

Hi

Need some help since i do have some issues when i connect to a Remote Desktop session.
My mouse cursor becomes transparent on few areas like in Excel, in the search bar of Windows, address bar in Edge in the Remote session.

My laptop is HP EliteBook 645 14 inches G10 Notebook that has the AMD Ryzen 5 PRO 7530U GPU Processor.
My OS (Win 11 23h2), the Display driver and everything else are up to date.

Currently, the temporary solution is changing the Display Driver to Microsoft Basic Display Adapter but this is not a possible solution because it affects more than one of my clients.

Maybe this can help since I'm receiving the following message from the AMD Software : Andrenaline Edition has detected the presence of one or more panels with high dpi values connected to the system.
Already try to change to Highest DPI via the compatibility Tabs in Windows but the problem is still there.

Thanks

[Carl20]

I forgot to indicate that the problem is only on the Laptop Screen and the problem disappears when it is connected to a monitor.

[FunkZ]

This is a known issue with the default Windows mouse pointer scheme when hovering over text fields.

You can select a different mouse pointer scheme or more specifically, change the Text Select pointer to use an alternate version, such as beam_r.cur

[Carl20]

It was the very first thing I tried when I noticed this problem but issue still in the Remote Destop session (Azure Virtual Desktop).
We don't have this cursor issues on other HP model that have Intel GPU

[arzhost0]

That's may be the issue with compatibility between the AMD driver and  Remote Desktop. Have you tried tweaking hardware acceleration setting or messing around with cursor schemes in  Windows? Also may worth checking AMD's setting for any DPI-related tweaks as well.

[Flaresolverr]

Since it seems related to high DPI scaling, have you tried adjusting the scaling settings in Windows Display settings? Also, disabling hardware acceleration in Excel and Edge might help. If it's an AMD driver issue, rolling back to an earlier stable version could be worth testing. Hope you find a fix soon!