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: Newest
  1. Sven Goossens 1 Reputation point
    2021-05-28T09:24:03.237+00:00

    We saw the issue dissappear after completely removing the antivirus. So I'm not really sure this is caused by Fslogix.

    Was this answer helpful?


  2. Robert Berggren 1 Reputation point
    2021-05-28T07:24:27.62+00:00

    Does anyone have an update on this? Unfortunately not very good. Will have to revert to rebooting my seesion hosts every night now until this is resolved.

    Was this answer helpful?

    0 comments No comments

  3. Micheal Thompson 1 Reputation point
    2021-05-13T12:31:29.343+00:00

    I am still experiencing this issue as of 13/05/2021.

    Multiple customers experiencing this, it's random. Did anyone find a fix for this yet? I see some people mentioning to just roll back to release 2004 of FSLogix should I try this?

    I am also going to try the registry key people who have previously mentioned CleanUpInvalidSessions.

    Did have one customer who was running 2 Citrix VDAs and this was happening daily have since removed a VDA and increased the Ram/CPU of the single VDA to match that of 2 VDA servers. And it doesn't happen anymore? Yes, I have concurrent sessions enabled.

    Weird...

    Was this answer helpful?


  4. Deepak Kumar 11 Reputation points
    2021-05-08T11:53:09.45+00:00

    Hello, I am very new to fslogix, and just finished setting up for a customer.

    Windows Server 2019
    Citrix Apps & Desktop : 1912 LTSR CU2
    FsLogix Apps : 2.9.7654.46150 (No cloudcache)
    All MacAfee AV exclusions recommended by Citrix & Microsoft

    As of now I am not getting any issue while deleting the profiles after user log off, But if i get i would take below steps to go more in detail . I understood most of you already did these troubleshooting but hope to add new things . Please do this on your test server first.

    1. Download sysinternals tools from Microsoft & run procmon tool (Logs can be very big so apply filters accordingly)
    2. Search the logs with local_username & find the details after user log off
    3. Assuming credential folder is not being deleted ( Try to add NT Authority/System and give rights to delete)..In my case I'm using centralized template profile so its easy to do from single place. If not use group policy to add security on folder or registry or use default profile folders.
    4. Delete existing vhdx and check

    I hope this will help or give new insights if not.

    Happy debugging.

    Thanks

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments

  5. Dlo 96 Reputation points
    2021-05-05T10:54:12.473+00:00

    I will have to check on the GPO for the registry change not sure we use it either.

    We have VHD's that get hung randomly and also folders not deleted and also the registry key issue.

    We did try the fix Microsoft gave us in our dev environment but we had to put the server in test mode but the small tests we did was a bit better.
    They said this is a fix for the windows search feature so not a patch for fslogix itself.

    Sadly it will be rolled into a monthly update for windows and they are not sure when. I am pressing them for a date so we can try this in a bigger environment instead of our smaller test one. As it puts a water mark on the desktop saying test mode so we didnt want to roll this out to a big area.

    Was this answer helpful?


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.