Category: FSLogix 7 posts

Finding in the Wild | FSLogix Black Screen – Microsoft Releases a Fix

A black screen after Windows logon? No desktop or taskbar, and explorer.exe does not start? These symptoms appeared after the August and September 2026 Windows updates in certain virtual desktop environments using FSLogix. ⚠️ The problem Users could

A black screen after Windows logon? No desktop or taskbar, and explorer.exe does not start?

These symptoms appeared after the August and September 2026 Windows updates in certain virtual desktop environments using FSLogix.

⚠️ The problem

Users could log on successfully, but the screen then remained black.

Typical symptoms:

* explorer.exe does not start or crashes repeatedly.
* The Windows Shell does not fully initialize.
* The desktop remains black or appears only after a long delay.

✅ The solution: update Windows and FSLogix

Microsoft released a correction with Patch Tuesday on October 13, 2026.

1️⃣ Install the Windows update

KB5127648 for Windows 11 24H2, 25H2 and 26H2.

2️⃣ Update FSLogix

Update to FSLogix 26.08 (3.26.826.17182).

This version includes additional improvements and fixes. Updating FSLogix is a supplementary recommendation; the officially confirmed black-screen fix is delivered through the Windows update.

3️⃣ Validate logon

After the update:

* Restart the VDA.
* Test logon with existing FSLogix profile containers.
* Check Application Events 1000/1001 for explorer.exe crashes.
* Check the FSLogix profile logs.
* If applicable, withdraw deployed Known Issue Rollback (KIR) policies after successful testing.

💡 Finding in the Wild

A black screen in a Citrix environment does not automatically mean the Citrix VDA, HDX or profile containers themselves are the cause.

In this case, the documented cause lies in Windows Shell initialization.

My recommendation: update and test Windows and FSLogix versions together on a pilot VDA before deploying changes to production.

🔗 Microsoft sources:

Windows fix:

October 13, 2026 – KB5127648 (OS Builds 26300.9711, 26200.9711 and 26100.9711) | Microsoft Support
October 13, 2026 – KB5127648 (OS Builds 26300.9711, 26200.9711 and 26100.9711)

FSLogix release notes:

FSLogix Release Notes – FSLogix
Provides a list of updates, changes, and fixes in FSLogix official releases.

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:

Installing New Microsoft Teams (Version 2) in Citrix
The new version of Microsoft Teams, often called Teams 2.0, has been the new standard since July 1, 2024. For VDI environments, this means there is no going back.

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.

MSIX App Attach with Windows 10 Version 2004 in Citrix Environments

With the latest version of Windows 10 (version 2004) it is finally possible to use MSIX App Attach in Citrix without any special adaptation.

MSIX App Attach allows you to store applications for virtual environments outside a virtual machine in a VHD/X file. Such an application can thus be integrated into the user session if required.

What is MSIX App Attach ?

MSIX App Attach is based on the concept where the application is stored in MSIX format in a central location and integrated into the operating system. After embedding, applications look like locally installed applications to both the user and the operating system. When combining FSLogix Profile Containers and MSIX App Attach, the Golden Master Image’s operating system remains completely clean and data, profiles and applications are completely separated.

Continue reading “MSIX App Attach with Windows 10 Version 2004 in Citrix Environments”

FSLogix App Masking in Citrix Environments

What is App Masking and what do we need it for?

App Masking minimize the number of Golden Images required, by allowing all applications to be installed in a single Golden Image. The mapping and separation of applications (as well as printers, fonts, office add-ins, Internet Explorer plug-ins, etc.) is done without packaging, sequencing, backend infrastructure or virtualization.

FSLogix App Masking

This is achieved by granular access control of the installed applications through App Masking Rules. These rules can be used to completely hide the application in an user runtime, so that it no longer appears in the file system, registry or under programs and features.

Because no additional ressources are required by the system when using the rules, applications run at their native speed.

Continue reading “FSLogix App Masking in Citrix Environments”