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. Much R 101 Reputation points
    2021-01-22T07:37:31.043+00:00

    Hi,

    I saw that there is a update for the version 2009.
    whats-new

    Unfortunately, this doesn’t solve the problem either.

    Best regards
    Michael

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments

  2. Much R 101 Reputation points
    2021-01-21T16:07:18.98+00:00

    Hi,

    I found Marco's article describing the same problem.

    He also confirms the problem with the new version of FSLogix

    Link: caution-fslogix-2009-2-9-7621-30127-profiles-wont-logoff-completely

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments

  3. Much R 101 Reputation points
    2021-01-15T15:23:03.35+00:00

    Hi there,

    Thanks to everyone for the answers.

    @ KarlieWeng-MSFT:

    1. We only used FSLogix on Windows 2019 RDS server.
    2. Software is only installed with admin users.
    3. I already know the article. It also happens to users with a new profile.
    4. The error with the GPO occurs when the folders described above are blocked by "System" or "lsass.exe". Only a restart releases the folder again. Then the logon works without any problems. Even several days ...

    @ FredrikEndresen-9130:
    We do not use a GPO to distribute or configure the groups. I do this manually for each RDS server.

    Thanks

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments

  4. Fredrik Endresen 96 Reputation points
    2021-01-15T13:11:34.21+00:00

    Check your GPO settings that defines the local FSLogix include\exclude groups.

    FSLogix now uses the SID of the local include\exclude groups. So if the GPO is set up to "replace" instead of "update", it will stop working after a gpupdate within users session. This because the local groups get recreated and get new SIDs.

    This may cause the problem you describe.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments

  5. Anonymous
    2021-01-15T08:27:39.347+00:00

    Fix: The Group Policy Client Service Failed the Logon

    "Therefore this error is caused by a group policy that fails to respond or if it stops running. This could be due to bad registry calls or a corrupt registry. Usually, this is caused by system updates and upgrades that might mess with the registry. A bad shutdown or startup process can also cause this issue.

    This can also happen when you try to logon using a non admin account in a PC that had some applications or drivers that were installed with admin privileges before. "

    FAQ: FSLogix Troubleshooting Guide
    "Some registry settings cannot be set through a GPO as they need to be read too early in the boot process that a GPO can’t set them early enough."

    How to resolve error “Group Policy Client service failed the logon. Access denied.” in Citrix and FsLogix environments

    Was this answer helpful?

    1 person found 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.