FsLogix - Unclean logoff causing locked files until server reboot

I have two Citrix environments which are pretty much identical. Both 2019 Citrix LTSR 1912 CU4. One has the issue the other one doesn't and profiles get cleaned up nicely. They both run 2105 HF1 and share the same redirections.xml file and container storage location.

On the not working I get these errors:

[14:57:43.138][tid:00001770.0000407c][WARN: 00000091] Failed to delete C:\Users\local_BURNESKA (The directory is not empty.)
[14:57:43.142][tid:00001770.0000407c][WARN: 00000005] Failed to delete C:\Users\local_cvetanom (Access is denied.)

The VHDX gets unmounted though, so the user can still re-logon. It just doesn't delete the temporary local_data.
When I try to delete the content from local_user myself I get an access denied. I tried spawning a CMD as SYSTEM but same thing, access denied. There is no way you can delete that folder. I'm running non-persistent disks though, so reboot and it's gone but it's still annoying enough.

My other Citrix env has no issues at all, it can run for weeks and all profiles are cleaned up perfectly fine! So wth is the difference :)

It's been a year now, and Microsoft doesn't want to solve the problem. I don't know what's wrong with them.

I temporarily fixed this problem with a script in the task scheduler.

1. On each RDSH server I created a folder C:\PS and put this script there: $Event = Get-WinEvent -MaxEvents 1 -FilterHashtable @{logname='Microsoft-FSLogix-Apps/Operational';ID='31'} $TimeCreated = $Event.TimeCreated $Event = [xml]$Event.ToXml() $User = $Event.Event.EventData.Data | Where-Object {$.name -eq "Username"}
   $SID = $Event.Event.EventData.Data | Where-Object {$.name -eq "SID"} $RefCount = (Get-ItemProperty -Path "Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileService\References\$($SID."#text")").RefCount[0] if( $RefCount -ne 0 )
   {
   "$TimeCreated, $($User.""#text""), $($SID."#text"), $($env:COMPUTERNAME)" | out-file \resoleasing.com\NETLOGON\RDS\FSLogix\FSlogix.txt -Append
   Set-ItemProperty -Path "Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileService\References\$($SID."#text")" -Name RefCount -Value (byte\[\])
   }
2. In the task scheduler, I had to run the task under my account, for all users with the highest rights.

Trigger:

This event occurs when a profile is unloaded.

Programm: powershell.exe

Arguments: -NoProfile -NoLogo -NonInteractive -ExecutionPolicy Bypass -File C:\PS\FixLockoutProfile.ps1

Using the latest version of fslogix we suffer the same problem on our rds 2012r2 servers and have done through various releases.
If you have the GPO setting to remove the local profiles at log off the profile will be trashed and we will find file locks on local search folders. Causing a profile error.
"C:\Users\username\AppData\Roaming\Microsoft\Search\"

You can use delprof to remove the profile cleanly
you can stop search to remove the lock

As a all in one solution i disable the GPO that removes the local profile. Then on on a nightly schedule stop the search services, disable the search services. Have delprof run. Rinse and repeat a few times.

by the morning previous sessions are cleaned off so new sessions work fine.
Works 95% of the time.

A preview update has been released. "KB5007266"

Addresses an issue that causessearchindexer.exe to keep handles to the per user search database in the path below after you sign out: “C:\Users\username\AppData\Roaming\Microsoft\Search\Data\Applications\<SID>\” As a result, searchindexer.exe stops working and duplicate profile names are created.

https://support.microsoft.com/en-us/topic/november-22-2021-kb5007266-os-build-17763-2330-preview-c9ba0c4c-c8b7-409a-8fac-a76ffae8f94f

https://twitter.com/\_POPPELGAARD/status/1463418452958453768

Hello everyone,
after an update from 1912 CU2 to 1912 CU4, we have the exact the same problems.

After a long search we restored the master image from the backup and the problems were gone...

We examined the difference between the master images and found that the working worker has not "Citrix User Profile Manager" and a "Citrix User Profile Manager WMI Plug-In" installed. Is there a connection? Do you have these VDA plugins installed?