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

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?
Gianluca Melis 101 Reputation points

2021-05-13T13:22:19.607+00:00

Literally just try a downgrade. It’s 2 restarts away and can save you lots of nerves!

Remember to fully uninstall FSL restart and install then restart again!
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
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?
Gianluca Melis 101 Reputation points

2021-05-06T09:40:29.847+00:00

what about downgrading to 2004 (2.9.7349.30108) ?
That fixed all the Problems described in this thread.

Dlo 96 Reputation points

2021-05-26T18:04:01.567+00:00

We had some other issues with the older version. We are at least getting our VHD dismounted now but we have the folders still there. We do weekly reboots which is keeping us better atm till its resolved.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
CitrixMember 6 Reputation points

2021-05-05T10:16:54.853+00:00

See this link Stephanos, Marco and Fredrik describes the situation

https://www.meinekleinefarm.net/caution-fslogix-2009-2-9-7621-30127-profiles-wont-logoff-completely/
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.
daniel reid 1 Reputation point

2021-05-05T07:53:11.73+00:00

In an effort to keep this thread active I'd just like to describe our current situation.

We have recently deployed FSLogix in our environment. As discussed in this thread, in our case, it seems to be that when a user is logged off due to inactivity (set to 8 hours in our environment) then two things happen, one is that sometimes the profile disk will stay attached on that machine until it is administratively removed. The second issue I'm finding, through reading the ODFC logs, is that when the user is logged off due to inactivity the following logs are displayed when trying to detach the container, saying that the "User is not a member of the include group" even though it they definitely are (and had been using FSLogix during that session).

[12:32:12.701][tid:00000dac.00001abc][INFO] ===== Begin Session: Detach Outlook Data Folder Container: George
[12:32:12.701][tid:00000dac.00001abc][INFO] Configuration Read (DWORD): SOFTWARE\Policies\FSLogix\ODFC\Enabled. Data: 1
[12:32:12.701][tid:00000dac.00001abc][INFO] Include group SID: S-1-5-21-2421605326-1487003826-3486927839-16969
[12:32:12.701][tid:00000dac.00001abc][INFO] Exclude group SID: S-1-5-21-2421605326-1487003826-3486927839-16970
[12:32:12.701][tid:00000dac.00001abc][INFO] Reason set to 1: User is not a member of the include group
[12:32:12.701][tid:00000dac.00001abc][INFO] Reason set to 1: User is not a member of the include group
[12:32:12.701][tid:00000dac.00001abc][INFO] User is not a member of the include group
[12:32:12.716][tid:00000dac.00001abc][INFO] Do not handle this session
[12:32:12.716][tid:00000dac.00001abc][INFO] ===== End Session: Detach Outlook Data Folder Container: George

Once this has happened I've found that I'm having to go into the registry and remove the session key for that users SID and then the next time they log in it will work as normal. Otherwise it will say a log message similar to "The container is already connected to another session" and the profile will not load.

Today we've implemented a workaround in the way of a scheduled task that polls the server every 30 minutes to see if there is any profile disk attached to the machine for a user that's not currently logged in, if there is then it detaches the disk. It also clears out the Session registry keys for any user that isn't currently logged on. I'll let you know how I get on with this script and whether or not it stops the issues occurring.
Was this answer helpful?
CitrixMember 6 Reputation points

2021-05-05T08:04:11.077+00:00

Thanks for update Daniel!
It seems that you experience the same problem as we do and several others.
But in our logs we dont get the "not member of the include group" and this I know was discussed earlier as a problem in earlier version of fslogix.
Couldt it be you have created the include/exclude groups with GPO and used REPLACE than the UPDATE?

Do you only use Office Profile disks?

daniel reid 1 Reputation point

2021-05-05T10:01:02.377+00:00

Hello, we do use a GPO to create the groups using the Replace action, should I change this over to Update?

Also, yes, we are currently only using the Office Profile disks.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
CitrixMember 6 Reputation points

2021-05-03T11:15:13.297+00:00

Anyone here who has found out more regarding the Fslogix locks problem?
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.

FsLogix - Unclean logoff causing locked files until server reboot

107 answers

Your answer