I currently have the problem with a customer that ...
# citrix-vad
c
I currently have the problem with a customer that after a Citrix Workspace app update to the current version 2402 LTSR, the mouse pointer is not visible with text (line with top bottom line/text marker). If I change the icon in the system settings, it works - but it is ugly and not a solution. Regardless of which application. Various VDA versions and server versions have been tested.
s
One customer is reporting similar symptom, will check their CWA version
m
just see one post above, describing the same problem 😄 I ended up creating a script that changes IBeam Cursor at logon.. but as you said: ugly
here´s the logon script.. The C# code is needed as the cursors needs to be refreshed, otherwise it will work only at 2nd logon.
Copy code
# Define a C# class for calling WinAPI.
Add-Type -TypeDefinition @'
public class SysParamsInfo {
    [System.Runtime.InteropServices.DllImport("user32.dll", EntryPoint = "SystemParametersInfo")]
    public static extern bool SystemParametersInfo(uint uiAction, uint uiParam, uint pvParam, uint fWinIni);
    
    const int SPI_SETCURSORS = 0x0057;
    const int SPIF_UPDATEINIFILE = 0x01;
    const int SPIF_SENDCHANGE = 0x02;

    public static void CursorHasChanged() {
        SystemParametersInfo(SPI_SETCURSORS, 0, 0, SPIF_UPDATEINIFILE | SPIF_SENDCHANGE);
    }
}
'@

# Change the cursor
Set-ItemProperty -Path 'HKCU:\Control Panel\Cursors' -Name 'IBeam' -Value '%SystemRoot%\cursors\beam_r.cur'

# Notify the system about settings change by calling the C# code
[SysParamsInfo]::CursorHasChanged()
👍 1
m
I'm so tired of this problem. I am dealing with random connection disconnects and the recommendation from Citrix is to use the LTSR release. I am not looking forward to this problem coming back. Also, if your user is using an AMD graphics card, check to see if there's an update. I have also encountered this with ARM64-based devices where everything is up to date.
s
I have seen this as well (disconnects and display issues) with 2402 CU1 LTSR and depending on if Windows or Mac, we have typically downgraded CWA and turned off auto update. I have not tested with 2402 LTSR CU3 yet. It's on my list.
r
Can you share a video of the issue and also share CDF traces? Was a support case raised for this?
p
I think we may be mixing issues here. The "cursor goes to a translucent ibeam" issue is a design function of Windows itself, and there are known workarounds like the above. I have had a fix in place since we first rolled out Windows 10.
c
Yes, a support case has been opened. I wrote down all the hardware devices from the tickets and compared them. But everything from ThinClient (Linux OS) to Windows, AMD, Intel etc. is included. What is very strange is that of all devices with this CWA version, it affects a maximum of 1% to 2% of devices. VDA and target OS do not seem to play a role in the combination, the effect on affected devices does not change. CDF traces have not yet been created.