Multiple sessions for users in AVD, FSLOGIX is Unable to logoff user session from SA-AVD-004

Question

Multiple sessions for users in AVD, FSLOGIX is Unable to logoff user session from SA-AVD-004

Chelsea Tech 0

Manish Deshpande 6,340 Reputation points Microsoft External Staff Moderator

2026-05-01T20:38:55.38+00:00
Hi Chelsea,

When a session is disconnected but not properly logged off, FSLogix leaves the user's VHDx container mounted on that host. If the user then reconnects to a different host, FSLogix cannot attach the profile disk because it's still in use especially when "Prevent login with temporary profile" is enabled. This is typically why FSLogix appears "stuck" and can't log off the session from SA-AVD-004.

Step 1 — Configure RDS Session Time Limits via GPO (Most Important Fix)

To ensure disconnected or idle sessions are properly logged off and to allow FSLogix to cleanly detach the user's profile disk, configure the following Group Policy settings:

Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Session Time Limits

Set these policies on your session host OU:

Set time limit for disconnected sessions → e.g., 15–30 minutes

Set time limit for idle Remote Desktop Services sessions → e.g., 1–2 hours

End session when time limits are reached → Enabled

Without the "End session" setting, sessions may remain in a disconnected state but not actually terminate — which is what keeps the FSLogix container locked.

Step 2 — Enable CleanupInvalidSessions Registry Key

In cases where a user's session terminates abruptly, the VHD(x) mounted for the user's profile isn't properly detached, and the user's next sign-in may not successfully attach their container. Enabling CleanupInvalidSessions causes FSLogix to attempt to clean up these invalid sessions and allow a successful sign-in. Microsoft Learn

Set the following registry key on all session hosts:

HKLM\SOFTWARE\FSLogix\Apps Value: CleanupInvalidSessions = 1 (DWORD)

Note: This key should not be used in conjunction with Cloud Cache when concurrent sessions (using ProfileType/VHDAccessMode) are in use.

Step 3 — Configure ProfileType for Multiple Sessions (if users need concurrent access)

If users legitimately need to connect from multiple hosts simultaneously, multiple connections are supported using VHD(x) differencing disks. To enable this, ProfileType must be set to 3 (Try Read/Write, fall back to Read-Only).

Registry path:

HKLM\SOFTWARE\FSLogix\Profiles Value: ProfileType = 3 (DWORD)

All sessions trying to use the VHD concurrently must have a matching ProfileType setting. If the VHD isn't accessed concurrently, ProfileType should be 0.

Step 4 — Check for Stuck Processes on the Session Host

If a specific user is stuck, running qwinsta on the session host will show all connected sessions including those in an "Unknown" state. Once identified, you can attempt logoff <session ID>from an elevated command prompt. If that fails with Access Denied, use query process /id:<sessionID> to find hanging processes and terminate them with taskhill.

https://learn.microsoft.com/en-us/fslogix/concepts-multi-concurrent-connections

https://learn.microsoft.com/en-us/fslogix/reference-configuration-settings?tabs=profiles

https://learn.microsoft.com/en-us/fslogix/troubleshooting-events-logs-diagnostics

Thanks,
Manish.
Manish Deshpande 6,340 Reputation points Microsoft External Staff Moderator

2026-05-05T01:10:45.7266667+00:00

Hello Chelsea,

I wanted to check if my last response made sense. I’d be glad to assist further or explain anything in more detail and please accept as Yes and upvote if the answer is helpful so that it can help others in the community.
Manish Deshpande 6,340 Reputation points Microsoft External Staff Moderator

2026-05-06T19:19:34.5133333+00:00

Hello @Chelsea Tech ,

I wanted to check if my last response made sense. I’d be glad to assist further or explain anything in more detail and please accept as Yes and upvote if the answer is helpful so that it can help others in the community.

2 answers

Your answer

Manish Deshpande 6,340 Reputation points Microsoft External Staff Moderator

2026-05-05T01:10:45.7266667+00:00

Hello Chelsea,

I wanted to check if my last response made sense. I’d be glad to assist further or explain anything in more detail and please accept as Yes and upvote if the answer is helpful so that it can help others in the community.
Manish Deshpande 6,340 Reputation points Microsoft External Staff Moderator

2026-05-06T19:19:34.5133333+00:00

Hello @Chelsea Tech ,

I wanted to check if my last response made sense. I’d be glad to assist further or explain anything in more detail and please accept as Yes and upvote if the answer is helpful so that it can help others in the community.

Answer 1

Hey Chelsea, it sounds like FSLogix is unable to detach the user’s profile VHD on SA-AVD-004 because a previous session is still “in use.” When a user disconnects without actually logging off, FSLogix leaves the VHD mounted and locked—so any new or second session can’t attach and you can’t cleanly log them off. Here’s what you can try:

Configure session time-outs in Group Policy • Open your Session Host OU GPO under Computer Configuration → Administrative Templates → Windows Components → Remote Desktop Services → Remote Desktop Session Host → Session Time Limits • Set “Set time limit for disconnected sessions” (e.g. 15–30 minutes) • Set “Set time limit for idle Remote Desktop Services sessions” (e.g. 1–2 hours) • Enable “End session when time limits are reached” This makes sure disconnected sessions are terminated and FSLogix can detach the VHD.
Enable automatic cleanup of invalid sessions • On all session hosts, create or set the DWORD CleanupInvalidSessions = 1 under HKLM\SOFTWARE\FSLogix\Apps • This tells FSLogix to find and clear orphaned mounts on next sign-in.
If you need true concurrent sessions on the same profile • Under HKLM\SOFTWARE\FSLogix\Profiles, set ProfileType = 3 (Try Read/Write, fall back to Read-Only) on every host. • Only use this if you really intend multiple simultaneous logins; otherwise leave ProfileType = 0.
Manually identify and clear stuck sessions/processes • From an elevated prompt on SA-AVD-004 run: qwinsta /server:SA-AVD-004 → Note SessionID(s) in “Disc” or “Unknown” state logoff <SessionID> /server:SA-AVD-004 • If you get Access Denied, run query process /id:<SessionID> → Kill hanging processes with taskkill • Or use the Azure Portal → Host pools → Session hosts → Log off each session for the affected user, then wait ~60 sec for the VHD to release.
Review FSLogix logs for error codes • Open Event Viewer > Applications and Services Logs > FSLogix > Operational • Look for Event ID 33 (VHD attach failure) or 25 (profile load failure) with “locked” in the message • That confirms the disk is still in use

Hope that helps! If you still see issues, could you share:

• The output of qwinsta/query user on SA-AVD-004

• Any FSLogix error codes from the Operational log

• The current values of CleanupInvalidSessions and ProfileType in your registry

• Your FSLogix version

Reference List

RDS Session Time Limits (GPO) https://learn.microsoft.com/windows-server/remote/remote-desktop-services/remote-desktop-session-host/manage-session-time-limits
CleanupInvalidSessions https://learn.microsoft.com/fslogix/reference-configuration-settings#cleanupinvalidsessions
Concurrent/multiple connections https://learn.microsoft.com/fslogix/concepts-multi-concurrent-connections
FSLogix troubleshooting & logs https://learn.microsoft.com/fslogix/troubleshooting-events-logs-diagnostics

Note: This content was drafted with the help of an AI system. Please verify the information before relying on it for decision-making.

Answer 2

Hello

Welcome to the Microsoft Azure Community

Good afternoon. Thank you for contacting us and detailing your scenario. This error occurs when FSLogix cannot correctly terminate the user profile on the host SA-AVD-004, usually due to a stuck session, locked VHDX, SMB/Azure Files storage, or FSLogix version. Quick suggestions:

Execute the following command in PowerShell to check for disconnected sessions, typing the commands one by one, followed by Enter:

query user

qwinsta

logoff IDSSESSION

Update FSLogix and validate Defender exclusions.
Check Azure Files/SMB connectivity/performance.
Compare SA-AVD-004 with the other hosts in the pool.

Let us know the result.

Reference technical documentation:

https://learn.microsoft.com/en-us/fslogix/troubleshooting-container-locked

https://learn.microsoft.com/en-us/fslogix/troubleshooting-error-codes

If the answer helped solve the problem, please mark it as a Helpful Answer. This action closes the thread, indicates the correct solution, and helps others with the same question find the answer more easily. If you still need support or have new questions, feel free to use this same post.

Share via

Multiple sessions for users in AVD, FSLOGIX is Unable to logoff user session from SA-AVD-004

2 answers

Your answer