The resolution is quite easy. Ignore all those tech geeks here and on other sites who just want to show off how they can fiddle with registries--a very dangerous game. Go to Search, type cmd, open cmd as Administrator. Type exactly this (with indicated spaces): netsh winsock repair then press Enter. You will need to Restart (NOT shut down and turn On) your computer. Bingo! Unfortunately this condition may re-occur from time to time, like if you Start your computer before turning on your internet and establishing a good connection. No sweat the fix takes about 3-5 minutes depending upon your computer Restart speed.
Why won't windows connect to the group policy client?
I am currently using a dell inspiron 7720 with windows 7 home premium and recently a small message has begun appearing above my taskbar saying
"Failed to connect to a windows service
Windows could not connect to the Group Policy Client service. The problem prevents standard users from logging on to the system.
As an administrative user, you can review the System Event Log for details about why the service didn't respond"
Anyone know why this is happening and how to fix it?
Windows for home | Previous Windows versions | Windows update
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
I FOUND SOLUTION TO THIS PROBLEM!
You did a great job on discovering the events BEFORE the issue started to occur. I had this issue on my laptop since November, and it really bugged me. Like you, I sifted through the event log and found absolutely the same pattern you described.
In short, the pattern is as follows: Windows updates run automatically, and when reboot is initiated after the updates are finished, the computer crashes. When it boots up, it reports that the last shutdown was unexpected, and the issue begins to occur.
I spent 2 days trying to dig out a solution from the Internet, to no avail, until I came across this page. It doesn't say anything about this particular problem, but it gives more information about SVCHOST process that starts many services, including Group Policy Client. It looks like during reboot a vital registry settings were lost and Group Policy Client simply "doesn't know" how to start. Let me explain:
There are two places to look in the registry:
- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services this path should contain gpsvc key (a folder), which is responsible for service parameters and configuration. I found that the key wasintact, so, you do not touch anything here.
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SVCHOSTThis is the most important path you should look into, as it must contain the keys and values referred in the key #1. Below are descriptions what must be present there.
- There must be Multi-String value called GPSvcGroup. My laptop was missing it. So, you should create multi-string value named GPSvcGroup and assign it value GPSvc.
- Next, you must create a key (a folder) and name it GPSvcGroup
- Then open newly-created GPSvcGroup folder and create 2 DWORD values:
- First called AuthenticationCapabilities and you must give it a value of 0x00003020 (or 12320 in decimal)
- Second is called CoInitializeSecurityParam and it must have value of 1.
Once you completed all steps above, reboot the computer and the problem will be fixed.
I am so relieved I was able to fix it, and hope this will help others with the similar issue.
Here is the link for video walkthrough: http://youtu.be/4m5KEmckWK4[http://youtu.be/4m5KEmckWK4](http://youtu.be/4m5KEmckWK4)
168 additional answers
Sort by: Most helpful
-
Anonymous
2016-03-23T07:54:12+00:00 Well if I refer to my last posting in praise of update KB3140768 stating everything was working fine. It was since March 8th up until last Monday 21st March 2016. Since last Monday we have gone back to how it was with the Group Policy Client issue again running riot. Cant understand why because we have not received any updates since so cant hold that responsible. Neither have I altered or added anything whatsoever to my computer, so this time for me it remains a complete mystery. Anyone else noticed.
-
Anonymous
2016-03-15T19:41:00+00:00 The problem cleared up on my PC also after the update.
However I have notice the ONLY Notification I get now is when Microsoft installs an update.
It's as if my other notifications have been turned off.
I hope that after reviewing my Notification settings and changing/resetting any of them the Policy problem does not return.
BTW Seems to me the problem is somewhere in the combination of the
Display/Power/Notification/Microsoft Sign-in Account usage settings.
-
Anonymous
2016-03-15T11:54:12+00:00 Hi Bristolred, Pleased its all working for you and you have managed to put it down to Kaspersky.
I have only been on McAfee during the lifetime of this latest computer (now two years old) and suffered the Group Policy problem almost for the full length of this period (with the exception of maybe 3 months) whilst on Windows 7 and now on Windows 10.
Here is the good news (as I write), and just hope that now I am making it public things dont take a turn for the worse.
But its looking really promising ever since last weeks windows update (March 8th 2016 KB3140768 ). Since then there have not been any problems whatsoever, with perhaps over 40 boot ups since that update. Which you would normally experience problems with at least one out of two boots (or 50%) boots. Also what I have noticed even when its a quick boot (only 10-15 seconds approx) when in the past is a sure sign of the Group Policy problem, since the update it works perfect and bringing in all the requested apps without problem even on a superquick boot which is another good sign.
It really looks good at present (well done Microsoft!), but obviously because of the long winded nature of this problem, I will have to wait a bit longer before I say ITS CURED FOR SURE and I am just hoping the next updates dont upset the situation.
Hope everyone else is doing OK with this since the updates.
Bryan.