FsLogix - Unclean logoff causing locked files until server reboot

Much R 101 Reputation points
2021-01-13T16:29:50.18+00:00

Problem is described by M4deman under unclean-logoff-causing-locked-files-until-server-reboot

It seems to have something to do with the 2009 version.
The latest version of FSLogix is installed whats-new

Description

After a user logoff, the "System" Process (PID 4) locks the following folders:

C:\Users\local_username\AppData\Local\Microsoft\Credentials
C:\Users\local_username\AppData\Roaming\Microsoft\Credentials

The user is completely logged of, according to Task Manager.

In the FSLogix Profile Log file I can see the following:

[07:53:55.601][tid:00000c90.0000ce44][ERROR:00000020] Delete profile failed for sid S-1-5-21-3364776539-3721753400-1968955100-1179, Cleaning up manually. (Der Prozess kann nicht auf die Datei zugreifen, da sie von einem anderen Prozess verwendet wird.)
The last sentence means that the process cannot access the file, because another process already uses it.

Also the whole "local_username" folder cannot be deleted:

[08:23:15.479][tid:00000c90.0000bcc4][WARN: 00000005] Failed to delete C:\Users\local_usename (Access is denied)
Access Denied

Does someone have any info on this behaviour?

Windows for business | Windows Client for IT Pros | User experience | Remote desktop services and terminal services
Windows for business | Windows Client for IT Pros | User experience | FSLogix
{count} votes

107 answers

Sort by: Most helpful
  1. Marius Neuhaus 1 Reputation point
    2021-03-11T07:41:48.95+00:00

    Hello,

    I have created a ticket.
    I hope microsoft will get back to me quickly.
    I'll post updates and soultions from microsoft.

    I'm curious, for the answer.

    Best Regards,
    Marius


  2. bjkoekkoek 1 Reputation point
    2021-03-16T07:32:08.713+00:00

    We are encountering the same issues with the locked credentials folder in the local_ user folder on windows server 2019 and the latest version of FSLogix.

    0 comments No comments

  3. Mihail Gusev 1 Reputation point
    2021-03-16T08:25:34.39+00:00

    Hi,
    I had the same problem with locked vhdx, but now it seems to be working fine. My RDS farm has been working for 1,5 month without the issue. I have several On-Prem RDSH servers besed on Server 2019 Std with latest FSlogix agent 2.9.7654.46150.

    I faced the issue with locked vhdx after I updated FSLogix agent from 2.9.7349.30108 to 2.9.7621.30127. To reslove the issue I turned on CleanupInvalidSessions reg key and updated FSLogix agent to 2.9.7654.46150. After that I haven't seen the issue with locked vhdx.

    I've opened a case in MS support, but they didn't help me, becasue the issue gone away.

    I want to add, that I also have a problem with undeleted local_username folders. I've been seeing it from the first installation of RDS farm with fslogix 2.9.7349.30108. I don't know if it makes bad influence on user experience or not.


  4. Dlo 96 Reputation points
    2021-03-17T11:01:14.847+00:00

    So we finally got something small from Microsoft I know we all dont have the same issue and mines a little different. But this is what I got back so far.

    Hope you are doing good!
    I got an update on this:
    Even though the feature is not enabled, logging is still on:
    Please Turn off the logging for ODFC containers and monitor the behavior.

    I asked what does that have to do with the issue and then she replied with...

    Hello David,
    Thanks for your response.
    This is accordance with the Outlook Logs and Windows Search that were checked that day in the meeting.
    Also, if you enable ODFC along with Profile logs, it collects same data twice and stores twice which may hamper the Performance.
    In any way, you have not enabled ODFC, however, Logging for ODFC is enabled.
    It is recommended to disable logging for the ODFC and monitor the behavior.


  5. CitrixMember 6 Reputation points
    2021-03-26T10:42:49.977+00:00

    It seems that Microsoft working on the problem as a bug, and we have to wait and see what they find out.
    For those of you experiencing this in Citrix, have you tried this out?
    May this be the performance hamper and might cause fslogix svc timeout?

    https://support.citrix.com/article/CTX279517

    We're testing this out now.
    From earlier perspective we have excluded chrome and other things from Ctxhooks, which has improved the performance for the specific application.


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.