Forum Discussion
- Lee_EBrass Contributor
I've set up a 5 minute scheduled task that runs a script (below). It's not pretty and if someone logs off and back on in less than 5 minutes it may still error until the 5 minute point but it works for us. We can run this with minimal complications until a production ready version is released. Hope this helps a few of you.
$profilesKey = "HKLM:SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileService\References\" $userProfiles = Get-ChildItem -Path $profilesKey ForEach ($userProfile in $userProfiles) { $RefCountProperty = Get-ItemPropertyValue -Path "Registry::$userProfile" -Name "RefCount" If ($RefCountProperty[0] -eq 1) { $RefCountProperty[0] = 0 Set-ItemProperty -Path "Registry::$userProfile" -Name "RefCount" -Value $RefCountProperty } }
- StevenRBrass ContributorLife saver, I had this issue when not even using fslogix but was on an Azure AD joined AVD, deleting the user from the "Reference" folder fixed it, Thanks
- michael_moshkovichBrass Contributor
Hi All,
FSLogix 2201 is now Generally Available > Announcing General Availability of FSLogix 2201 (2.9.8111.53415)
Best regards,
MM
- bloggin1725Copper Contributor
Hi Michael, we are seeing this issue with the latest FSLogix version running on Server 2022. If I set the Refcount key to 0 then the affected person can log in again.
- Andreas MöriCopper Contributorsame for us "access denied" for users (less then before but still happening)... with AVD and Windows 10 Enterprise multi-session (mostly when 2 or more sessions hosts are in a AVD-ppol)
- SOVE-82Copper ContributorHi,
I installed fslogix 2201 hotfix 1 but we still have this issue.
We are using profile and office container in a RDS environment.
We notice the problem when the server does an unexpected reboot and with user logged on.
With Lab I noticed that this issue appear only when office 365 Is installed, without it there is no issues.
If I delete the "user" folder the user can log in. If can help under the user folder there is ntuser.dat file (without Office 365, the folder is empty).
Regards
- Soo Kuan TeoMicrosoftIs it consistent repro on the same sessionhosts? Can you please share the connection activityid that produce this error?
From the activityId, find out the session host, check the sessionhost eventlog for any FSLogix, user profiles errors. Please share your findings. - mark1nhCopper ContributorWe see the same problem with citrix server 2019 based multisession. the folder c:\users\local_USERNAME cannot be deleted because some process locks appdata\local\credentials.
Only solution: reboot the affected server.- Dale HayterCopper Contributor
mark1nh From our investigation the issue was caused by the FSLogix service stopping for some reason. This then resulted in profiles being left behind. We are still working with Microsoft on a resolution for the stopping of the service.
- JohnMankariosCopper Contributor
Dale Hayter Did you find any solution, as I am facing the same problem.
- GuidoMicrosoft
Hello All, The fix will be included into the next FSLogix version released on January with a public preview this month. We are in the middle of a testing phase as we cannot release a version or a fix without fully tested otherwise we could have other issues in your environment. Our sincerely apologies for all problems that this is causing in your environment. Feel free to reach me out if you have additional questions.
- GuidoMicrosoftFLogix versions can be found here; https://docs.microsoft.com/en-us/fslogix/whats-new
- lilalexMSBrass ContributorHi Guido! have you got some other updates about the fix? The ETA that you say us is confirmed? We have big troubles with our customers.
- GuidoMicrosoft
Hello. The FSLogix Public preview version has slipped to early January. We apologize for any inconvenience this may cause.
- sachin1988Copper ContributorWill this resolved permanently once and after installation of latest version (FSLogix) ?
- CaptainRebootBrass ContributorIt has resolved it for us so far. We have not seen the error come up since. Please note that you need the preview version of FSLogix, not the latest production version.
- AgdarMicrosoftHi Dale, try a reboot and see if it fixes the issue temporarily (am sure it will)
Also you can always:
○ Look for RefCount value in HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileService\References\<User SID> and set that to 0
This is a temp fix for the issue
Lets hope it gets fixed in the next version- syedaltamashCopper Contributor
Agdar
We are facing same issue from many days we have many times changed ReFcount value to 0 but again and again it's reversing.- MarkF26Brass Contributor
I am suggesting the following short script as a logoff script for WVD users to be deployed by a GPO. Please use at your won risk:
$ProfRefsPath = "Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileService\References" $MySID = (Get-CimInstance -Class Win32_UserAccount -Filter "Domain = '$ENV:Userdomain' AND Name = '$ENV:UserName'").SID If (Test-path $ProfRefsPath\$MySID) { set-itemProperty -Path $ProfRefsPath\$MySID -Name RefCount -Value 0 }
- ahmadhalaby1989Copper Contributorany soltuion yet?