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. CitrixMember 6 Reputation points
    2021-09-16T07:27:20.42+00:00

    This was the most active forum I found at a earlier time.
    As mentioned earlier the 2105 preview and public version has solved problem for us.
    Not sure what why fslogix still struggling in your environment.

    I have tried to help much I can.

    Did you change include groups?


  2. Jonathan Pitre 6 Reputation points
    2021-09-16T16:57:26.577+00:00

    I currently have the issue on Server 2019 with the latest FSLogix version. I also tested with another profile solution (Citrix Profile Management) and the issue persist. I have the feeling this is a Windows Server issue and not necessarily related to FSLogix. Bare in mind that the underlying RDP components for Server 2019 are old. I'm wondering if the issue also happens on Server 2022.

    Jonathan Pitre, Citrix CTA


  3. BananaBread-1757 1 Reputation point
    2021-09-27T23:25:16.967+00:00

    We too are facing this issue with a recent implementation. We have other sites setup with fsl running on the older versions without issues.

    In addition to the black screen logons, we also experience users where they cannot connect to any 365 services. Appears to be related to aad/ssso in cominbation with fsl.

    We have a case logged with MS, and still waiting to hear back from them..

    0 comments No comments

  4. Robert Berggren 1 Reputation point
    2021-09-28T16:53:52.21+00:00

    Today I got the "The Group Policy Client service failed the sign-in" Access denied.

    I found this workaround to at least let the user in again. HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileService\References\<sid affected user>
    RefCount set the value to 0. Then when the user logged in a new local_username was created. Would it be possible to zero out this key at log off somehonw?


  5. Андрей Михалевский 3,461 Reputation points
    2021-10-12T06:57:06.257+00:00

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.