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

107 answers

Sort by: Most helpful
  1. CitrixMember 6 Reputation points
    2021-07-26T20:56:31.29+00:00

    We did solve the problem we experienced with the preview version of 2105 version. Prod version of the 2105 havent been implemented yet. So for no problems since middle of June. We did also from a earlier point implement the frxrobocopy solution and excluded all fslogix services from Antivirus realtime scan.

    We're planning to go from preview version 2.9.7802.10873 to prod version 2.9.7838.44263 after summer.

    Was this answer helpful?

    0 comments No comments

  2. Андрей Михалевский 3,476 Reputation points
    2021-07-23T09:45:07.973+00:00

    Guys !!! I think I solved the problem.

    1. Installing all updates on windows server 2019
    2. updating FSLogix to the latest version.
    3. disabling the DiagTrack service.
    4. Copy C:\Windows\System32\Robocopy.exe to C:\Program Files\FSLogix\Apps\frxrobocopy.exe
    5. Excluding C:\Program Files\FSLogix* from the antivirus.
    6. I added a registry key for all users: AutoEndTasks (https://www.tenforums.com/tutorials/97821-turn-autoendtasks-restart-shut-down-sign-out-windows-10-a.html)

    I don't know which of these helped, but the problem is gone for 3 days, before that it was every day.

    In the dump I saw that the folder C:\Users\local_username\AppData\Local\Microsoft \Credentials was hanging in the application C:\Windows\System32\Robocopy.exe

    Maybe point 4 solved the problem.

    • So in the latest version I encountered a new problem. Sometimes local profiles are created instead of FSlogix.

    Was this answer helpful?


  3. Much R 101 Reputation points
    2021-07-23T06:49:15.903+00:00

    Hi guys,

    unfortunately the problem is not solved even with the latest version of FSLogix.

    It also seems that Microsoft doesn't want to solve the problem ...
    Microsoft has other problems too :-)

    Regards

    Was this answer helpful?


  4. Dlo 96 Reputation points
    2021-07-16T14:23:45.413+00:00

    From what remember its part of the windows search issue so it will be resolved in normal windows monthly updates but no time frame on when.

    Was this answer helpful?


  5. Daniel Viklund 22 Reputation points
    2021-07-16T14:01:00.283+00:00

    Looks like this problem still exist with the latest version 2.9.7838.44263

    Was this answer helpful?

    0 comments No comments

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.