trio.so
How-Tos

Fix: The Group Policy Client Service Failed the Sign-In

Fix "The Group Policy Client service failed the sign-in" and "Windows couldn't connect to the Group Policy Client service": service, permissions, repair.

Mountain landscape representing leadership perspective and vision
Written by
Atena Ladchartabi

Content writer, trio.so

Published on
Modified on

"The Group Policy Client service failed the sign-in. Access is denied." means Windows could not start or reach the Group Policy Client service (gpsvc) during sign-in, so it refuses to log the user on. The most common causes are the service being stopped or disabled, wrong permissions on its registry key, a damaged user profile, corrupted system files, or a profile container that did not attach on a VDI. Work through the fixes below in order; they run from least to most invasive.

The same fault shows up under a second message: "Windows couldn't connect to the Group Policy Client service. This problem prevents standard users from signing in." The fixes are the same. Administrators can often still sign in, which is the clue that it is a gpsvc problem.

Before you start

  • You need a way in. Use a local or domain administrator account that still works, or boot into Safe Mode with Networking (hold Shift while choosing Restart, then Troubleshoot > Advanced options > Startup Settings).
  • Edits to the registry can stop Windows from starting. Export the key before you change it (File > Export in Registry Editor), and where you can, compare against a healthy PC with the same Windows version.
  • Take a restore point or a backup if the PC holds data that is not synced.

Fix 1: Check the Group Policy Client service

  1. Press Win + R, type services.msc, and press Enter.
  2. Scroll to Group Policy Client. Its status should be Running and its Startup type Automatic.
  3. If it is stopped, right-click and choose Start.
The Windows Services console, which lists Group Policy Client among the services.
The Services console. Scroll down the list to Group Policy Client.

On current Windows versions the Startup type is greyed out for this service, so you cannot change it here. If it is stopped or disabled, set it in the registry:

  1. Open regedit and go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\gpsvc.
  2. Check that Start is 2 (Automatic). Change it to 2 if it is not.
  3. Restart the PC.

Fix 2: Repair permissions on the gpsvc registry key (access is denied)

The "access is denied" variant often comes from missing permissions on the service key, usually after a security hardening tool or an incorrect script changed them.

  1. In Registry Editor, right-click the gpsvc key and choose Permissions.
  2. Check that SYSTEM and Administrators have Full Control, and Users have Read.
  3. If they do not, use Advanced to take ownership as an administrator, add the missing entries and apply them to child keys.
  4. Restart.

If you are not sure what the defaults are, open the same key on a healthy PC of the same version and copy what you see.

Fix 3: Repair system files with SFC and DISM

From a Command Prompt run as administrator, run these in order:

sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

Restart when they finish. DISM needs a connection to Windows Update, or a source you give it with /Source.

Fix 4: Repair or rebuild the user profile

If administrators can sign in but one user cannot, the profile is a suspect.

  1. Open regedit and go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList.
  2. Look for the user's SID twice, once with a .bak suffix. A .bak without a matching entry, or the reverse, means the profile registration broke.
  3. If you are sure which entry is right, remove the broken one, or rename the .bak entry to the proper SID, and set State to 0.
  4. If that does not work, rename the user's folder in C:\Users, delete the SID key, and let Windows create a new profile on the next sign-in. Copy the user's data from the old folder afterwards.

Fix 5: FSLogix, Citrix and other VDI profile problems

On virtual desktops, this error often means the profile container did not attach and the session fell back to a temporary profile before gpsvc could start cleanly.

  • FSLogix. Look at the profile logs in C:\ProgramData\FSLogix\Logs\Profile for the failing user. A VHDX that is locked by another session, a share with the wrong permissions or no free space are the usual causes. Fix the container, then sign the user in again.
  • Citrix Profile Management. Check the Citrix profile logs and the profile store path and permissions. A damaged profile folder on the store can cause the same failure.
  • Antivirus. Check the vendor's guidance for profile container exclusions.

Fix 6: Check Group Policy itself

A policy that restricts access or changes user rights on the registry or services can trigger this. On an affected PC, run:

gpresult /h C:\Temp\gpresult.html

Open the report and look for policies that touch Registry or System Services permissions, then test with the policy removed. To read a gpresult report, see how to enable Remote Desktop with Group Policy.

Fix 7: If nothing works

Back up the user's data, then reset the PC or restore from an image. Do this for a single PC. If sign-in fails on many PCs at once, look first at what changed on the network, such as a recent GPO or security baseline.

What causes the Group Policy Client service error?

CauseClueFix
Service stopped or disabledAdmin can sign in; gpsvc not runningFix 1
Wrong registry permissions"Access is denied" in the messageFix 2
Corrupted system filesStarted after a failed update or power lossFix 3
Damaged profileOnly one user affectedFix 4
Profile container failureVDI or roaming profilesFix 5
Restrictive policyStarted after a GPO or hardening changeFix 6

Managing this across many devices

Group Policy reaches domain-joined Windows machines. trio.so pushes policies to enrolled Windows, macOS, Linux, iOS and Android devices from one console. See policy management.

Related reading: enable Remote Desktop with Group Policy, disable Control Panel using Group Policy and how to disable a domain controller GPO.

Ready-to-use Templates

Must-have Template Toolkit for IT Admins

Explore All
Template Toolkit

Manage Windows devices without depending on Group Policy

trio.so applies policies, apps and patches to Windows devices from one console, and shows the status on each device. Start a 14-day free trial.

Start free trial

Manage Every Device From One Console

trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.

14-day free trial. No credit card required.

trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.

Smiling womanAbstract geometric patternAbstract geometric patternSmiling womanSmiling woman

Frequently Asked Questions (FAQ)

Have questions? We've got answers. This section covers some of the most commonly asked questions related to this topic.

Windows could not run gpsvc at sign-in. The usual causes are a stopped service, wrong permissions on the service's registry key, a broken profile, corrupted system files or a profile container that failed on a VDI.

Check the permissions on HKLM\SYSTEM\CurrentControlSet\Services\gpsvc. SYSTEM and Administrators need Full Control and Users need Read. Restart afterwards.

It is the same fault. Start with the service and registry checks, then SFC and DISM, then the profile.

Yes. Boot into Safe Mode, or sign in with a working administrator account, or use the Windows Recovery Environment command prompt to edit the registry offline.

Related

From the blog

The related industry news, interviews, technologies, and resources.