Why do users get a temporary profile with FSLogix?

Because FSLogix couldn't attach their container and, by default, lets Windows sign them in anyway. The usual causes are a share the host can't reach or that denies the user, a container still locked by another session, a full share, a local profile that already exists, or FSLogix not being enabled on that host. The FSLogix profile log shows which.

How do I fix "VHDX is locked" or error 33 in FSLogix?

Find and sign out the user's other session. If there isn't one, the lock is orphaned: close the open handle on the VHDX with Close-AzStorageFileHandle (Azure Files) or from Open Files on a Windows file server. Then make sure backup and antivirus tools exclude the share's VHDX files.

What is the default FSLogix container size?

SizeInMBs defaults to 30000, about 30 GB. Containers are dynamic by default, so each only uses the space it needs on the share up to that limit. You can raise the limit at any time, and existing containers grow at the next sign-in, but you can't lower it.

What happens when the FSLogix file share is full?

New users can't create a container and get temporary profiles, existing sessions can hang, and sign-outs can fail to write back or detach. Raise the share's quota first, then find out what filled it.

Where are the FSLogix logs?

Text logs are in C:\ProgramData\FSLogix\Logs, with profile sign-in logs in the Profile subfolder. Event logs are in Event Viewer under Applications and Services Logs → FSLogix.

Is frxtray still available?

No. Microsoft retired the FSLogix Profile Status tool (frxtray.exe) in FSLogix 25.02 in February 2025. Use the profile logs and the per-session values in the registry instead.

Does the 2026 Kerberos RC4 change affect FSLogix?

It can. From the April 2026 Windows update, domain controllers default to AES instead of RC4 for accounts without explicit encryption types. Azure Files or file servers joined to AD DS that only support RC4 stop authenticating, and users get access denied. Make sure the storage account's AD object supports AES and rotate its password.

Do I need Cloud Cache?

Only if you need the profile to survive a storage account or region outage. Cloud Cache adds a local cache, more storage cost and more ways to fail. Microsoft recommends the Standard configuration for most deployments.

FSLogix Troubleshooting: The Profile Errors That Actually Happen and How to Fix Them

The FSLogix profile errors that actually happen on Azure Virtual Desktop, each with the symptom, cause and fix: temporary profiles, locked VHDX files, full containers and shares, Azure Files permissions and Kerberos, slow attach, Cloud Cache and antivirus. Plus where the logs live, how to read the error codes, and how to stop the tickets coming back.