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. Anonymous
    2021-08-24T08:35:53.157+00:00

    Hi,
    really interessting what you talk about. I got the same issue since we introduced FSLogix and did a long journey until I found your posts here. Thanks
    Actually I still face same issues.

    Installed FSLogix 2105
    Usergroups for exclusions are solved by local groups, no GPO
    FRXrobocopy created

    Still the same issues with this new release of fslogix.
    Username_local - folder persists and is not getting deleted

    sysinternals handler.exe shows no matches on specific folder.

    any suggestions?

    Regards,
    Daniel

    0 comments No comments

  2. Андрей Михалевский 3,461 Reputation points
    2021-08-24T12:07:30.997+00:00

    LeilaKong said that she discussed in the developer group that if the theme was popular ( https://techcommunity.microsoft.com/t5/azure-virtual-desktop/fslogix-unclean-logoff-causing-locked-files-until-server-reboot/idi-p/2595889#M45 ), the developers would pay attention to it. It became popular, but the developers completely ignored it. I think this is a big critical problem and they don't know what to do about it.

    0 comments No comments

  3. ErikS 96 Reputation points
    2021-08-25T13:09:40.777+00:00

    While the frequency of this happening is WAY less now, I did still experience it after upgrading to 2.9.7838.44263.

    0 comments No comments

  4. Magoogle 1 Reputation point
    2021-08-27T20:25:04.85+00:00

    Same issue here, 2x 2019 session hosts, 1 host is working fine, other host is consistently getting locked profile folders due to the robocopy bug listed above.

    Latest version is not helping and on top of this issue, the new version is now creating local profile folders when users fail to sign in, ignoring the registry key that should be preventing them from doing so.

    0 comments No comments

  5. Андрей Михалевский 3,461 Reputation points
    2021-09-13T07:11:25.603+00:00

    Has anyone made a ticket to Microsoft?


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.