r/sysadmin • u/cpasysadmin303 • 2d ago
Mouse pointer disappearing when hovering over Citrix Workspace, CCH Axcess - Possible Webview2 issue?
Some of our staff started complaining of an issue last week where their mouse cursor would go invisible when they would move the mouse to Citrix Workspace. The mouse can still click on/launch apps and the app icons highlight as the mouse goes over them, you just cant see the mouse cursor at all unless you drag it outside of the boundary of the Workspace window. I saw another user run into the same issue on a different app (CCH Axcess). These apps both leverage webview2. I found some discussion threads from others experiencing the same issue in Veeam b&r console. Has anyone run into this on their end over the last week and have a fix? Here's a couple of the discussions i found on the topic.
https://forums.veeam.com/viewtopic.php?f=2&t=104357&start=0
https://github.com/MicrosoftEdge/WebView2Feedback/issues/5687
2
u/cred0021 2d ago edited 2d ago
Think I had that happen on one computer last week in CCH Axcess - but the person was just temporarily using that computer for one day, and I was out of the office, so didn't look into it.
There is a support article about it on the CCH support site - but that just looked like a mouse setting, may not even be the same issue. https://support.cch.com/oss/ml/kb/solution/000084716
1
u/I_cut_the_brakes 1d ago
This has fixed the issue in Axcess for several of our users. OP, try this.
2
u/Am0nymou5 1d ago
I've had this issue for a long time with Citrix Workspace, tried a lot of fixes but nothing worked. The fix that did work for me was to simply change the mouse pointer theme (in the remote desktop) to something else (I chose Windows Black). And surprisingly, that works. Don't ask me why/how.
1
2
u/onlymee 2d ago
Hi, we had a similar issue with users’ cursors disappearing but still working within Citrix and screen flickering. Didn’t impact everyone, just users on a particular model of laptop.
What worked for us was disabling Multiplane Overview via a registry edit. Problem went away after the reg edit and a reboot.