FsLogix - Unclean logoff causing locked files until server reboot

Much R 71 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?

Remote Desktop
Remote Desktop
A Microsoft app that connects remotely to computers and to virtual apps and desktops.
4,250 questions
FSLogix
FSLogix
A set of solutions that enhance, enable, and simplify non-persistent Windows computing environments and may also be used to create more portable computing sessions when using physical devices.
463 questions

105 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Андрей Михалевский 2,641 Reputation points
    2021-09-10T06:18:40.043+00:00

    I can't understand why the developers are ignoring this problem. Even LeilaKong doesn't give answers now. What is wrong with them ?

    1 person found this answer helpful.
    0 comments
  2. Андрей Михалевский 2,641 Reputation points
    2021-10-20T09:55:31.237+00:00

    As a temporary solution, I use this script when a user logs out using group policies. 

    $SID = ([System.Security.Principal.WindowsIdentity]::GetCurrent()).User.Value

Set-ItemProperty -Path "Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileService\References\$SID" -Name RefCount -Value ([byte[]](0x00,0x00,0x00,0x00))
    1 person found this answer helpful.
  3. hyperv117 5 Reputation points
    2023-09-13T17:39:25.6966667+00:00

    We've mitigated our fslogix issues by restarting our RDS servers once a week. It's a pain but ever since we introduced this cadence we haven't had the odd server lockups we used to get.

    1 person found this answer helpful.
    0 comments
  4. Much R 71 Reputation points
    2021-01-15T07:54:01.613+00:00

    Am I the only one in the world who has the problem?

    Thanks
    Regarts
    Michael

  5. Karlie Weng 14,331 Reputation points Microsoft Vendor
    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

    0 comments