Finding in the Wild | Microsoft Teams Is Installed, but Unavailable to the User

An issue I encounter repeatedly in Citrix VDI environments: Microsoft Teams is installed in the master image and works for the administrator. After MCS or PVS provisioning, however, users cannot start Teams. ❌ Teams is missing from the

An issue I encounter repeatedly in Citrix VDI environments:

Microsoft Teams is installed in the master image and works for the administrator. After MCS or PVS provisioning, however, users cannot start Teams.

❌ Teams is missing from the Start menu
❌ The application does not start
❌ Only some users are affected
❌ Reinstallation helps only temporarily

The cause? Often, missing MSIX registration in the user context.

New Teams is based on MSIX. System-wide provisioning and per-user registration must be distinguished.

An installed package does not automatically mean Teams is available to every user.

🔍 1️⃣ Check Teams provisioning

2️⃣ Registration in the user context

3️⃣ Analyze AppX errors

🛠️ 4️⃣ My workaround: register Teams again at logon

At several customers, I was able to resolve the issue by registering Teams again during user logon.

Run a scheduled task in the user context:

The command registers the already provisioned Teams package again for the signed-in user.

Important: the task must run in the relevant user’s context. It does not replace missing system-wide Teams provisioning.

🔧 5️⃣ FSLogix and Citrix UPM

Also check the following settings:

✔ FSLogix InstallAppxPackages
✔ Current FSLogix/UPM versions
✔ UWP app roaming in Citrix UPM
✔ AppX/MSIX permissions
✔ DisableAppInstallsOnFirstLogon
✔ Profile persistence and exclusion lists

The logon task is an effective workaround for missing user registration. In the longer term, however, the cause in profile management or the AppX registration process should be addressed.

💡 My takeaway

Installed ≠ provisioned ≠ registered.

In non-persistent Citrix environments in particular, registering Teams again at logon can make the decisive difference.

I have published a complete guide to installation, optimization, profile configuration and troubleshooting here:

Finding in the Wild | Secure Boot – The Certificate Has Expired, but Windows Still Starts

On October 19, 2026, the Microsoft Windows Production PCA 2011 certificate expired after 15 years. Nevertheless, Windows servers, virtual machines and workstations continue to start normally. The actual problem will emerge with future updates. 🔍 What has Microsoft

On October 19, 2026, the Microsoft Windows Production PCA 2011 certificate expired after 15 years.

Nevertheless, Windows servers, virtual machines and workstations continue to start normally.

The actual problem will emerge with future updates.

🔍 What has Microsoft changed?

Microsoft has frozen bootloaders signed with PCA 2011.

This means:

* Existing Windows installations continue to boot.
* Regular Windows updates generally continue to work.
* New bootloader security fixes use the Windows UEFI CA 2023 certificate chain.
* Future installation media increasingly rely on the new certificate chain.

Systems that trust only the old certificate gradually lose important security updates for the boot process.

⚠️ Particularly relevant for virtualized infrastructure

This issue should not be underestimated with Hyper-V, VMware vSphere, Citrix MCS and golden images.

A fully patched Windows installation does not automatically mean that the virtual UEFI firmware supports the new certificates.

Hyper-V Generation 2: certificate updates are delivered through Windows servicing.

VMware vSphere: the ESXi version and virtual hardware must support the new certificates.

Golden images: the bootloader trust chain must also be correct.

🛠️ What should you check?

An initial PowerShell test:

But be careful: True confirms only that Secure Boot is enabled, not whether Windows UEFI CA 2023 has already been installed.

Also:

✅ Check the UEFI certificate status

✅ Check hypervisor and VM hardware versions

✅ Test installation and recovery media

✅ Back up BitLocker recovery keys before making changes

✅ Check WDAC/App Control policies for dependencies on PCA 2011

🔬 An often overlooked detail

Windows Defender Application Control (WDAC) may also be affected.

If old Microsoft certificates are explicitly embedded in policies, updated Windows components may be blocked in the future.

Event ID 3077 in the Code Integrity event log can indicate such blocks.

💡 My takeaway

Secure Boot enabled ≠ Secure Boot ready for future updates.

Certificate expiration does not cause an immediate boot failure, but it changes the foundation for future bootloader updates.

Especially in virtualized infrastructure, the firmware trust chain should therefore be checked alongside the Windows patch level.

Finding in the Wild | Windows 11 26H2 – Black Screens and Endless Citrix Logons

Problems in Citrix environments are increasing after Windows updates: ❌ Logon hangs at Welcome or Please wait ❌ A black screen appears after successful logon ❌ Explorer does not start ❌ User profiles are not fully loaded The

Problems in Citrix environments are increasing after Windows updates:

❌ Logon hangs at Welcome or Please wait
❌ A black screen appears after successful logon
❌ Explorer does not start
❌ User profiles are not fully loaded

The problem: identical symptoms, different causes.

Several known issues currently fit this pattern:

1️⃣ Windows Shell / explorer.exe
Microsoft confirms Explorer issues after logon, particularly in virtual Windows 11 environments using FSLogix.
✅ Fix: KB5127648 (October 2026).

2️⃣ Citrix UPM – UPM-13949
On Windows 11 26H2, new user profiles on MCS machines may hang during the first logon. The profile folder is created, but logon does not complete. Existing profiles work.
⚠️ Citrix is investigating.

3️⃣ FSLogix – profile containers
Possible causes include delayed VHDX mounting, SMB latency, storage bottlenecks, locked containers, permissions or antivirus interference.

4️⃣ Citrix UPM – profile store
Incorrect NTFS or share permissions after profile migrations may prevent correct profile initialization.

5️⃣ Citrix VDA – registration issues
After KB5127648, VDAs may remain stuck at Registering. BrokerService reports errors including SecurityNegotiationException.
➡️ Citrix documents a registry workaround.

6️⃣ Remote Desktop Services
After certain Windows updates, TermService may hang. Sessions remain at Connecting and new connections fail.

7️⃣ MCS master image
If all machines are suddenly affected, compare the Windows build, VDA version, GPOs, logon scripts and last working snapshot.

🔧 My troubleshooting approach:

✔ Is the VDA registered?
✔ Has the session actually started?
✔ Is a new or existing profile affected?
✔ Has the FSLogix VHDX or UPM profile loaded?
✔ Are there User Profile Service errors?
✔ Has explorer.exe started or crashed?
✔ Have Windows updates and the VDA version been checked?
✔ Are individual VDAs or the entire MCS catalog affected?

💡 Takeaway

A black screen is a symptom, not a diagnosis.

Investigating only FSLogix while Explorer is crashing or the VDA is not registered wastes valuable time.

First identify the point at which logon fails. Then address the cause directly.

Finding in the Wild | Citrix Workspace App 2610 – A Client Update with Side Effects?

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

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.

Finding in the Wild | Citrix HDX Direct – Repeated Disconnects Caused by a Cipher Mismatch

Citrix sessions repeatedly disconnect and automatically reconnect for no apparent reason. The first assumption? Network issues, packet loss, firewalls or an unstable UDP connection. But the cause does not always lie in the network. 🔎 The problem Using

Citrix sessions repeatedly disconnect and automatically reconnect for no apparent reason.

The first assumption?

Network issues, packet loss, firewalls or an unstable UDP connection.

But the cause does not always lie in the network.

🔎 The problem

Using EDT (Enlightened Data Transport) over HDX Direct can result in repeated session disconnects and reconnects.

The interesting part: the connection is established, but does not remain stable.

Citrix documents this behavior under issue CVADHELP-29336.

🛠️ The cause

A cipher mismatch when using EDT over HDX Direct.

The cause is therefore not necessarily poor network quality, but a problem negotiating or using encryption.

This makes troubleshooting particularly interesting because the initial symptoms strongly resemble a conventional network issue.

💡 What should you check?

✅ Is the affected session actually using EDT over HDX Direct?

✅ Do disconnects occur only with UDP/EDT?

✅ Does the same session remain stable over TCP?

✅ Do Citrix diagnostic data indicate transport or encryption errors?

✅ Which VDA version and cumulative update level are installed?

Important: switching to TCP can help narrow down the issue, but is not a permanent solution to the underlying problem.

🔧 The fix

Citrix lists CVADHELP-29336 in the fixed issues for Citrix Virtual Apps and Desktops 2507 LTSR CU1.

🎯 My takeaway

Not every Citrix reconnect is a network issue.

With EDT, HDX Direct and multiple transport paths, troubleshooting is becoming increasingly complex.

If TCP is stable but EDT constantly reconnects, investigate known Citrix transport issues as well as firewalls and packet loss.