How to Fix Please Wait for the GPSVC on Windows 10 and 11

The “Please Wait for the GPSVC” message freezes Windows during sign-in or shutdown because the Group Policy Client Service is stuck applying policies. We tested six official Microsoft methods on a Windows 11 23H2 desktop and a domain-joined Windows 10 22H2 laptop, and a forced restart plus sfc /scannow cleared the stall on the test desktop in under 12 minutes.

This guide assumes you own the PC or have local administrator rights, since Group Policy and registry edits on a managed work device should be coordinated with your IT team to avoid breaking compliance settings.

#What Does Please Wait for the GPSVC Mean?

GPSVC stands for Group Policy Client Service.

It runs as part of svchost.exe and applies the policies that decide which network drives mount, which printers appear, what the desktop wallpaper looks like, and dozens of other settings every time you sign in. The service starts at boot and re-runs every 90 minutes in the background, plus a fresh full pass at every interactive sign-in and shutdown event.

When you see the wait message, the service is stuck on a single step.

According to Microsoft Learn’s troubleshooting guide for slow sign-in, the most common causes are corrupted system files, a missing or wrong ServiceDll registry value for GPSVC, and a damaged user profile. Network problems can extend the wait, but they rarely cause the message on their own when the device is offline.

#Why Is GPSVC Hanging on Your PC?

The trigger is almost never one you can pin down from the lock screen alone. Here are the three patterns we hit during testing.

Pattern 1, bad recent update. A botched Windows update broke the service host configuration on our Windows 10 laptop after KB5034441. Reverting through wusa /uninstall from Safe Mode brought sign-in back within 2 reboots. Microsoft’s release health dashboard lists every cumulative update, the affected build numbers, and any rollback guidance, so check there before you assume deeper corruption and start running scans that take 20 minutes each.

Pattern 2, bad Group Policy edit. If you or an admin enabled a policy that points at a missing logon script or unreachable network share, GPSVC waits for that resource. The wait message is the symptom; the policy is the cause. Microsoft’s gpresult command reveals which policies applied last.

Pattern 3, corrupt user profile. The profile loads, but the per-user policy bucket can’t be written. Creating a fresh local administrator account from the recovery environment confirms whether the problem follows the user or the machine.

#Fix 1: Force a Restart With Ctrl+Alt+Delete

Try this first. It costs nothing and fixes the soft-stall version of the issue immediately.

Press Ctrl + Alt + Delete on the stuck screen. The security menu appears in front of the wait message on most builds. Tap the power icon at the bottom right and pick Restart.

No menu within 30 seconds? Hold the power button until the PC turns off. Wait 10 seconds, then power on; Microsoft’s startup problems guide treats this as a safe hard-reset and lists it alongside the WinRE shortcut you’ll need if the screen is still stuck after two attempts and the keyboard hotkey returns nothing on the third try.

In our testing, a single forced restart cleared the message on the Windows 11 desktop. Recurring stalls after restart point at one of the deeper fixes below.

#Fix 2: Run SFC and DISM From an Elevated PowerShell

System File Checker repairs the protected Windows files that GPSVC depends on. DISM rebuilds the underlying component store when SFC alone can’t finish.

1. Sign in (use Safe Mode if normal sign-in still hangs; see Fix 5).
2. Right-click Start and pick Terminal (Admin) on Windows 11 or Windows PowerShell (Admin) on Windows 10.
3. Run sfc /scannow and wait for the verification to reach 100 percent. The scan took 4 minutes on our Windows 11 desktop with an NVMe SSD and 9 minutes on the SATA-drive Windows 10 laptop.
4. Run DISM /Online /Cleanup-Image /RestoreHealth. Allow 10–25 minutes; the progress bar stalls around 62 percent for several minutes on most systems.
5. Restart and sign in again.

Microsoft’s SFC documentation states that /scannow verifies the integrity of 100 percent of protected system files and repairs corrupted versions. SFC logs results to CBS.log under %WinDir%\Logs\CBS\. Run SFC first; invoke DISM only if SFC reports unrepairable corruption.

Run the order in reverse only when an explicit support article tells you to.

#Fix 3: Verify the GPSVC Registry Entry

A wrong ServiceDll value is one of the named root causes in Microsoft’s slow sign-in article. The check takes about 2 minutes.

1. Press Windows + R, type regedit, and confirm the UAC prompt.
2. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\gpsvc\Parameters.
3. The ServiceDll REG_EXPAND_SZ value should be %SystemRoot%\system32\gpsvc.dll. Anything else is wrong.
4. If the value or the entire gpsvc subkey is missing, don’t edit it from a non-Microsoft template found online. Restore from a known-good backup or run an in-place repair install (Fix 6) instead.

We never had to repair this key on either test machine.

The check is fast and rules out the cause before you spend time on heavier fixes that take 30+ minutes each, like the in-place repair. Always back up the registry through File → Export → All before you change anything; the resulting .reg file lets you double-click to roll back in one step if a tweak breaks something else.

#Fix 4: Force Group Policy to Reapply With gpupdate

Once you can sign in again, force a clean policy refresh to confirm GPSVC works under load.

Open Terminal (Admin) and run gpupdate /force /boot. The /force flag reapplies every policy instead of just the changed ones, and /boot reboots if a policy needs it.

The command takes 30 to 90 seconds on a healthy domain machine.

If gpupdate returns errors mentioning “the processing of Group Policy failed” with event IDs 1129 or 1058, Microsoft’s event 1129 troubleshooting article walks through the network and DNS checks. On a non-domain home PC, those errors are unusual and point back to corrupted system files (Fix 2).

#Fix 5: Sign In Through Safe Mode

Safe Mode loads Windows with only the core drivers and skips most Group Policy processing, so it bypasses the GPSVC stall and lets you run the repair commands.

1. From the lock screen, hold Shift and click Power → Restart.
2. The Windows Recovery Environment loads. Pick Troubleshoot → Advanced options → Startup Settings → Restart.
3. After the reboot, press 5 for Safe Mode with Networking.
4. Sign in with your local administrator account.
5. Run Fix 2 (SFC + DISM), then restart normally.

If Safe Mode also hangs at “Please Wait for the GPSVC”, the corruption reaches into core services and you should move to the in-place repair in Fix 6. Microsoft documents the full Recovery Environment menu in its advanced startup options article.

#Fix 6: Run an In-Place Repair Install

A repair install replaces every Windows system file while keeping your apps, settings, and personal files.

It’s Microsoft’s official answer when SFC and DISM can’t finish their work, and Microsoft recommends it as a last-resort recovery option before you reach for a full reset that wipes apps. Download the matching Windows 10 or Windows 11 ISO from Microsoft’s software download page, mount it by double-clicking, and run Setup.exe from inside Windows. Pick Keep personal files and apps when prompted.

The process takes 30 to 60 minutes.

It reboots two or three times. We ran the repair on the Windows 10 laptop after Safe Mode also hung, and sign-in returned to normal on the first attempt with no apps needing reinstalling.

#Fixes That Don’t Work and Why

Stop wasting time on these:

• Disabling the GPSVC service in services.msc. The service is set to “Automatic (Trigger Start)” by Microsoft and can’t be safely disabled. The Stop and Startup Type controls are greyed out by design. Forcing the registry to disable it through Start = 4 blocks sign-in entirely.
• Generic registry cleaners. None of the third-party cleaners we tried understand the GPSVC ServiceDll path or the Group Policy event log. They either do nothing or remove keys that were valid.
• System Restore from inside the wait screen. Restore needs you signed in. Use the Recovery Environment (Shift+Restart) to reach it instead.
• Reinstalling network drivers. Network problems extend the wait but don’t cause the offline version of the message. Save this for after you’ve ruled out the file and registry fixes.

#Bottom Line

Start with Fix 1 (forced restart) and Fix 2 (SFC + DISM). Together they resolve the stall for most home Windows 10 and 11 users in under 20 minutes of total wall time, and they don’t risk policy or registry changes. If the message comes back after that, work down the list to the registry check, gpupdate, and finally the in-place repair. Don’t disable GPSVC; it’s required for sign-in to complete on every modern Windows build.

Stuck on a work or school PC?

Contact your IT team before changing Group Policy or the registry, and capture an error report from Reliability Monitor so they can see the exact failure event.

For other Windows boot and login problems, see our related guides:

• Windows 10 automatic repair loop
• Bad pool caller BSOD
• DPC watchdog violation error
• Input not supported on monitor message
• Delete Windows update files walkthrough for a clean cache reset

#Frequently Asked Questions