Why won't windows connect to the group policy client?

Anonymous
2012-11-04T18:34:27+00:00

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.

0 comments No comments
Answer accepted by question author
Anonymous
2016-08-21T13:45:28+00:00

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.

Was this answer helpful?

300+ people found this answer helpful.
0 comments No comments
Answer accepted by question author
Anonymous
2013-02-02T03:55:35+00:00

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:

  1. 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.
  2. 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:
  1. First called AuthenticationCapabilities and you must give it a value of 0x00003020 (or 12320 in decimal)
  2. 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)

Was this answer helpful?

100+ people found this answer helpful.
0 comments No comments

168 additional answers

Sort by: Oldest
  1. Anonymous
    2015-12-14T23:08:54+00:00

    This was exactly the problem I had on my laptop - thanks P.L.X. for the solution!  Like others in this thread, I think it started after some round of Windows updates nearly a year ago (maybe more) and I never bothered trying to sort it out until recently when I tried to add a standard user to my laptop and couldn't.  I really appreciate the helpful walk-through video that made it incredibly easy to fix (despite my trepidation about messing with the registry.)

    I am running Windows 7 Pro, in case that helps anybody to know if this solution will apply to them or not.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2016-01-05T20:59:08+00:00

    Many, many thanks

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-01-16T07:35:14+00:00

    Thank you PLX for your advice and video.  We upgraded our Windows 8 machine to Windows 10 about a month ago.  On start-up, we have had a truncated version of the message about not connecting to the 'Windows Policy Client Service' displayed for a short period.  This message ends with the comment '... as Administrator you can review".  Nothing i could do would allow me to scroll further to see what I could review and the message vanished after 10-15 seconds, so I was puzzled about what it all meant.  We have also been driven nuts by our HP printer which we used to use for scanning and printing via Wi-Fi.  After much pain and anguish (including have a HP technician take control of our computer, we managed to restore scanning by using the USB connection while continuing to print via wireless.  So next thing, there were 2 different printers and 'the system' always defaulted to the device that did not work.  I printed your advice by manually setting the printer after first trying to print to the default printer.  Guess what

    • after implementing the fixes given in your advice (the video was REALLY helpful here!), not only did the stupid truncated message disappear but the print job to the default printer - which i had forgotten about - suddenly fired up!  MAGIC!

    Thank you for your efforts in documenting the fixes - including the video - in a clear, plain and simple manner that allowed a dummy like me to actually make the changes without having to call in an expert.  It  is very much appreciated.  I hope my experience with Windows 10 gives others with this problem the courage to 'give it a go' and fix it themselves! 

    Cheers

    Was this answer helpful?

    0 comments No comments