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?

Karlie Weng 18,581 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 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
Karlie Weng 18,581 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 26 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.

106 answers

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

2021-09-10T06:18:40.043+00:00

I can't understand why the developers are ignoring this problem. Even LeilaKong doesn't give answers now. What is wrong with them ?
Please sign in to rate this answer.

2 people found this answer helpful.

0 comments No comments
Sign in to comment

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

2021-10-20T09:55:31.237+00:00
As a temporary solution, I use this script when a user logs out using group policies.

$SID = ([System.Security.Principal.WindowsIdentity]::GetCurrent()).User.Value Set-ItemProperty -Path "Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileService\References\$SID" -Name RefCount -Value ([byte[]](0x00,0x00,0x00,0x00))
Please sign in to rate this answer.

2 people found this answer helpful.
Wayne Bedwell 1 Reputation point

2021-10-26T11:46:04.433+00:00

I've reverted back to (2.9.7349.30108) Version 2004 and this appears to have resolved the problem. Microsoft really need to get this fixed

Jonathan Pitre 1 Reputation point

2021-10-26T19:18:05.8+00:00

Thanks for sharing your script Wayne but I'm not sure how to configure this by GPO.

Non-admin users has no access to modify the HKLM branch of registry so how exactly are you processing this at logoff ?

BananaBread 1 Reputation point

2021-11-09T03:02:36.33+00:00

How has the roll back been? Also are you utilizing both user and office profiles?
Sign in to comment

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

2023-09-13T17:39:25.6966667+00:00

We've mitigated our fslogix issues by restarting our RDS servers once a week. It's a pain but ever since we introduced this cadence we haven't had the odd server lockups we used to get.
Please sign in to rate this answer.

2 people found 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-01-15T07:54:01.613+00:00

Am I the only one in the world who has the problem?

Thanks
Regarts
Michael
Please sign in to rate this answer.

1 person found this answer helpful.
Sean 1 Reputation point

2021-01-15T11:36:51.497+00:00

Hi,

We also started seeing this issue with some users.
Similar as you described, although local profile cleanup fails with: (The directory is not empty)

Doesn't happen for all users.
rolling back while we investigate
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Karlie Weng 18,581 Reputation points Microsoft Vendor

2021-01-15T08:27:39.347+00:00

Fix: The Group Policy Client Service Failed the Logon

"Therefore this error is caused by a group policy that fails to respond or if it stops running. This could be due to bad registry calls or a corrupt registry. Usually, this is caused by system updates and upgrades that might mess with the registry. A bad shutdown or startup process can also cause this issue.

This can also happen when you try to logon using a non admin account in a PC that had some applications or drivers that were installed with admin privileges before. "

FAQ: FSLogix Troubleshooting Guide
"Some registry settings cannot be set through a GPO as they need to be read too early in the boot process that a GPO can’t set them early enough."

How to resolve error “Group Policy Client service failed the logon. Access denied.” in Citrix and FsLogix environments
Please sign in to rate this answer.

1 person found this answer helpful.

0 comments No comments
Sign in to comment

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

Share via

FsLogix - Unclean logoff causing locked files until server reboot

106 answers

Your answer