Last updated:
A new Citrix Workspace App release initially sounds routine.
However, version 2610 introduces changes that can quickly become relevant during larger client rollouts.
And this time, it is not just about new features.
🔍 What has changed?
Citrix Workspace App 2610 changes its runtime dependency from .NET 8 to .NET 10.
This means that installation may require and install an additional or updated .NET runtime.
Organizations using centralized software distribution through Intune, Configuration Manager or other deployment solutions should account for this change.
⚠️ The real challenge: x86 → x64
When migrating from a 32-bit Workspace App to a native 64-bit version, older third-party virtual channel plugins may become a problem.
Citrix therefore performs compatibility checks.
Possible results are recorded at the following path:
C:\Program Files\Citrix\Logs\IncompatibleThirdPartyPlugins.json
If an incompatible plugin is detected, automatic migration may be blocked.
Citrix does provide the parameter:
/SkipThirdPartyVCCheck
But be careful: this parameter only skips the check. It does not make incompatible plugins compatible.
🛠️ What I would check before a rollout
✅ Inventory existing x86 virtual channel plugins
✅ Account for .NET 10 dependencies in software distribution
✅ Test Teams, Webex, scanner and peripheral integration
✅ Validate silent installation, upgrade and rollback
✅ Check GACS policies after the update
💡 My takeaway
A Workspace App update is not automatically just a client update.
Once runtime dependencies, architecture and virtual channels are involved, an apparently simple version change can become a compatibility problem.
Especially with several hundred endpoints, I would not deploy it broadly straight away.
Test first. Then migrate.
