Finding in the Wild | Citrix – ICA Session Started, but No Desktop Is Visible

An issue that can quickly send Citrix troubleshooting in the wrong direction: The user launches a virtual desktop using a downloaded ICA file. The connection starts, but Citrix Desktop Viewer does not appear. ❌ No visible desktop ❌

An issue that can quickly send Citrix troubleshooting in the wrong direction:

The user launches a virtual desktop using a downloaded ICA file. The connection starts, but Citrix Desktop Viewer does not appear.

❌ No visible desktop
❌ No clear error message
❌ Launching the session again does not necessarily help
✅ The session may already exist on the VDA

🔍 Root cause – HDX-97520

Under HDX-97520, Citrix documents a client-side issue when launching sessions through downloaded ICA files.

The key distinction: a successfully established ICA connection does not automatically mean that the corresponding Desktop Viewer interface is displayed.

The cause is therefore not necessarily the Delivery Controller, VDA or StoreFront.

🛠️ My troubleshooting approach

1. Check the client

First, I check the installed Citrix Workspace App and deliberately relaunch the downloaded ICA file.

I check whether wfica32.exe starts and whether Desktop Viewer is visible.

2. Check the session on the server side

Using Citrix Director or PowerShell, I check whether the user already has a session on the VDA.

If the session exists but no desktop is visible, I focus on the client side.

3. Analyze logs and processes

* Workspace App version and ICA launch method
* wfica32.exe and Desktop Viewer processes
* Citrix Workspace App diagnostic logs
* Windows application events
* Session status on the VDA

✅ The fix

Citrix lists HDX-97520 among the fixed issues in Citrix Workspace App 2607 LTSR for Windows.

My approach: update an affected endpoint, then retest ICA launch and the Desktop Viewer display.

💡 My takeaway

A user seeing no desktop does not automatically mean that Citrix failed to establish a session.

Combining client diagnostics with a server-side session check reveals where the issue actually lies.

Finding in the Wild | High CPU Utilization Caused by Citrix Workspace App?

It is worth looking at receiver.exe. Recently, I have heard more reports of unusually high CPU utilization associated with Citrix Workspace App. Citrix has officially documented a corresponding issue: RFWIN-41567 On Windows Server 2022, receiver.exe could cause increased

It is worth looking at receiver.exe.

Recently, I have heard more reports of unusually high CPU utilization associated with Citrix Workspace App.

Citrix has officially documented a corresponding issue:

RFWIN-41567

On Windows Server 2022, receiver.exe could cause increased CPU utilization in certain installations.

The fix has been included since Citrix Workspace App 2603.10.

On server systems, jump hosts or in double-hop scenarios in particular, this can quickly become a performance problem.

Important: I would not automatically attribute high CPU to this bug. First check:

– Which CWA process causes the load?
– Which Workspace App version is running?
– Is CPU usage persistently high or periodically spiking?
– Is a store refresh currently running?
– Are Teams/Webex/Zoom optimizations involved?
– What influence do AV/EDR/DLP have?

My recommendation:
If CWA runs on Windows Server 2022 and receiver.exe causes unusually high CPU utilization, check the version first. For builds before 2603.10, test a current supported build with a pilot group.

This is more than a community observation: Citrix has officially confirmed and fixed the issue.

Finding in the Wild | CWA CleanInstall & Teams SlimCore

During a recent Citrix Workspace App update , I encountered interesting behavior involving Microsoft Teams SlimCore . The Microsoft Teams VDI Plugin was already installed on the client. Workspace App was then updated using /CleanInstall . Initially, everything

During a recent Citrix Workspace App update, I encountered interesting behavior involving Microsoft Teams SlimCore.

The Microsoft Teams VDI Plugin was already installed on the client. Workspace App was then updated using /CleanInstall.

Initially, everything looked fine:
Citrix Workspace App ✔️
Teams VDI Plugin ✔️
Software deployment ✔️

Nevertheless, SlimCore optimization no longer worked.

The investigation revealed that the required DLLs were no longer present in the ICA Client directory, although the Teams VDI Plugin still appeared as installed under Apps & Features.

That is precisely what makes this issue interesting.

If an automated CWA update checks only installation status, you get a successful deployment even though the actual Teams optimization no longer works.

For my update tests, this means:
CWA version → Teams VDI Plugin → DLLs → SlimCore → actual optimization mode
must be checked together.

Especially with the increasing move to SlimCore, I believe this functional test should be part of a CWA/Teams update.

👉 Finding in the Wild: installed does not automatically mean operational.

These issues are exactly why I do not just install Citrix updates, but also check the relevant functions afterwards.

Finding in the Wild: I will keep investigating.

Finding in the Wild | Citrix Workspace App + IGEL – BadWindow in Multi-Monitor Setups

At a customer, I encountered an interesting issue with Citrix Workspace App on IGEL OS. The symptoms: In a multi-monitor configuration, individual Citrix windows occasionally misbehaved. The session itself generally worked, but the logs showed X11 errors such

At a customer, I encountered an interesting issue with Citrix Workspace App on IGEL OS.

The symptoms:

In a multi-monitor configuration, individual Citrix windows occasionally misbehaved. The session itself generally worked, but the logs showed X11 errors such as:

BadWindow
BadDrawable
BadGC

After some investigation, I narrowed the issue down to the interaction between IGEL OS, Citrix Workspace App and X11 window handling.

One interesting parameter provided by IGEL for Citrix Workspace App is:

app > cwa > wfclient > thinwire30 > ignorexerrors

Specific X11 errors can be ignored there using values such as

20.0/3, 55.0/9, 60.0/13

.

This mitigated the behavior in my case.

But be careful: this is not a true fix for the underlying cause.

IgnoreXErrors causes the relevant X11 errors to be ignored. These errors also stop appearing in the logs.

That must be considered during troubleshooting. A clean log afterwards does not automatically mean the underlying cause has disappeared.

My learning from this case:

If Citrix generally works on an IGEL endpoint but unusual window issues occur, particularly with multiple monitors, examine the CWA/X11 logs.

BadWindow, BadDrawable or BadGC can be useful clues.

And before dismantling the VDA, HDX Graphics or the entire Citrix infrastructure:

Check the endpoint first. 😉

Finding in the Wild | Citrix Workspace App 2603.11 x64

I came across an interesting issue with the native 64-bit version of Citrix Workspace App 2603.11 . This is particularly interesting because 2603.11 is also one of the builds Citrix recommends updating to because of CVE-2026-78546 and CVE-2026-78547.

I came across an interesting issue with the native 64-bit version of Citrix Workspace App 2603.11.

This is particularly interesting because 2603.11 is also one of the builds Citrix recommends updating to because of CVE-2026-78546 and CVE-2026-78547.

After the update, under certain conditions:
❌ Published applications and desktops may fail to start
❌ Domain pass-through authentication against StoreFront may fail
❌ Users may suddenly receive a credential prompt

The cause is related to a missing or incorrect reference to the 64-bit cck.dll.

Citrix has now documented a workaround:

The following value must exist there:
Name: X64
Type: REG_SZ
Value: C:\Program Files\Citrix\ICA Client\Receiver\cck.dll

Via command line:

Citrix plans to include the fix in an upcoming 2603 release.

💡 The interesting part:
Security says: Upgrade to 2603.11 or later.

Operations says: Not without testing, especially with StoreFront + domain pass-through.

These are exactly the small details that are easy to overlook in a test environment and then cause trouble during a broad client rollout. 😉

Finding in the Wild: Anyone currently upgrading to CWA 2603.11 x64 should explicitly test app/desktop launch and domain pass-through.