If you guys are facing the above error while trying to login into a non-administrator account then you guys are at the right place. Since today we are going to discuss how you can fix this issue. The error clearly states that the Group Policy Client service failed whenever trying to log in the non-administrator users into Windows. However, using an administrator account there is actually no such error and the user can just easily login into Windows 10. In this article, we are going to talk about Windows Couldn’t Connect to the Group Policy Client Service. Let’s begin!
Well, as soon as the standard user tries to login into Windows he/she actually sees an error message” Windows couldn’t connect to the Group Policy Client service. Please consult your system administrator.” It clearly says consult your system administrator since administrators can log in to the system and then view the event logs for a better understanding of the error as well.
The main issue actually seems just like the Group Policy Client service isn’t running whenever the standard user tried to log in. And hence, the error message is displayed. However, administrators can log in to the system but they will also see the error message is actually the notification. That says “Failed to connect to a Windows service actually. Windows couldn’t connect to the gpsvc service. This problem avoids standard users from signing in” So without even wasting any time let’s now see how you can actually Fix Windows that couldn’t connect to the Group Policy Client service error along with the help of the below-listed troubleshooting guide as well.
- 1 Windows Couldn’t Connect to the Group Policy Client Service
Windows Couldn’t Connect to the Group Policy Client Service
Try System Restore
- Tap on Windows Key + R and type”sysdm.cpl” and then click on enter.
- Choose the System Protection tab and then select System Restore.
- Tap on Next and then select the desired System Restore point.
- You have to follow on-screen instructions to complete the system restore.
- Now after reboot, you guys may be able to Fix Windows couldn’t connect to the Group Policy Client service error.
Run SFC and DISM
- Tap on Windows Key + X and then click on Command Prompt(Admin).
- Now, just type the following in the cmd and click on enter:
Sfc /scannow sfc /scannow /offbootdir=c:\ /offwindir=c:\windows (If above fails then try this one)
- Just wait for the above process to finish and when done restart your PC.
- Then again open cmd and type the following command and click on enter after each one:
a) Dism /Online /Cleanup-Image /CheckHealth b) Dism /Online /Cleanup-Image /ScanHealth c) Dism /Online /Cleanup-Image /RestoreHealth
- Just let the DISM command run and now wait for it to finish.
- If the above command doesn’t really work then try on the below:
Dism /Image:C:\offline /Cleanup-Image /RestoreHealth /Source:c:\test\mount\windows Dism /Online /Cleanup-Image /RestoreHealth /Source:c:\test\mount\windows /LimitAccess
Note: Replace the C:\RepairSource\Windows along with the location of your repair source (Windows Installation or Recovery Disc).
- Just reboot your PC to save changes and see if you’re able to Fix Windows that couldn’t connect to the Group Policy Client service error.
Set Group Policy Client service to Automatic
Make sure you guys are logged in with the Administrative account in order to carry out the following changes.
- Tap on Windows Key + R and then type services.msc and click on Enter.
- Just find Group Policy Client service and then right-click and choose Stop.
- Now double tap on it and then make sure the Startup type is all set to Automatic.
- Next, you have to tap on Start in order to again start the service.
- Tap on Apply followed via OK.
- Now reboot your PC and this will Fix Windows that couldn’t connect to the Group Policy Client service error.
If you can’t open Windows Update Setting
- Tap on Windows Key + X and then choose Command Prompt (Admin).
- Then type the following command into cmd and click on Enter:
netsh winsock reset netsh winsock repair
- Reboot your PC in order to save changes and the error is resolved.
Registry Fix | Group Policy Client Service
- Tap on Windows Key + R and then type regedit and click on enter to open Registry Editor.
- Just now navigate to the following key in the Registry Editor:
- Now, find the value of imagepath key and then check its data. Well, in our case, its data is svchost.exe -k netsvcs.
- This actually means the above data is actually in charge of the gpsvc service.
- Now, just navigate to the following path in the Registry Editor:
- Now in the right window pane, just locate netsvcs and then double-tap on it.
- Just now check the Value data field and make sure gpsvc is not missing. If it’s not there and then just add the gpsvc value and be really careful in doing. So because you guys don’t want to delete anything else. Tap on Ok and close the dialog box.
- Next, just navigate to the following folder:
(This is not really the same key present under SvcHost, it’s actually present under the SvcHost folder in the left window pane)
- If netsvcs folder is not really present under SvcHost folder and then you have to manually create it. To do this, right-click on SvcHost folder and choose New > Key. Next, enter netsvcs like the name of the new key.
- Choose the netsvcs folder which you just created under SvcHost and in the left window pane right-click and choose New > DWORD (32-bit) value.
- Now enter the name of the new DWORD as CoInitializeSecurityParam and then double click on it.
- Just set Value data to 1 and click OK to save changes.
- Now similarly just create the following three DWORD (32-bit) Value under netsvcs folder and then enter the value data as specified below:
Name of the DWORD Value Data CoInitializeSecurityAllowLowBox: 1 CoInitializeSecurityAllowInteractiveUsers: 1 AuthenticationCapabilities: 3020
- Tap on Ok after setting the value of each of them and then close the Registry Editor.
Registry Fix 2
- Tap on Windows Key + R and then type regedit and click on Enter to open Registry Editor.
- Now navigate to the following registry key:
- Just make sure that the above key is in its location and then continue.
- Now just navigate to the following key:
- Right-tap on Svchost and choose New > Multi-String Value.
- Name this new string as GPSvcGroup and then double-tap on it to change its value to GPSvc and click on OK.
- Again right-tap on Svchost and choose New > Key.
- Now name this key as GPSvcGroup and click on Enter.
- Then right-click on GPSvcGroup and choose New > DWORD (32-bit) value.
- Name this DWORD as AuthenticationCapabilities and double tap on it to change its value to 12320 (make sure you are using a Decimal base).
- Just like that, create a new DWORD called ColnitializeSecurityParam and then change its value to 1.
- Now close Registry Editor and reboot your PC.
Turn off Fast Startup | Group Policy Client Service
- Tap on Windows Key + R and then type “powercfg.cpl” and click on enter to open Power Options.
- Tap on Choose what the power buttons do in the top-left column.
- Next, tap on Change settings that are currently unavailable actually.
- Just Uncheck Turn on Fast startup under Shutdown settings.
- Now tap on Save Changes and then Restart your PC.
This solution seems to be really helpful and should Fix Windows couldn’t connect to the Group Policy Client service error as well.
Well, That is all from my side. If you want to know more about this article or have any queries. Then feel free to ask me anything in the comments section below.
Have a Good Day!