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

Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more
Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more
Jos 106 Reputation points

2023-08-10T15:01:01.6666667+00:00
We do have the same issue, the local_username folder remains when the users has logged off on the server. Inside this are two folders which we cannot open because we then get Access denied:
- \AppData\Local\Microsoft\Credentials
- \AppData\Local\Microsoft\Office\16.0\OfficeFileCache
We are using the following configuration:
- Windows Server 2019 Standard 1809 17763.4645
- FsLogix 2.9.8440.42104
This is the error from Profile....txt
```
[15:03:02.304][tid:00001054.00003978][ERROR:00000091]     Error removing directory: C:\Users\local_username\AppData\Local\Microsoft\Office\16.0 (De map is niet leeg.)
[15:03:02.304][tid:00001054.00003978][WARN: 00000091]     Failed to delete C:\Users\local_username (De map is niet leeg.)
```
A bit further in the log we see
```
[16:24:04.929][tid:00001054.0000ad60][WARN: 00000005]    Failed to delete C:\Users\local_username (Toegang geweigerd.)
```
Anyone who found a solution?
Was this answer helpful?
Juan Ramirez 0 Reputation points

2023-09-13T17:27:23.8+00:00

We have the exact same issue right now with our AVD environment. We have a case open with Azure support but they haven't been able to assist us at all. Hopefully someone here posts a solution in the future.

GM 0 Reputation points

2023-09-26T19:14:02.5666667+00:00

I also have the exact same problem. Did you find any solution?

Jos 106 Reputation points

2023-09-27T06:59:08.2433333+00:00

We do not have this issue often anymore, not exactly sure what changed. But we tried to apply the default settings as much as possible as recommended by Microsoft. Since then I got the feeling that the times we had this issue decreased. Perhaps this helps?

GM 0 Reputation points

2023-09-27T07:16:54.05+00:00

Thanks for the reply. Default settings referring to redirections.xml?

Steve Turnbull 26 Reputation points

2023-09-27T07:24:58.0766667+00:00

This issue is random for us but still occurs, we usually have around 50 multi user windows 10 machines running in azure each day and about 10% of those end up with these issues. We also have the exact same issue on prem with server 2019. We perform nightly checks with our ops team to restart any with profiles left after all users have logged out. This issue should never even happen full stop, so the fact it doesn’t happen so often is a bit irrelevant since the issue is still there. I believe this only occurs in a multi user environment

the nightly checks and reboots keeps our tickets down to a minimum

Jos 106 Reputation points

2023-09-27T07:51:03.32+00:00

We did go over these settings https://learn.microsoft.com/en-us/fslogix/reference-configuration-settings?tabs=profiles and changed some back to the defaults. Not sure what changed exactly since this was a couple of weeks ago.
Sign in to comment

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

2023-04-05T12:27:35.0933333+00:00

This is an old problem, has been around for at least two years. The developers say it is not a problem with FSLogix, but with third-party applications. Unfortunately, even with Microsoft Office this is a common problem.
Was this answer helpful?
js2010 191 Reputation points

2023-04-05T14:24:49.07+00:00

We still get occasional non-zero refcount registry entries after logout, but they seem to fix themselves I guess when the user logs in again. Fslogix version 2.9.8228.50276.

Kevin Vlasselaer 11 Reputation points

2023-05-17T14:12:19.7866667+00:00

Still the same problem with latest version of fslogix 2.9.8440.42104. Cloud cache on 2 SMB location.
User get his vhw locked by PID4 "System" user and unable to relaase the file.
This user is no more displayed in the "users" list of Task Manager or in our Citrix system.
Sign in to comment

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

js2010 191

Making a sanity check in powershell. Seeing if refcount is non-zero but the user is logged out. I take out the "DOMAIN\" part of the user. I wish the logon denials were logged when auditing is turned on.

# profilecheck.ps1  
function sid2user {  
  param($id)  
  $SID = New-Object System.Security.Principal.SecurityIdentifier($id)  
  $objUser = $SID.Translate([System.Security.Principal.NTAccount])  
  $objUser.Value -replace 'DOMAIN\\'  
}  
$qusers = quser  
get-itemproperty HKLM:\SOFTWARE\Microsoft\Windows` NT\CurrentVersion\ProfileService\References\* refcount |  
select @{n='Sid';e={$_.pschildname}},  
  @{n='User';e={sid2user $_.pschildname}},  
  @{n='Refcount';e={$_.refcount[0]}},  
  @{n='LoggedOut';e={-not [bool]($qusers|select-string (sid2user $_.pschildname))}}  
# end profilecheck.ps1  


$avd = 0..4 | % tostring avd-0  
icm $avd profilecheck.ps1 | ? refcount | ? loggedout | ft  

Sid                                              User       Refcount LoggedOut PSComputerName RunspaceId  
---                                              ----       -------- --------- -------------- ----------  
S-2-6-31-1423303271-3025932689-4187700767-524288 abc123            3      True AVD-3          84594543-d151-53ee-ca1e-ec8a5186ca22

Martijn Kools 171 Reputation points

2022-12-19T09:57:21.933+00:00

That refcount issue has already been fixed in a previous FSLogix release 2201:

FSLogix now correctly handles cases where the Windows Profile Service refCount registry value is set to an unexpected value.
js2010 191 Reputation points

2022-12-19T15:01:12.967+00:00

I'm still seeing this in Microsoft FSLogix Apps 2.9.8228.50276.

FsLogix - Unclean logoff causing locked files until server reboot

107 answers

Your answer