Forum Discussion
FSLogix v3 25.02 profiles not unloading
Hi all!
Like mentioned in the comments in the FSLogix Blog: FSLogix v3 Release 25.02 is now generally available! | Microsoft Community Hub
Disks are not unloaded on logoff and the excluded conten (local_%username%) remains on the Worker.
Eventlog shows:
Event source: Apps (Microsoft-FSLogix-Apps)
Event id: 26
invalid map<K, T> key (An exception occurred in the service when handling the control request.)Event source: Apps (Microsoft-FSLogix-Apps)
Event id: 42
SessionId: 3, ErrorCode: 1064, Detail: Logoff failed, Please check logs and tracelogging and verify that the users disk was detached.Event source: Apps (Microsoft-FSLogix-Apps)
Event id: 26
UnloadProfile failed. Version: 3.25.202.4223. User: <user>. SID: <SID>. SessionId: 3. FrxStatus: 1064 (An exception occurred in the service when handling the control request.)
Best regards,
Jan
4 Replies
- Ken_ZBrass Contributor
Hi everyone
is this on Server 2019 RDS or Windows 10 (older versions)?
I had this issue with HF4 and traced it to some folders in my redirections.xml file.
As administrator, go into the local_%username% folder, and try deleting everything. Some things will delete, some won't as they're locked by the System. delete everything you possbly can, and then what's left, remove them from the redirections.xml file, and hopefully that should fix your issue.
Regards
Ken Z
- skylerkincaidCopper Contributor
We are using Windows 11 Multi-Session with AVD.
- skylerkincaidCopper Contributor
We are seeing the exact same events. Typically, it is prefaced with the staff member reaching out because application just randomly started locking up. The other nine staff on the server have no issues. Even if they log out, the server has the files locked and we have to use Powershell to unlock them so they can sign in again.
We had this issue before the 25.02 update but were hoping that the update would solve it. - AptitudeLogicielsCopper Contributor
We have the same issue. All servers upgraded to version 3.25 can log in normally, but upon logging out, the profile disk remains stuck, making it impossible to log in again. The only solution we've found is to restart the server. We're rolling back to the previous version—thank you, Microsoft, for this wonderful update...