Windows 8, group policy client service failed sign in

Anonymous
2012-12-25T13:27:15+00:00

Hello,

I'm running Windows 8 Professional, and in the last couple of days have experienced random errors trying to login.

Firstly, when I log in as a standard user, I get the message "Group policy client service failed sign in", and cannot login.  If I try to log in as Administrator I can log in but Windows recreates the profile from scratch and when I get to the start menu I have no apps displayed, and cannot find any programs via search.  This problem has happened twice now, and it seems to temporarily fix itself after rebooting, however this morning it took 4 reboots to fix.

I also get the error "Windows couldn't connect to the system event notification service", and again this seems to fix itself after a few reboots.

I have scanned my SDD on which the OS installed and there are no reported errors.

I am worried that on the next reboot the problem will revert and will not be fixable.  Please can you tell me how to fix this.

Kind regards,

Matthew

Windows for home | Previous Windows versions | Performance and system failures

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
2013-02-25T18:52:57+00:00

OK, guys, I already posted solution in other threads and it is for Windows 7. But, It looks like it is exactly the same issue, and a very wide-spread one - caused by crash during reboot initiated by Windows Update.  I am re-posting here.  If someone can test on Windows 8 would be great.  If you need my help let me know - I am actually very interested in testing it on Windows 8.

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

Here is the link to the video walkthrough if you have any troubles understanding what has to be done:http://youtu.be/4m5KEmckWK4

http://youtu.be/4m5KEmckWK4

Was this answer helpful?

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

162 additional answers

Sort by: Most helpful
  1. Anonymous
    2016-02-22T09:32:30+00:00

    Hi Juan

    Unfortunately you will continue with problems with Group Policy Client. Its a serious software malfunction that Microsoft are ignoring and I'm at a loss as to how to persuade them to get the problem resolved. Several of the Forum Members have abandoned Microsoft and gone to Apple, a route I'm seriously considering.

    Peter I King

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2016-02-21T19:15:15+00:00

    Thank you so much. This RESOLVEDmy problem. It makes sense how you explained it could have been corrupted. Most of the time, my kids close the computer without shutting down gracefully.

    In addition, I noticed the value on the image path did not reference the Group Policy Service but rather "ntsvc" and still worked.

    NOTE: Very nice video and explanation.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-01-30T01:09:56+00:00

    Reply to ChrisGoodhew -Well isn't that just a kick.  Had a feeling it was not over and thanks for the restart routine.  Will try it for awhile but I am too old to continue fighting this thing, as well as my computer skills for searching out this type of problem is very limited.  Thanks to all who have given me things to try out and work.  My next step is to just eliminate the problem all together and go to Mac.  Have been a die hard since computers were new with windows and the related services.  Believe it is time to quit fighting them as they obviously have no interest in fixing the problem.  When it affects enough people they will get the message the hard way.  I cannot believe that this is as limited as it appears to be as I am not seeing enough requests for service, etc. that I would think has to be out there.  Again thanks to all.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2016-01-30T00:14:52+00:00

    It will happen again in Win10.  Except that mmcss is a "hidden service" in Win10 (doesn't list in Computer Management with the other services).  I'm on autopilot now.  Close applications; command prompt NET STOP MMCSS; hard shut down (hold down power button until the world stops); restart; continue working until next time.  "Next time" is usually after an automatic update.  Somehow mmcss faults on an update, preventing gpcsrv from starting or being started.   Our PCs do not fault equally.  Worst is my key-tied-to-BIOS Win 8 Home laptop (HP), upgraded for free from win8->Win8.1->Win10 (about twice a week).  Try getting MS Assure service on that puppy!  They say that it is a HP problem, and HP doesn't want to know about it because it's BS.  Next worst is a (not tied to BIOS) win7PRO->win8->Win8.1->Win10 upgraded HP laptop, faults about once a week.  Best is a built-from-scratch (still OEM licence) Win8.1 PRO i7 tower, which hardly ever faults.

    Was this answer helpful?

    0 comments No comments