Forum Discussion
MicrosoftAnnouncing General Availability of FSLogix 2201 (2.9.8111.53415)
Unfortunately it is normal these handles can't be easily closed without the server reboot.
Hard to guess remotely what's exactly locking it, if some other troubleshooting may help or only reboot is the solution.
Right now in test env I can't simulate it as we currently test private version which don't let me to break profile easily so some fragments will not unload correctly.
Btw. normally you should see more than "Type: File" only (you must use -a parameter), e.g. Mutant/Event/Token. Did you use "-a" param? If yes, then it seems only reboot will help, unfortunately.
Edit: Ok I forced a lock again but another one than your so this one was easily fixable without reboot by restarting a single service:
As you can see almost unrelated service/process released other locks as well, including PID4 ones. If your session host where you have problems is not productive, you can try to stop/restart each non-critical OS processes/services (Antivirus, FSLOGIX,...) and then system services as well (which are restartable, non-critical) and monitor if any of them will release some of the locks for you to find out which process/service is the culprit.
Good luck to find it out to avoid whole server reboot but to be honest I expect you will be forced to reboot it to resolve the "issue".
- Thanks, I'll definitely try that!)
Another tip for avoiding reboot you can try to use frx.exe stop-agent / start-agent to unlock profile folders.
Btw. about the:C:\Users\local_username\AppData\Local\Microsoft\CredentialsThese are most frequent ones on my side and in 99.9% it was quite easy to release them without reboot.
In most cases there was a lock by some "telemetry" services which are easily restartable...Btw. when user is logged off correctly, user profile should be unloaded from registry but in your case you still see profile hive in ProfileList and FSLOGIX-Sessions?
- Yes, the records remain. I noticed this seems to happen when a user's session is disconnected by timeout. RDS settings.
Btw. are you using Profile Container only or Office Container or Cloud Cache as well?
- Profile Container only.
What exactly are you redirecting to the local profile?
- https://pastebin.com/tvvabTNX
But even if I turn it off, I see an error with the folders:
C:\Users\local_username\AppData\Local\Microsoft\Credentials
C:\Users\local_username\AppData\Roaming\Microsoft\Credentials
Edit: Did you try "&'C:\Program Files\FSLogix\Apps\frx.exe' list-redirects" command if you can see active redirect there for local_profile folder?
- I did a reboot over the weekend to clear the folders, I'll check back later.I think these folders:
C:\Users\local_username\AppData\Local\Microsoft\Credentials
C:\Users\local_username\AppData\Roaming\Microsoft\Credentialsnot related to Microsoft Office or google chrome browser
The FSLogix developers say that folder freezes are not related to FSlogix.
But why can't they make Microsoft components compatible with their program?We don't use redirections so folders are almost empty, only some caches or temp files.
Btw. when user is logged off correctly, user profile should be unloaded from registry but in your case you still see profile hive in ProfileList and FSLOGIX-Sessions? Weird as they should be unloaded during logoff.
Maybe FSLOGIX log [C:\ProgramData\FSLogix\Logs\Profile\] shows something relevant?
Btw. are you using Profile Container only or Office Container or Cloud Cache as well?
What exactly are you redirecting to the local profile? Maybe some item there is the culprit why folder is not correctly unmounted... If you have problems with undeleted local_profile every time, I should recommend to create special GPO for specific test user where you will disable redirections (deny permissions for specific user on such redirectionsXML share should be enough to not apply them whithout changing any GPO) and test it if local_profile is correctly cleared. If yes, direct your sight on redirections XML file...Edit: Did you try "&'C:\Program Files\FSLogix\Apps\frx.exe' list-redirects" command if you can see active redirect there for local_profile folder?
ExSportCZ, hi.
"when you run "mountvol" command, do you see if profile is mounted?"
- No.
\\?\Volume{bb3aa5e4-0000-0000-0000-602200000000}\
C:\
\\?\Volume{934d4f6b-9ba1-11ec-b596-806e6f6e6963}\
A:\
\\?\Volume{934d4f6a-9ba1-11ec-b596-806e6f6e6963}\
D:\
"Please check registry "HKEY_LOCAL_MACHINE\SOFTWARE\FSLogix\Profiles\Sessions" and "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList" as well if profile of the affected user is unloaded or not."
https://ibb.co/j4qDC3q
https://ibb.co/PQwvMCFI have to delete 20 gigabytes every week ~
- Btw. when you run "mountvol" command, do you see if profile is mounted?
Please check registry "HKEY_LOCAL_MACHINE\SOFTWARE\FSLogix\Profiles\Sessions" and "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList" as well if profile of the affected user is unloaded or not. Mountpoint path per user can be found in [FSLogix\Profiles\Sessions] hive.
I know that "local_username" folder is the local folder and not the mounted one but good to know if FSLOGIX handled unmounting correctly or some fragments left also there...
Anyway if local_username folder exists for whatever reason, FSLOGIX will create another one for new user session so it should not be problem the old folder was left in filesystem as it doesn't block user logon process.
As it seems a cosmetic issue only, it is quite easy to delete all old local folders after clean reboot in C:\Users folder for not loaded profiles 🙂 - Someone describes it here like blackscreen during logon. The state when FSLOGIX don't handle user session correctly, e.g. in case more (different) user sessions are opened for the same user what leads to lockups, broken profiles or session hosts....