Share via

Logout stuck on Windows Server 2025

Carisch Benjamin 10 Reputation points
2025-09-03T12:26:04.17+00:00

We use Windows Server 2025 with FSLogix and Citrix. Now and then we have stuck logout sessions where the following 5 Services are still running but you can't see the Session owner.

User's image

In this situations the RW-Disk from the FSLogix-Profile is still in use and the user can't login with its profile again. The only way to fix this is to reboot the server. We also haven't fount any helpfull logs - maybe also because we don't know where the problem starts.

Also the diskmanagement is not available in this situation - you can access it but the disks are not loading.

If this occures it seems that the server has the issue - because after a while other sessions get the same problem while on the other servers of the delivery group everything is fine.

We really need help because it's getting more and more problems. thanke

Windows for business | Windows Server | User experience | Accessibility

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. PK 0 Reputation points
    2026-01-14T10:19:23.1866667+00:00

    Hello,

    we got the same issue,

    any solutions for this issue?

    greetings and ty

    0 comments
  2. Domic Vo 20,250 Reputation points Independent Advisor
    2025-09-03T13:32:05.0766667+00:00

    Dear Carisch Benjamin,

    Based on similar cases and current guidance, we suggest the following steps:

    1. Restart FSLogix Services Instead of Rebooting In many cases, restarting the FSLogix Apps Services (frxsvc) can release hung sessions and dismount the RW-Disk without requiring a full server reboot.
    2. Update FSLogix to the Latest Version Ensure you're running the latest FSLogix build, as recent updates have addressed container lock and session cleanup issues. You can find the latest version and release notes on FSLogix Known Issues.
    3. Disable Stale Session Cleanup via GPO (If Enabled) Some environments have resolved similar issues by disabling the FSLogix stale session cleanup policy. This can be done via Group Policy:
      • Code 
             Computer Configuration > Administrative Templates > FSLogix > Profile Containers
        Set "Enable session cleanup" to Disabled and monitor behavior.
    4. Review Event Logs for Session Termination Check for Event IDs such as 4647, 4634, and FSLogix-specific logs under:
      • Code 
             Event Viewer > Applications and Services Logs > FSLogix
        These may help identify the root cause or timing of the failure.
    5. Disk Management Delay The unresponsive Disk Management may be a symptom of the RW-Disk being locked by orphaned processes. Consider using diskpart or PowerShell (Get-Disk) to verify disk status when GUI tools fail.
    6. Isolate Server Behavior Since the issue is isolated to specific servers, we recommend comparing patch levels, Citrix policies, and FSLogix configurations across affected and unaffected hosts.

    We understand this issue is escalating and affecting user productivity. If the problem persists after applying these steps, we recommend opening a support case with full FSLogix logs and session details for deeper analysis.

    I hope this helps. Just kindly tick Accept Answer that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

    Best regards,

    Domic Vo

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.