FsLogix - Unclean logoff causing locked files until server reboot

Much R 71

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?

Karlie Weng 14,331 Reputation points Microsoft Vendor

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 71 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
Karlie Weng 14,331 Reputation points Microsoft Vendor

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 21 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.

105 answers

Fredrik Endresen 91 Reputation points

2021-01-15T13:11:34.21+00:00

Check your GPO settings that defines the local FSLogix include\exclude groups.

FSLogix now uses the SID of the local include\exclude groups. So if the GPO is set up to "replace" instead of "update", it will stop working after a gpupdate within users session. This because the local groups get recreated and get new SIDs.

This may cause the problem you describe.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment
Much R 71 Reputation points

2021-01-15T15:23:03.35+00:00
Hi there,

Thanks to everyone for the answers.

@ KarlieWeng-MSFT:

We only used FSLogix on Windows 2019 RDS server.

Software is only installed with admin users.

I already know the article. It also happens to users with a new profile.

The error with the GPO occurs when the folders described above are blocked by "System" or "lsass.exe". Only a restart releases the folder again. Then the logon works without any problems. Even several days ...

@ FredrikEndresen-9130:
We do not use a GPO to distribute or configure the groups. I do this manually for each RDS server.

Thanks
Please sign in to rate this answer.

0 comments No comments
Sign in to comment
Much R 71 Reputation points

2021-01-21T16:07:18.98+00:00

Hi,

I found Marco's article describing the same problem.

He also confirms the problem with the new version of FSLogix

Link: caution-fslogix-2009-2-9-7621-30127-profiles-wont-logoff-completely
Please sign in to rate this answer.

0 comments No comments
Sign in to comment
Much R 71 Reputation points

2021-01-22T07:37:31.043+00:00

Hi,

I saw that there is a update for the version 2009.
whats-new

Unfortunately, this doesn’t solve the problem either.

Best regards
Michael
Please sign in to rate this answer.

0 comments No comments
Sign in to comment
Bracko Ewald 21 Reputation points

2021-01-25T16:16:19.713+00:00

We are encountering the same issue with the 2004 release (2.9.7349.30108), too.
The fslogix agent doesn't delete the redirections and unmount the containers on rare occasions.
But when it starts to happen more and more users are affected.
A reboot of the system will "fix" it for the moment.
Maybe this is caused by another Microsft update...
Please sign in to rate this answer.
Gianluca Melis 101 Reputation points

2021-05-06T09:24:35.893+00:00

we had the same problems with 2009, a downgrade to 2004 fixed everything (2.9.7349.30108 to be specific). Please note we had to uninstall 2009, restart, install 2004 and restart again. if you just install 2004 "on top" 2009 ist not going to be replaced but just installed alongside and in our case we could see in the logs that windows was still using the 2009 version.
Maybe your problem ist not strictly related to the 2009 version.
Sign in to comment