Hi all, I'm currently facing some challenges with my FSLogix deployment in a Remote Desktop environment. Here's a quick overview: we have a storage server for FSLogix user profiles which all connect through a Remote Desktop Gateway, using four Windows Server 2025 Standard servers for around 90 users. Daily, some users report that their Remote Desktop session gets stuck on 'Please wait for FSLogix app service.' When this occurs, attempting to disconnect them leads to ghost sessions, with no user listed in Task Manager and lingering system processes that are tough to terminate. We've attempted various troubleshooting steps, including cleaning up sessions and adjusting GPO settings, but solid solutions remain elusive, and often users have to wait for a random timeout to clear their sessions. We're also comparing the setup with another environment running Windows Server 2022 that doesn't have these issues. Any advice or insights would be greatly appreciated!
5 Answers
Have you considered adding an exclusion for the FSLogix profiles folder in your Defender antivirus settings? Disabling on-access scans for that folder could help mitigate the problem.
From my experience, this issue isn’t exclusive to FSLogix; I’ve had similar problems with standard User Profile Disks on Server 2025. It appears to be a bug that hasn't been resolved yet, unfortunately.
Make sure you’re using the latest ADMX templates for your Group Policy settings. It can make a difference. You can find the details here: https://learn.microsoft.com/en-us/fslogix/how-to-use-group-policy-templates. Just share your GPO settings to see if something’s missed!
I suggest setting up configurations to force logoff or force kill processes during user sign-out. It might help in getting rid of those ghost sessions more effectively.
Before diving deeper, check the Known Issues section related to FSLogix. There might be something listed that relates to your issue. It’s worth a look!
That's frustrating to hear. I was hoping it was something specific to FSLogix, but maybe I'll need to consider other workarounds then.