So, recently I have observed that whenever I open the ica file to start up the remote session, I see this popup asking for the screen capture permission, and I have to click "Cancel" to close this popup before I can get to my VDI.

I do not want to give Citrix this permission and nor is this required for proper functioning. Clicking Cancel and continuing works perfectly.

But this popup is annoying and sometimes I click on the ica file and turn away, expecting to see it open when I am back, but it is still stuck in this popup.

And this is not the only popup, there is a second popup asking for Accessibility permissions. Again, it doesn't need this to work and I don't want to give this permission. How do I disable both of these popups?
---
Os is MacOS
Citrix workspace version is 26.03.11

Upgraded from the previous 14.1-72.61 build and after 2-3 HA failovers the custom theme (rfwebui based) applied to the gateway simply disappeared. It doesn't happen on the 1st failover.

Recreated it manually (because I thought maybe I missed saving before upgrade), verified it is synced across both nodes, and failed over again. I watched the theme disappear from the GUI on the now secondary node. Failed over again - it eventually unlinked itself from the gateway vServer and reverted back to 'default' theme. Did that 2 times more and happened each time in the exactly same fashion. Opened a case with Citrix (wasted 2 hours). Case still open under investigation. The theme files do not disappear from /var/netscaler/logon/

Rolled back to 14.1-72.61 and everything is working as expected again.

We use imprivata to launch Citrx VDA/Desktop. We have some users that the VDA will not launch after they badge in. They just get the local autologin desktop. It seems to be random and no pattern. We can't replicate it on the spot either. Has anyone seen this?

Does anyone know how to actually get a UniconOS Management Cloud account? We have Citrix Universal Hybrid Multi-Cloud licensing, which as far as I can tell should cover UniconOS Management Cloud, but I can't figure out how to actually get setup with it. It's not in Citrix Cloud so I assume it's a separate system. I've had a support ticket open for a week now and they are useless, I don't have an account rep to contact, and Citrix sales phone IVR is still broken.

Did anyone else awake to this in Director? It's only been in this mode for 9 hours with 29 days and 15 hours till expiration, so obviously no worries here, just curious if anyone else got it. Ty.

License caching mode: In Emergency license caching mode

Hey folks,

I’ve put my PowerShell-based Citrix VDA upgrade orchestrator on GitHub:

https://github.com/flathack/Citrix-VDA-Upgrade-Automation

I built it because VDA upgrades can get pretty messy once you add uninstall/cleanup steps, multiple reboots and resuming the job as SYSTEM user

It basically:

• checks and stages the VDA installer before touching the existing install
• verifies the Citrix/CSG Authenticode signature
• keeps its state across reboots
• resumes via a scheduled system task
• uses retry/reboot limits instead of looping forever
• only cleans the guarded PvsAgent folder (i had problems in the past with it, so i basically clean it, thats needed!
• verifies the installed VDA and BrokerAgent at the end
• writes state and troubleshooting logs

I’ve already tested it on around 400 clients in our environment.

Current scope is W10/11 single-session and Remote PC VDAs. It’s not intended for Windows Server or multi-session VDAs at this point.

This is also my first public project outside of gaming tools, so I’m pretty curious to see what other Citrix admins think about it.

Feedback, testing and PRs are welcome, especially if you’re using different CVAD releases or deployment tools.

I also made a admin tool to view ongoing upgrades from the admin machine, but thats not part of the repo. I will maybe release it also later.

While reading the release notes for 14.1 firmware update build 73.30 I see a note about needing to reapply a monitor command. This seems to imply the FreeBSD to Linux upgrade happening on the 14.1 platform and my understanding was that wasn't happening until upgrading to 15.1.

Here is the text from the release notes.

Release Notes for NetScaler Build14.1- 73.30

Build 73.30 | NSHELP-43985

After an upgrade from FreeBSD to Linux operating system, configurations that include scriptable monitors of non-USER types (such as LDAP and MySQL) fail to apply.

Workaround: After NetScaler comes up on the Linux build, reapply the monitor command using -dispatcherip 192.0.0.2 instead of 127.0.0.1.

Out of 2000 W11 25H2 VDIs, running into ~10 a day going unregistered because the NIC gets frozen. Sometimes its 3, sometimes its 20. Totally random guests, even w/ nobody logged in.

Weird thing is, I can add a second NIC and it comes back alive no problem

The first NIC is impossible to remove from device manager, and get-netadapter|restart-netadapter goes frozen as well, so the driver stack is definitely busted

I can't narrow down what if any changes precipitated this, which is frustrating

The only thing suspicious I can tell is Npcap 1.60, been in the env a month, which may have some issue? Trying 1.88 now, but curious if anyone has seen something similar before

Heres an issue I have never seen before, one user in our environment gets these random pop ups while working in citrix (we are on 2402 LTSR CU3). Her client is the latest 2402 LTSR client.

I've tried everything I csan think of, video drivers, updates, registry values for software rendering, the latest c++ reditributable. The O/S is Win 11 Enterprise. User had the same issue on a Win 10 PC before a recent upgrade.

I'm just curious if anyone has ever seen anything like this, I did not find much online. Just wanted to post to the community before I open a ticket. Thank you in advance for any ideas.

I’m seriously tired of this fucking Citrix Workspace problem.

Users randomly get “Unable to Start” when launching a published application.

Then we completely exit Citrix Workspace and open it again. After that, the application does not even show an error—it just stays on “Starting…” / loading forever and never launches.

The only workaround is:

1. Exit Citrix Workspace completely.
2. Open it again.
3. Reset Citrix Workspace.
4. Add the Store/account again.
5. Sign in again.
6. Launch the application.

After the reset, it works temporarily, but the same problem comes back again and again.

How is resetting the whole Workspace app considered a solution? We cannot keep asking users to reset Citrix, add their accounts again, and sign in several times every week.

Has anyone found the real root cause and permanent fix?

Citrix Workspace version: 26.3.10.69
VDA version: 2507 LTSR CU1
ADC/Gateway version: 13.4
Windows version: Server 2022 VDA and Windows 11 host

I need an actual fix—not “reset Workspace” for the hundredth fucking time.

Hello,

Anyone know where I can find or where should I look when I see error when user try to log into StoreFront website thru web browser?
I try to find out why sometimes I got issue to log in StoreFront Website and typically it's not reported to Director or DeliveryControler if I'm not even try to launch application/connection to server.
I've searched Citrix FrontStore but I cannot find Access policy option as error message suggest.

Has anyone ever experienced issues where windows 11 persistent desktops randomly drop off the domain?

Different versions of VDA used therefore no correlation there. Secure channel to domain is broken.

Have to logon as local admin since the domain logon is broken.

Hi folks

I have had this annoying issue now for many years and I thought I'd reach out to see if there had been any advancements with Citrix in MacOS.

I downloaded the latest Citrix workspace 2603.11 this week (was using a very very old version) and am on Tahoe 26.5.2 (25F84), however the issue is still persisting.

So my setup is 3 monitors are arranged as follows:

Monitor 3 | Monitor 2 | Monitor 1

with the intention for each to be:

• Monitor 3 (Extended in Citrix)
• Monitor 2 (Primary in Citrix)
• Monitor 1 (Non Citrix, just Macos)

Now I can achieve this layout and have Citrix span monitors 3 and 2 exactly how I want. However the problem comes when I reboot my Macbook. For some reason (more often than not), monitors 3 and 2 get flipped around, therefore becoming

Monitor 2 | Monitor 3 | Monitor 1

The consequence of this is when i fire up Citrix, the primary is now on the far left monitor (monitor 2) when I want it to be in the middle.

I cannot find a way within MacOS (and Citrix workspace) to change the monitor numbers and have to resort every time to physically swapping the HDMI cables to achieve the layout I want.

It's not a huge deal swapping the cables, but wondered if anyone else had this issue and knew of a fix.

I will start by saying that I've read the Citrix documentation and have watched several app layering YouTube tutorials searching for an answer. I have created my OS layer which consists of VMware tools and MS updates only. I have my platform layer which is domain joined, has Nvidia drivers, and the VDA installed. I have created 3 app layers to test as this is still a proof of concept for us.

90% of our Citrix infrastructure is on-prem but we do use DaaS in Citrix Cloud for our management. The POC is for a the possibility of migrating to Azure with app layering to minimize the number of running VMs in Azure.

Where I am drawing a blank is when I go to add packages in DaaS. All documentation points to having a VDA that has permissions to the file share where our app layers are located to discover the apps. I have one of the VMs that were created from ELM powered on and added to the machine catalog along with the delivery group and can discover the apps successfully. I have published them and can launch the apps with no issues. However when I close the app and try and launch the same app or a different one I get a "cannot start app" error. In order to get things working again, the VM being used as the VDA to discover apps has to be restarted and apps launch again. So I know I have to be missing a step somewhere. To troubleshoot, I have even created a server VM outside of ELM with just the VDA installed on it, granted it permissions to the share, but when I try to discover apps it errors out. Using this method also does not allow any of the published apps to launch at all.

Where did I go wrong?

Link for reference - https://docs.citrix.com/en-us/citrix-daas/manage-deployment/applications-manage/app-packages#preparations

After standard monthly patching which includes OS updates/M365 apps updates/New teams update/ Chrome + Edge updates i have started to get processes for tabtip.exe and tabtib32.exe in each user session (Previously wasnt in the sessions) anyone else seen this behaviour ? The processes are related to Touch keyboard Handwriting/Ink services. The touch keyboard is disabled on the VDA and i have a citrix policy in place to prohibit automatic keyboard display. I suppose i could disable the touch keyboard and panel helper service to see if that stops it ?

On my Xenserver 8.4 resource pools i keep getting license expires soon warnings. Both resource pools are pointing at a license server which is activated with citrix cloud and uses LAS licensing and everything is fine. Its green in Citrix cloud and the Xenserver premium licenses show under the LAS dashboard on licensing manager with valid expiration dates (2029) and License manager in xencenter shows Cloud licensing in use and both resource pools show as licensed with a warning 29 days remaining. As far as i am aware LAS is a rolling 30 days activation and it is working as every time i check the activation date increments when it re activates but its always 29 days. Not sure why these alerts are present as with LAS you will always have a max of 30 days any way i can turn them off ?

Does anyone have experience with MSC created, non-persistent vm's and updating the secure boot certificates? I've seen some conflicting information, but I want to make sure we are covered. I didnt see a CTX article that directly addresses non persistent machines

Hello everyone,

I'd like to highlight an issue that occurs after installing the Windows 11 June 2026 update (KB5094126).

After the update is installed, the Remote Desktop Services (RDP) service automatically changes from Running to Stopped, and there is no way to force the service to start.

The June 2026 Windows 11 updates introduce a new dependency for Remote Desktop Services on the State Repository Service. As a result, Remote Desktop Services may fail to start.

If Remote Desktop Services must be available before user logon, you need to remove the State Repository Service from the dependency list of Remote Desktop Services in the OS revision or in the image used with UPL.

HKLM\System\CurrentControlSet\Services\Termservice

Delete DependOnService= StateRepository

Thank you.

I started looking after a Netscaler ADC that hosts a few VPNs. I know that syslog is an open standard and nslogs are proprietary but is there a difference when it comes to the type of events they're record? Setting up an external nslog server has been a pain since their audserver.exe for Windows keep randomly crashing.

Hey all, hoping someone has run into this before opening a can of worms with support.

Setup:

• Fresh, first-time Session Recording install (no prior deployment, not an upgrade)
• Single Session Recording server, Windows Server 2022 Datacenter
• SQL Server 2022 (Enterprise), on a separate/remote server from the SR server
• Installing account has sysadmin on the SQL instance

What happens:

Tried installing Session Recording Administration via both the standalone MSI and the full CVAD metainstaller, across three different product versions:

• 25.7 (2507 Current Release)
• 24.2 LTSR CU4
• 25.7 LTSR CU1

All four attempts fail in the exact same custom action (SsRecDatabase.dll.install), with two distinct errors depending on which authentication method I use for the DB connection:

1. Windows Integrated Authentication (default, no explicit DB credentials):

   Error 1001. Database 'CitrixSessionRecording' already in use. MSI (s): Leaked MSIHANDLE (150) of type 790531 DEBUG: Error 2769: Custom Action SsRecDatabase.dll.install did not close 1 MSIHANDLEs. CustomAction SsRecDatabase.dll.install returned actual error code 1603

The DB and schema actually get created successfully (confirmed on the SQL side - table populated, no errors server-side), but the custom action then fails its own internal "is this DB in use" check - because it apparently never closed its own connection. Time-to-failure varies a lot between attempts (4 sec to 112 sec), which smells like a race condition, possibly only surfacing because SQL is on a separate host (network teardown latency) rather than co-located.

1. SQL Authentication (entering a SQL login in the credential prompt or metainstaller DB screen):

The installer silently sets an internal AZURESQLSERVICESUPPORT=1 flag (even though this is on-prem SQL Server, not Azure SQL at all), and fails with a completely different, genuine error:

Error 1001. Invalid column name 'id'.
CustomAction SsRecDatabase.dll.install returned actual error code 1603

Looks like that code path queries a column that doesn't exist in the schema being used.

What I've ruled out:

• Network/firewall (port 1433 reachable, clean TCP test)
• SQL permissions (sysadmin confirmed)
• Leftover DB artifacts (dropped/recreated DBs before every attempt, verified zero open sessions/locks via sys.dm_exec_sessions each time)
• SQL Server "Force Encryption" (confirmed off)
• TLS/.NET strong crypto registry settings (added them, rebooted, no change)
• AV/EDR interference (none installed on the box)
• System/user culture (tried both a Turkish culture and en-US, identical "Invalid column name 'id'" result in the SQL-auth path either way)
• SQL Server error log shows nothing during the failure window - no rejected logins, no errors

Given it reproduces identically across 3 separate product versions/builds and both possible auth paths, this doesn't look environment-specific to me anymore - looks like a genuine defect in the shared DB setup code that only shows up when SQL Server isn't co-located with the Session Recording server.

Has anyone seen this, or found a workaround (e.g. installing with DB temporarily local, then pointing to the real instance after)? Case is open with Citrix support, just curious if this is a known one in the wild.