Windows could not connect to the Group Policy Client Service problem

Markieboy1 used Ask the Experts™
I have two customer laptops that have the same problem.

Randomly - every few days - they produce the following error:

Failed connection to Windows Service
Windows could not connect to the Group Policy Client Service.
This problem prevent standard users from signing in.
As an administrative user you can review the system event log for details about why the service did not respond.

This affects certain programs. On one laptop, for example, it affects WIndows Live Mail.

Both computers have been updated from WIndows 8 Home to WIndows 10 Home. On one, the problem was occuring on WIndows 8, the other has started after updating to WIndows 10.

I have found that a system restore does the trick for a while but unfortunately the problem then returns.

I have tried some solutions available on the internet which are too long to mention here. They didn't work so, in the end, did a full reset of Windows 10 on both machines.

On one of the laptops the problem has come back. The other hasn't been returned to the customer yet. I haven't, however, experienced any issue although it isn't getting the use it would in situ.

I have tried to see if there is any relationship between the two computers and I can't really see anything. They are different makes of laptops with different anti-virus, email programs, Office programs etc.

They may be running the same drivers for some part of the system but I haven't fully checked this.

Any ideas, solutions etc. would be very much appreciated.
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Technical Systems Analyst
I have seen this many times - from what I have seen, it is caused either by a Windows "Fast Startup" feature issue, or something with the TCP/IP stack on the system.

First Suggestion:
 Just to be safe, run the system-file checker to make sure there are no core system file issues.
- In the search, type "CMD" and then right-click "Command Prompt" and select "Run as administrator".
- issue "sfc /scannow" in the command window. Let this run for a few minutes until it has completed.

Second Suggestion:
- Reset WINSOCK by opening command prompt as administrator (as above) and issue the following:
netsh then type: winsock reset
- Reboot the PC

If the issue is resolved, great. If it recurs, it may be the Fast Startup feature causing the grief. Information on how to resolve that problem can be located here:

Hopefully this helps get the issue sorted for you.


Thanks for your quick reply,

I have tried your first two suggestions before but with no luck. I would, however, suggest anybody else trying them as part of a solution.

The third solution - Fast Startup - is one I haven't tried but makes a great deal of sense especially as I have read many times that the problem could be due to updates when shutting down / restarting.

I have advised the customers - who now have their computers - to turn off Fast Startup and we will see what happens.

While I am unsure if things have being solved, I am willing to take the answers as the solution..although I may be back!!

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial