Vista SP1 The Group Policy Client service failed to start due to the following error: RRS feed

  • Question


    I recently started getting this error "The Group Policy Client service failed to start due to the following error:

    The service did not respond to the start or control request in a timely fashion" You can only logon the Vista Business if you are an administrator. If you don't have local administrative rights then you can not log in.


    I changed the services start time from 30 seconds to 60 seconds hopeing that might fix it but didn't. I goto the Group Policy Client service, right click but the Start, Stop, Pause, Resume, and Restart options are grayed out. It's set to automatic. RPC has started.





    <Event xmlns="">

    - <System>
      <Provider Name="Service Control Manager" Guid="{555908D1-A6D7-4695-8E1E-26931D2012F4}" EventSourceName="Service Control Manager" />
      <EventID Qualifiers="49152">7000</EventID>
      <TimeCreated SystemTime="2008-07-27T12:15:21.000Z" />
      <Correlation />
      <Execution ProcessID="0" ThreadID="0" />
      <Security />
    - <EventData>
      <Data Name="param1">Group Policy Client</Data>
      <Data Name="param2">%%1053</Data>
    Sunday, July 27, 2008 1:22 PM

All replies

  • Feel free to contact MS tech support if this issue is caused by the SP1 install. They are offering for a limited time, free tech support on SP1 issues. There are some exclusions that you can find on their site.



    Hope this helps.

    Sunday, July 27, 2008 5:17 PM
  • uninstall norton antivirus 2008 thats what i did and now the pc is works just fine and i was having the same problems that you had
    Monday, August 4, 2008 12:46 AM

    The crash of your computer after Windows Updates most probably caused that.  It has nothing to do with Antivirus or anything else.

    I had this issue on my laptop since November, and it really bugged me.  I sifted through the event log and found the pattern of events that preceded the issue, and, probably, caused it.

    In short, the pattern is as follows: Windows updates run automatically as scheduled, and when reboot is initiated after the updates are finished, the computer crashes (probably during reboot sequence).  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 during crash and Group Policy Client "don'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 was intact, so, you do not touch anything here - just check that the key exists.
    2. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SVCHOST This 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 - this key normally should be there, but, again, it was missin on my laptop.
    • 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 complete all steps above, reboot the computer and the problem will be fixed.

    Video walkthrough for those who are not very technical is here:

    I am so relieved I was able to fix it, and hope this will help others with the similar issue.

    • Proposed as answer by SQL-ER Sunday, February 17, 2013 6:39 PM
    Sunday, February 17, 2013 6:39 PM