Intermittent FSLogix Profile Issues in AVD – Users Not Getting Latest Data Until Session Host

Question

Hi Team,

We have multiple Azure Virtual Desktop (AVD) pooled host pools with FSLogix** Profile **Containers configured.

We are experiencing an intermittent issue where some users do not see their latest profile data (Desktop files, and save data) after logging in.

Observed Behavior

1. A user logs in but does not see their latest profile data.
2. We forcefully log off the user's session from the backend.
3. After the user reconnects, in many cases the profile loads correctly and the data becomes available.

However, for some users:

1. Even after forcefully logging off their session, they are assigned back to the same** session host ****(VM)**.
2. The issue persists until we place that specific session host into Drain** **Mode.
3. Once the host is in Drain Mode and the user reconnects to a different session host, their profile and data load correctly.

Questions

• What could be the root cause of this behavior?
• Could this indicate an FSLogix profile container locking or mounting issue on a specific session host?
• Is AVD session reconnection behavior causing users to be redirected back to the same problematic VM?
• What logs (FSLogix, Event Viewer, AVD diagnostics, Azure Files/ANF logs, etc.) should we review to identify the exact cause?
• What is the recommended long-term solution to prevent users from experiencing this issue?

Environment

• Azure Virtual Desktop (pooled host pools)
• FSLogix Profile Containers enabled
• Multiple session hosts per host pool

Any guidance or troubleshooting recommendations would be greatly appreciated.

Thank you.

Answer 1

hi shamim & thx for sharing urs issue here at Q&A portal,

fact that the problem follows a specific session host is the biggest clue. If users get their latest profile as soon as they land on a different host, I'd suspect an FSLogix issue on that VM rather than AVD itself. That could be a profile container not detaching cleanly, mount failures, stale handles, or storage connectivity problems.

I'd start by comparing a healthy host with the problematic one

FSLogix logs (C:\ProgramData\FSLogix\Logs\Profile)

Event Viewer > Applications and Services Logs > FSLogix

AVD diagnostics to confirm whether users are reconnecting to an existing session

Storage latency/connectivity if you're using Azure Files or ANF

See whether the affected users still have a disconnected session on that host. If AVD reconnects them to an existing session, they'll keep hitting the same problem until that host is out of rotation.

https://learn.microsoft.com/azure/virtual-desktop/diagnostics-log-analytics

If the issue is consistently isolated to one or two session hosts, I'd focus on why those hosts aren't releasing or mounting profile containers correctly rather than looking at the host pool as a whole.

rgds,

Alex

&

If my answer was helpful pls mark it and additional thx if u follow me at Q&A portal

and at my blog https://ctrlaltdel.blog/