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

Richard 1 Reputation point

2021-02-25T07:10:33.663+00:00

Hi,

Same issue for us.

FSLogix 2.9.7654.46150
Windows Server 2019 (last update)

We need a fix !!
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.
Adam Gemberling 1 Reputation point

2021-02-26T16:51:24.377+00:00

Seeing this exact same issue on a Windows 10 Enterprise for Virtual Desktops, version 2.9.7654.46150.
Will try out cleanupinvalidsessions (not on cloud cache) and will give notice on any improvement
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.
SomeLameSysAdmin 1 Reputation point

2021-03-05T14:34:49.9+00:00

Were are seeing this with server 2016 RDS on-prem, 100% Microsoft, FSLogix v2.9.7349.30108 using profile containers. User sessions will not log off and only recourse is a server reboot. Randomly occurs.
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.
Much R 101 Reputation points

2021-03-10T16:24:31.327+00:00

Hi,

check out the last post on this website.
how-to-resolve-error-group-policy-client-service-failed-the-logon-access-denied-in-citrix-and-fslogix-environments

It's a bug.

I think it's strange that Microsoft just doesn't take these posts seriously.

Regards
Michael
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.
Marius Neuhaus 1 Reputation point

2021-03-11T07:41:48.95+00:00

Hello,

I have created a ticket.
I hope microsoft will get back to me quickly.
I'll post updates and soultions from microsoft.

I'm curious, for the answer.

Best Regards,
Marius
Was this answer helpful?
Stefanos Evangelou 116 Reputation points

2021-03-11T11:03:34.787+00:00

Hello,

A lot of Microsoft customers have been affected by this issue and a lot of tickets have been opened on the same. My ticket has been open since Jan 29th as a critical ticket. We have performed very thorough testing, took verbose traces and carried out all actions requested by MS FsLogix support team, to no avail. For some reason they are very slow in responding. The support team is having discussions with the FsLogix product group team but they have yet to provide us with a clear and conclusive update on how the issue will be fixed. All evidence so far points to a potential software bug but we have not yet received official confirmation on this from the technical support side, despite our numerous emails to the escalation team.

Hopefully there will be action from the Microsoft side soon, since this is affecting a growing number of customers and production environments worldwide.

Marius Neuhaus 1 Reputation point

2021-03-11T11:36:56.937+00:00

a little bit more pressure for MS is okay ;D

I agree with you and hope we get some answers/fixes from MS

Dlo 96 Reputation points

2021-03-11T12:00:10.67+00:00

I just keep getting they are going threw logs every time they give me an update.

Sountharanayagam, Jan 1 Reputation point

2021-03-15T09:41:22.79+00:00

Hello everyone, we are facing the same Issue. MS Case already opened for 1 Months. Still waiting for response...
Current Workaround: Reboot the Servers every night.

Stefanos Evangelou 116 Reputation points

2021-03-16T14:04:08.75+00:00

Hello,

Unfortunately I am get the same type of response with this ticket now open for almost 1.5 month. They are requesting for same type of traces/logs which we sent long time ago and for which we never got a clear analysis of or the logs were not helpful to determine the root cause. I am starting to think that they may have issue identifying the problem from their end and to be honest I am not optimistic about a resolution any time soon.

Stefanos Evangelou 116 Reputation points

2021-03-22T15:19:49.457+00:00

Hello,
It seems we are getting closer to this being identified as a bug for resolution in an upcoming FsLogix release: https://stefanos.cloud/blog/kb/how-to-resolve-error-group-policy-client-service-failed-the-logon-access-denied-in-citrix-and-fslogix-environments/ (see bottom or article for my latest updates from FsLogix technical support and product group).

Stefanos Evangelou 116 Reputation points

2021-04-15T08:41:52.457+00:00

Issue continues to occur since the root cause has not been isolated yet from the MS side. Newest update is that the technical support team in collaboration with the product group requested a full memory crash dump from the affected Citrix session machine right after the issue occurs. Analysis of the full memory dump is now in progress: https://stefanos.cloud/blog/kb/how-to-resolve-error-group-policy-client-service-failed-the-logon-access-denied-in-citrix-and-fslogix-environments/. Hopefully this will help sort the issue out.

Stefanos Evangelou 116 Reputation points

2021-05-20T15:13:22.087+00:00

After 4 months of my Microsoft Technical Support critical case having been open, I received a reply today (May 20) stating that the case will be closed and that the product group is still investigating the issue without a known ETA for providing a fix (the issue has clearly been identified as a bug but never officially admitted as such).
See https://stefanos.cloud/blog/kb/how-to-resolve-error-group-policy-client-service-failed-the-logon-access-denied-in-citrix-and-fslogix-environments/ (bottom of article) for details on the response from the technical support team.

Stefanos Evangelou 116 Reputation points

2021-05-20T15:20:52.417+00:00

After 4 months of this case having been open with Microsoft Technical Support today (20th May) I received a response by email (see https://stefanos.cloud/blog/kb/how-to-resolve-error-group-policy-client-service-failed-the-logon-access-denied-in-citrix-and-fslogix-environments/). In essence, the case was closed and an internal case is still open in the FsLogix product group without an ETA for providing a fix. Clearly the support team and product group have not realized the significant impact this has on multiple customers and environments.
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