Finding in the Wild | Citrix & FSLogix – Outlook Only Works on the Second Launch!

While analyzing a Citrix multi-user environment, I encountered an interesting issue:

Outlook starts, but Microsoft 365 authentication does not work reliably. Sign-in only succeeds on the second attempt.

The FSLogix profile loads successfully, other applications work, and the Citrix VDA is registered.

⚠️ The symptoms

• Outlook repeatedly prompts for credentials.
• Microsoft 365 SSO fails intermittently.
• Relaunching Outlook sometimes allows sign-in to succeed.
• Profile and ODFC containers are mounted.
• The issue can also occur outside Citrix.

🔬 Possible causes

A mounted FSLogix container does not guarantee working Microsoft 365 authentication.

Outlook relies on components including Windows Web Account Manager (WAM) and Microsoft.AAD.BrokerPlugin.

Potential sources of failure include:

🔹 Incorrect WAM initialization
🔹 Issues with Entra device identity or the PRT
🔹 Roaming of device-bound authentication data
🔹 Timing issues during profile initialization
🔹 Third-party add-ins or security software

A root cause has not yet been confirmed.

🛠 My diagnostic steps

1️⃣ Check FSLogix

Review the Profile and ODFC logs under C:\ProgramData\FSLogix\Logs\ for mount failures and timeouts.

2️⃣ Check the WAM broker

Get-AppxPackage Microsoft.AAD.BrokerPlugin

3️⃣ Check Entra authentication

dsregcmd /status

In particular, check AzureAdJoined, DomainJoined and AzureAdPrt in the affected user’s context.

4️⃣ Correlate events

Compare WAM, Entra, AppModel and Office events with the timing of the Outlook launch.

5️⃣ Review the FSLogix configuration

Check ODFC policies, identity roaming and the FSLogix version.

⚠️ What I would avoid

Indiscriminately deleting all Microsoft 365 token caches or disabling WAM.

These measures may change the symptoms without addressing the underlying cause.

💡 My takeaway

A successfully loaded FSLogix profile does not automatically mean Microsoft 365 SSO is working.

What matters is the interaction between Windows device identity, WAM, profile management and Outlook.

📚 Sources

Microsoft – FSLogix Known Issues
https://lnkd.in/eU_ygcFg

Citrix – CTX695895
https://lnkd.in/eeAWVnQG

17:35

Finding in the Wild | Citrix PVS – Database Connection Drops Because the vDisk Version Is 20!

Sometimes the smallest details lead to surprisingly extensive troubleshooting.

I recently received a report of particularly unusual behavior in Citrix Provisioning Services (PVS):

⚠️ The symptoms

The PVS environment experienced repeated, brief database connection interruptions.

The following events appeared regularly in the event log:

• Event IDs 201 / 214 – PVS database connectivity issues
• SQL Error 8023 – Error processing a supplied value
• PVS loses its database connection for a few seconds and temporarily goes offline.

The strange part: not all targets were affected, only one specific group.

🔬 The cause – reproduced by Citrix in the lab

After extensive analysis, Citrix reproduced the issue in its lab using the supplied data.

The cause lies in the Microsoft OLE DB Driver for SQL Server (MSOLEDBSQL), which PVS uses to communicate with its SQL database.

The decisive trigger?

vDisk version number 20!

When a PVS target starts or stops, PVS writes a license usage record to the database. This record also includes the version number of the vDisk in use.

If that version number is exactly 20, the driver transmits the value incorrectly.

SQL Server rejects the operation with Error 8023.

PVS interprets this error as a loss of database connectivity and briefly goes offline.

In the investigated environment, exactly one active vDisk was running version 20. This also explained why only the associated targets were affected.

🛠 The workaround

The solution is surprisingly straightforward:

✅ Do not use vDisk version 20 in production.
✅ Deploy a newer version, 21 or higher.
✅ Alternatively, merge the vDisk versions as appropriate.
✅ For other vDisks, avoid keeping version 20 in use long-term.

Important: this is not a general SQL connectivity issue. Restarting SQL Server or adjusting network timeouts does not eliminate the underlying trigger.

📌 Vendor status

Citrix has reproduced the behavior in its lab.

A permanent fix is planned for a future PVS release.

💡 My takeaway

A single version number can be enough to cause brief PVS database connectivity failures.

If you see PVS Events 201/214 together with SQL Error 8023, check the vDisk versions in use as well.

The number 20 certainly would not have been my first suspect. 😉

Finding in the Wild | Citrix MCS – Windows Rearm Failure After November 2026 Updates

I’ve recently encountered the same issue at two of my customers:

After installing the November 2026 Windows updates, image preparation through Citrix Machine Creation Services (MCS) fails.

And apparently, I’m not the only one. Several administrators have reported similar issues in the comments on Günter Born’s blog.

⚠️ Windows Updates Under Investigation:

  • Windows Server 2019 – KB5131085
  • Windows Server 2022 – KB5131090
  • Windows Server 2025 – KB5131080

🔍 The Issue

MCS image preparation fails with the following error:

Image preparation failed to rearm the copy of Windows installed on the master image.

As a result, the updated master image cannot be deployed successfully.

🔬 Technical Analysis

The failure occurs during the Windows rearm operation as part of the MCS image preparation process.

Whether this is caused by changes to the Windows Software Protection Service, Windows activation mechanisms, or the interaction between Windows and Citrix MCS remains unclear.

The timing strongly suggests a connection to the November Patch Tuesday updates, but correlation alone does not establish the root cause.

🛠️ My Recommendations

1️⃣ Install the November updates on test master images first.

2️⃣ Validate the complete MCS image preparation process — not just whether Windows boots successfully.

3️⃣ If preparation fails, investigate Citrix ProvTask details, preparation VM logs, and Windows activation events.

4️⃣ Keep the last known-good master image snapshot available for rollback.

5️⃣ Postpone production Machine Catalog updates until the updated image has been successfully validated.

I would also avoid manually modifying slmgr /rearm or Windows activation settings until the underlying cause has been identified.

❗ Current Status

I’ve reproduced this issue in two customer environments, and several similar reports have appeared in the community.

As of now, there is no official confirmation or documented fix from Citrix or Microsoft.

Has anyone identified a reproducible root cause or a working workaround?

I’m particularly interested in the CVAD versions and Windows activation methods (KMS, MAK, or ADBA) used in affected environments.

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 | NetScaler 14.1-73.33+ – Security Patch Installed, and Suddenly the ICA Session Is Gone?

Many NetScaler administrators are currently likely to be updating their appliances to 14.1-73.33 or later because of current security issues. And, of course, the recommendation remains: 👉 Install security updates! However, the release notes contain a small detail

Many NetScaler administrators are currently likely to be updating their appliances to 14.1-73.33 or later because of current security issues.

And, of course, the recommendation remains:

👉 Install security updates!

However, the release notes contain a small detail worth knowing before the maintenance window.

ICA Proxy sessions may lose their ability to reconnect

The scenario:

A user starts a Citrix session before the NetScaler upgrade.

The session continues running on the VDA.

The NetScaler is then updated to 14.1-73.33+.

When the user subsequently tries to reconnect to the existing session:

💥 Reconnect fails.

The reason is the session tickets issued before the upgrade.

They can no longer be used for reconnection after the upgrade. The user must start a new session.

The good news:

This is not a general ICA Proxy issue after the upgrade.

Sessions started after the upgrade work normally, including subsequent reconnects.

No additional configuration is required.

The affected transition is:

Pre-upgrade session → upgrade → post-upgrade reconnect

Why does this matter?

We normally perform NetScaler HA upgrades with as little user impact as possible:

Upgrade secondary → failover → upgrade primary.

It is easy to assume:

HA upgrade without downtime = users notice nothing.

That is not necessarily true here.

The infrastructure may be fully available while existing ICA sessions are still affected at the next reconnect.

🔥 Zero-downtime HA upgrade ≠ zero user impact

My recommendation

When upgrading to 14.1-73.33+:

👉 Account for existing ICA sessions
👉 Inform users about possible session loss
👉 Prepare the service desk accordingly
👉 Perform the upgrade outside productive usage hours where possible

This small detail can become particularly relevant in 24/7 environments.

Takeaway

Of course, this is no reason to postpone a security update.

But it demonstrates again:

Sometimes the most interesting findings are not in the security bulletin, but somewhere in the release notes. 😉