FsLogix - Unclean logoff causing locked files until server reboot

Much R 101

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?

Anonymous

2021-01-14T03:03:58.32+00:00

Hello @Much R

Did you check affected user has full control and Owner over their FSLogix Folder and the VHDX files ?

Thanks
Karlie
Much R 101 Reputation points

2021-02-02T08:02:21.997+00:00

Hello,

Where is my answer from yesterday?
Why was this deleted?

How can I open a ticket at Microsoft now?

Thank you
Anonymous

2021-02-02T08:16:39.607+00:00

Hello @Much R

sorry I was going to delete my comment as it wasn't helpful, and your comment is below mine, so it seems they were deleted together. I want to restore but it doesn't has this option.

FSLogix is supported for use with versions of Windows and Office that are still included in the Microsoft Support Lifecycle.

How to open a FSLogix Support Request
https://social.msdn.microsoft.com/Forums/en-US/14ea5f6f-760b-4ad2-83cf-23c3cbc1bcc4/how-to-open-a-fslogix-support-request?forum=FSLogix

Best regards
Karlie
Germain 11 Reputation points

2021-02-19T11:44:10.117+00:00

We are currently experiencing the same issue. The user VHDX is locked by system and can only be unlocked by rebooting the server.
Has Microsoft acknowledged this issue?

Currently using: 2.9.7654.46150
Bracko Ewald 31 Reputation points

2021-02-19T12:10:09.137+00:00

Did you activate the registry value HKEY_LOCAL_MACHINE\SOFTWARE\FSLogix\Apps\CleanupInvalidSessions (REG_DWORD, 0x1)?
Do you use Cloud Cache or not?

Also, maybe you can check with the frx command line tool if there are still some redirects pointing to the use VHDX file. You can then use that tool to delete them manually and detach the VHDX files afterwards using diskpart.
Marius Neuhaus 1 Reputation point

2021-03-09T10:31:38.737+00:00

Hello,

we have the same problem.
We use on-premise terminalserver.:
Windows Server 2019
Citrix 1912 CU2 LTSR
FSLogix 2.9.7621.30127

I've tried the CleanupInvalidSessions RegKey, but it doesn't effect.
We don't use Cloud Cache.
FSLogix Configuration only local and not per gpo.
The frx command line tool dont show redirects pointing to the use VHDX file.
Permission are set correct. Users work correctly with the containers.
Luckily the problem occurs only randomly and not at every logoff.

In the FSLogix Configuration we include the group domain-users and exclude the domain-administrators.
Could it be a Problem?

Best Regards,
Marius
itsupport 1 Reputation point

2021-05-26T12:40:37.147+00:00

When this happens are you left with multiple <USERNAME>.original folders? I've seen it go as high as <USERNAME>.original11 before I just manually delete all the folders.
Guido Racamato 26 Reputation points

2021-09-28T17:39:34.337+00:00

Hello Everyone, For the Group Policy Access Denied, once you get an affected user, could you please modify the following registry? There's no reboot required.

HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileService\References\<SID affected user>
REG_BINARY: RefCount
Value: 0
Jon McLeod 1 Reputation point

2021-11-19T14:56:08.267+00:00

This is the answer. Thank you.
Farooq 5 Reputation points

2024-02-14T12:02:36.9533333+00:00

We are having the same issue. We have an RDS environment and time to time users get logged in with Temporary profile, when I check the FSlogix logs I am seeing the following error - Failed to open virtual disk: \server\Profiles\S-1-5-21-26711-2174_user\Profile_user.vhd (The process cannot access the file because it is being used by another process.)
What we done to try resolve this or at least try find the cause and reduce downtime is, we have removed AV from all RDS host, we have created a script which logs out all users at midnight but issue is still occurring. We have a case opened with Microsoft but unfortunately there has been no resolution. Another issue we had is where users could not sign into their Outlook, teams, Office profile on the host. Has anyone else experiencing this issue and has anyone managed to resolve this? Any help or suggestion would be much appreciated.

107 answers

Андрей Михалевский 3,476 Reputation points

2021-12-08T06:57:17.86+00:00
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
Was this answer helpful?

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Martijn Kools 171 Reputation points

2021-12-09T14:15:17.45+00:00

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 :)
Was this answer helpful?

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Sues, Marco 1 Reputation point

2021-12-13T15:37:10.893+00:00

We got the same issue with Windows 2019, FSLogix 2105 HF_01 (2.9.7979.62170) and CVAD 1912 CU4.

(latest kb installed, cleanupinvalid Sessions key set..)

I have read in some Posts, that a downgrade worked for some of you guys. Which Version did you chose in this Case?

Also someone wrote uninstalling UPM worked for someone..

If we want to open a case with MS on this Problem, does someone have a link for this?

Greetings Marco
Was this answer helpful?
Simon Brunkau 1 Reputation point

2021-12-21T15:07:08.61+00:00

Same Problem and a long weekend to find out, that only a rollback to citrix vda 1912 ltsr CU2 fix it. With connections over RDP everything was fine, no chance to reproduce the problem, only hdx connection affected! This week i try to recreate the problem for the citrix support case.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Андрей Михалевский 3,476 Reputation points

2022-01-13T09:25:58.987+00:00

Hi. What's new? Still no fix. Does anyone do paid tickets, do they help you?
Was this answer helpful?

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Robert Berggren 1 Reputation point

2022-01-25T06:52:05.567+00:00

New version out https://techcommunity.microsoft.com/t5/azure-virtual-desktop/the-fslogix-2201-public-preview-is-now-available/m-p/3070794#M8455
Was this answer helpful?
Sues, Marco 1 Reputation point

2022-01-25T07:06:42.407+00:00

Fixed an issue where active user session settings where not retained if the FSLogix service was restarted. This was causing some logoffs to fail.

If i get this right, the only "logoff" Issue fixed? right?

Anyony tried this preview?

Srojas 1 Reputation point

2022-02-02T19:53:39.977+00:00

Hi Robert,

Have you deployed the preview? I just signed up to see if I could get a download link.
We only use FSL for ODFC but I believe we encountering the same issue.

Every so often our RDS host will get stuck attempting to reattach a "detached" disk until eventually the FSL service breaks.
I"m not sure why the disk detaches in the first place but at this point I'm concerned keeping the system operational.

This looks promising from the link you provided:

FSLogix will no longer attempt to reattach a container disk when the user session is locked.

Fixed an issue that caused the FSLogix service to crash when reattaching container disks.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

FsLogix - Unclean logoff causing locked files until server reboot

107 answers

Your answer