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

Hoppe, Tim 6 Reputation points

2021-02-11T08:31:50.333+00:00

We are seeing the same issues!
We have a few hundred smaller environments, each with 1-10 Citrix VDAs and the issues occur randomly.
All of our machines are running Server 2016 (German), Citrix 1912 LTSR (99% are published Desktops) and the latest FSLogix Release (all profile and no office containers).

I will try to open a ticket with Microsoft today and hope that this increases the visibility on Microsoft's side.
Was this answer helpful?
Dlo 96 Reputation points

2021-02-11T12:00:23.877+00:00

What are your session timeouts and stuff for users? We have long timeouts and are going to try to shorten them to log users out sooner to see if that helps some.
Do you see folders in the user folder as well? As in user folders who logged out but nothing was cleaned up behind them to?

We even see the folders there if the VHD is unmounted sometimes. Really hoping they find some solutions for this.

Hoppe, Tim 6 Reputation points

2021-02-11T14:23:52.97+00:00

We have the following settings "Set time limit for active but idle Remote Desktop Services sessions" at 3 hours and "Set time limit for disconnected sessions" at 8 hours.

Under C:\Users we see quite a lot of "local_Username" that are days old and sometimes cannot be deleted because there are either files still open or apparently the folder does not exist anymore. The users have logged off long ago and the VHD was successfully removed. If the user connects to this VDA again the "local_Username#" will have a number next to it.
The second and worse case is if the whole user profile is stuck. Also, with "files still open" or "folder does not exist anymore" when trying to delete it. VHD was apparently successfully removed and cannot been seen in the disk manager, but the only way to fix this is to reboot and then do a clean-up.

Our support request has been opened and we've been assigned an engineer. Let's see how that goes!

Bracko Ewald 31 Reputation points

2021-02-11T14:28:46.07+00:00

Have you checked with the frx command line tool from fslogix if there are still remaining folder redirections pointing to the locked local_ folders?

Hoppe, Tim 6 Reputation points

2021-02-11T16:27:42.137+00:00

Actually never used the tool until now. There were no redirects left on both folders that I can and cannot delete.
Thanks for the hint!

Dlo 96 Reputation points

2021-02-12T12:09:15.543+00:00

What files do you see in these local_username folders?
Most of ours have some outlook logging files which we never turned on so we are looking into that as well to see if its causing an issue.
Microsoft called me yesterday and we worked on the issue a bit thats what we came up with so far.

Gianluca Melis 101 Reputation points

2021-05-06T09:30:23.6+00:00

servus!
Please make yourself a favor and do not waste time troubleshooting that!
I had 2 weeks of pure hell trying to fix that!
We had the exact same problem and it literally vanished after installing 2004 (2.9.7349.30108)
Now its working since 2 weeks with almost no errors. edit we have other minor errors regarding other things but never saw the same error again (yet) and the user can log on and off and work basically undisturbed
In order to install 2004, you need to fully uninstall 2009 and restart the server and then install 2004. Make a backup of your Regedit settings too! (in my case they were not deleted but better be sure!)
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
SMB Solutions Cloud Services Pty Ltd 31 Reputation points

2021-02-18T23:24:22.323+00:00

We are also now experiencing the same issue across multiple RD Servers and the only workaround we seem to have is to reboot the affected server which is problematic as we can have 30 users on the server and only 1 is impacted by the issue.

We need some kind of fix urgently (statement of the bleeding obvious)
Was this answer helpful?

2 people found this answer helpful.
SMB Solutions Cloud Services Pty Ltd 31 Reputation points

2021-07-23T08:49:17.453+00:00

We have deployed the latest release and our issue seems to be solved on all of our RDS servers.
Sign in to comment

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

2021-02-18T23:45:47.723+00:00
We have also had the same problem for about a week. I am waiting for a solution from Microsoft soon.
It seems to have been occurring since the Windows Updates of December or January.
It is a single RDS Server deployment with about 15 Users on it.
The issue occurs to about one user per day.
I scheuduled a daily reboot and adjusted the RDS session limits but the issue still occurs.
- Server 2019
- FSLogix 2.9.7621.30127
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.
Chris Pickens 6 Reputation points

2021-02-21T04:08:58.863+00:00

Hi All,

The identical issue in our WVD environment as well. Same symptoms as reported by MuchR-5838. Runing Windows 10 H202. Now performing a nightly restart so users can log in the next day. Not impressed as we just went live with WVD from legacy RDS and now having more bug-type issues. lol

Have a ticket open with Microsoft and the FSLogix team.

Will share what I learn.
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.
Dlo 96 Reputation points

2021-02-22T12:19:10.55+00:00

So since the latest update our issue has changed some.
In our Citrix environment the VHD's are at least getting disconnected now but we have hung sessions randomly in the background (They are linked to a user but they are at least logged off enough to disconnect the VHD and Citrix doesn't see them but windows does.) and local files and stuff isn't being cleaned up.
We still have profile reg keys on the servers in the fslogix registry section and users local user folders aren't getting cleaned up either now.
Support said this wasn't as FSLogix issue at first but once I showed them all this stuff they are not looking into it again.
This issue snowballs issues on our servers and we sadly cant reboot things nightly as a fix.
Hopefully they figure this out soon.
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