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: Oldest
  1. Anonymous
    2014-01-14T18:19:12+00:00

    Excellent advice, worked first time. Many thanks.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2014-01-18T22:53:09+00:00

    Hi everyone.  My steps to fix this are based on everyone's postings but were in a  bit different order than those stated so I thought I'd post what I did to reach the fix.

    Based on what I did the root cause has something to do with Windows Updates and restarting...

    1. The standard user account login on my Windows 8.1 installed Lenovo Laptop was working in the morning today but stopped working in the afternoon.
    2. When logging into the standard user account the following pop-up error message appeared:

    Failed to connect to a Windows Service.

    Windows couldn't connect to the Group Policy Client. 3. When I clicked OK the Restarting message appeared and 1-2 minutes to get back to the login prompt. 4. I didn't have any files saved or an Outlook .pst under the standard user account so I logged in with an Admin account and deleted the standard user.  You will get a warning from Microsoft that all the files will be lost for this user if you do this, so if you do have file or an Outlook .pst file I don't recommend deleting the standard user.  Instead you should keep the standard user in place, login with an admin user and identify all .pst and other user specific files and back them up to a USB drive for safekeeping.I rebooted, logged in with my Admin account and tried re-creating the user with the same @outlook.com email account name. 5. The account registration process didn't continue, after 1-2 minutes the following error message appeared:

    We're sorry but something went wrong.  This user wasn't added to the PC.

    Code: 0x800770426 6. I searched the Internet and found this page: http://answers.microsoft.com/en-us/windows/forum/windows_8-security/windows-8-group-policy-client-service-failed-sign/7ce8e193-6651-4f8f-b2c3-28de3d389b1a 7. I did the steps in P.L.X.'s February 25, 2013 posting.  I had to do both item 1 and item 2 as they weren't there. 8. I rebooted using charms and selecting "Power....Restart and Update".  It's important to note here that the laptop restarted and didn't apply any updates.  When I tried adding a standard user again with no luck. 9. I did MatthewRiley's February 11, 2013 GUID steps but found the GUID didn't exist in the registry so there was nothing to delete. 10. I did BennettGibson's January 30, 2013 CTRL-ALT-DEL and disabled all startup services (except for the mousepad). 11. I rebooted using charms and selecting "Power...Restart and Update".  It's important to note here that the laptop restarted and didn't apply any updates. 12. When I tried adding a standard user again IT WORKED!~ 13. I went back into CTRL-ALT-DEL and enabled everything except for Java and McAfee. 14. I rebooted using charms and selecting "Power...Restart and Update".  This time 1 of 16 updates were applied. 15. I checked adding another standard user again and IT WORKED!~ 16. I went back into CTRL-ALT-DEL and enabled everything. 17. I rebooted using charms and selecting "Power...Restart" - note that "and Update" wasn't part of the Restart option any more. 18. I checked adding another standard user again and IT WORKED!~.

    Looks like something was blocking the application of the updates for sure and disabling the startup items seemed to be key, along with the GPSvc registry settings and "Restart and Update".  I can't test now but it would be good to know if as an admin user you do "Restart and Update" without the other steps if it's possible and if it fixes the problem.

    All the best.

    Cheers,

    cH>

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2014-01-21T20:11:56+00:00

    Thanks, was having this problem on my laptop, followed your youtube video as never done registry updates before.

    All sorted now, much better than microsoft!!!

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2014-01-30T02:24:52+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.

    Just logged in to say Thanks !!!

    Worked like a charm... Windows 8.1 Pro

    Thanks again.

    Was this answer helpful?

    0 comments No comments