The first reason is group policy that fails to respond or if it stops running. When you try to log in with a non-administrator account on a PC with some installed applications or drivers, the error can also be caused.
Then I will introduce how to fix the group policy client service failed the logon issue. The first method for you is to use Registry Editor. Here is how to do that:. Type regedit and click OK to open Registry Editor. Step 2: In the left pane of Registry Editor, navigate to the following registry key:. Name the new key as GPSvcGroup. Step 6: First is called AuthenticationCapabilities and it must have the value of 0x or in decimal.
The second is called CoInitializeSecurityParam and it must have a value of 1. Make sure to create a restore point just in case something goes wrong. Make sure you are logged in with the Administrative account in order to carry out the following changes. Find Group Policy Client service then right-click and select Stop. Now double click on it and make sure the Startup type is set to Automatic. Next, click on Start in order to again start the service.
Select System Protection tab and choose System Restore. Click Next and choose the desired System Restore point. Wait for the above process to finish and once done restart your PC. Again open cmd and type the following command and hit enter after each one:.
Click on Choose what the power buttons do in the top-left column. Uncheck Turn on Fast startup under Shutdown settings. Next, find the value of imagepath key and check its data. In our case, its data is svchost. This means the above data is in charge of the gpsvc service. In the right window pane locate netsvcs and then double click on it.
There might be some discrepancies in registry values. Here is the video I set for Windows 8. Nice one, thank you! I no longer have multiple Windows boxes to compare, so this saved me a lot of hassle. I'd love to know what the origin of this broken Windows distribution is.
My laptop is Toshiba in case anyone wants to compare notes. Thank you, thank you, thank you!!!! Worked like a charm. I did try the above, but it did not fix my issue with the ""group policy client service failed the logon". This problem was happening on 5 different RDS Nodes. I saw this post in another thread as well. I went through the steps but the appropriate keys were already there. When I boot up it shows the notification window twice that the group policy failed to connect, when I look in msconfig in services it shows the group policy service stopped.
So I go to component services with the intent of turning it on It is recommended that you shut down and restart MMC. I see you post this as the end all answer to this problem on a few sites, but its not effective if the registry values are already there and correct.
Office Office Exchange Server. Not an IT pro? Windows Client. Sign in. United States English. Ask a question. Quick access. Search related threads. Remove From My Forums. Answered by:. Archived Forums. Windows 7 User Interface. Sign in to vote. Or does have to do with other computers in my homegroup?
Would be Very Greatly Appreciated! Tuesday, November 6, AM. Wednesday, November 7, PM. I found that the key was intact, so, you do not touch anything here - just check that the key exists. Below are descriptions what must be present there. My laptop was missing it. Next, you must create a key a folder and name it GPSvcGroup - this key normally should be there, but, again, it was missin on my laptop. Saturday, February 2, AM. Sunday, February 10, PM. I have been trying to resolve this for months..
Monday, February 11, AM. Glad it helped. I am damn proud I was able to nail it down ;-. Sunday, February 17, AM. Took me 2 days to get through the gut of Windows and to get it right ;- Glad it helped. Thanks so much! Keep doing what you are doing!
Sunday, February 17, PM. It helped me too. Thank You so very much How'd you figure it out, would love to know. Tuesday, February 19, PM. How did I find the solution? I had another laptop which was healthy, and Group Policy Client service was running fine there. When banging my head against the wall trying to fix the issue, I came across the link I posted in my original post.
I found from the linked article where those parameters should be. The rest was easy - I just looked what was the keys on a healthy PC and re-created them on the faulty one. The result is documented above ;- Oh, yes, I also checked values on Win 7 Professional and Enterprise PCs, and confirmed that they are all the same.
What strikes me most is that this issue was out there for at least 3 years I tracked it back to Vista , and it is wide-spread I had to post my solution to good dozen of threads in different forums , but no one at Microsoft got to the root cause of it, not mentioning posting a fix.
Monday, February 25, PM. It worked perfectly! I appreciate it! Saturday, March 2, PM. Double amazing This was driving me nuts, thanks for saving my sanity. Saturday, March 16, AM. This is the funniest reply I got!
You made my day! Sunday, March 17, PM. Thanks again! Wednesday, April 10, PM. Seriously dude, you just won the Internet!!!! Friday, April 19, PM. Thx, took me a while to find this solution. It works fine. Once added the other users could login again. Saturday, April 27, PM. You sir absolutely ROCK! Thanks again, Nico. Sunday, May 5, PM. You are a legend, thanks. Saturday, May 25, PM. Monday, May 27, PM. Hope this helps.
0コメント