WVD logon issues. The Group Policy Client Service failed the sign-in. Access is denied.

Copper Contributor

Hi. We have a mutli-session Win10 WVD farm up and running. We are running 1909 with the latest quality updates applied. FSLogix profile container is being used. 


We are seeing intermittent issues with users not being able to login. They are being presented with the error:


"The Group Policy Client Service failed the sign-in. Access is denied"




From investigation, cant see anything appropriate in the event logs. Anyone seen this issue before?



58 Replies
Is 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.
We 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.

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

@Dale Hayter Did you find any solution, as I am facing the same problem.

Hi Dave,
Appreciate any update on this we are seeing the same symptoms
Hello. Could you please check if setting up RefCount value to 0 solve the issue without rebooting the machine? Here's the path for this key:
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileService\References\<sid affected user>
Thanks for the reply. Will try it next time it happens and report back. Thanks



I can confirm that setting up the RefCount value to 0 solved the issue and the user is able to log in without rebooting the server. 

Let's see how long will take to happen again.


Thank you.

Thanks for confirming that. We will fix this in the next FSLogix release which could be at the end of the year. Regards.
Hey Guido - I can also confirm that the RefCount registry change works without rebooting the machine, however this issue appears to be getting worse and worse. This is causing a major business impact for 2 of our clients at the moment, with 5-10 people experiencing it per day. I know you said the next update would be the end of the year, but is there a better estimation you can provide at this time?

Additionally, I'm unable to find any official confirmation of this bug besides this post. Do you have anything I can reference confirming Microsoft is aware of this issue?

@Kyorii and @Guido 


We too are seeing an increased number of occurrences of this issue. The best solution for us at the moment is to enable drain mode on the session host that the user is failing to sign into so that they are signed into a different one and then disable drain mode after they've successfully signed in. We are also rebooting all of the session hosts every night.


This is obviously not ideal and an earlier fix for this would be much appreciated.

We've now seen this twice in 2 days and we aren't in a position to fix it quickly when it happens due to the size of our team. I don't understand how it can suddenly get so bad when it's been running fine for a long while.
Thanks so much for this it has really helped.

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.

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

Hello. The FSLogix Public preview version has slipped to early January. We apologize for any inconvenience this may cause.