Random GPSVC failures prevent login to Windows 10 RRS feed

  • Question

  • Problem: random events prevent account log-in after upgrade to Windows 10 version 1703. System started as Windows 7 SP1 with special applications loaded. System was upgraded to Windows 10 version 1511 by in place upgrade using Windows 10-1511 media. System was upgraded to Windows 10 version 1703 by in place upgrade using Windows 10-1703 media. Media is DVD from Volume Licensing. All patches through KB4049011 and KB4053580 are applied. System is not part of domain and is not connected to internet. At unpredicable intervals, accounts are unable to successfully log-in. Messages may appear followed by system returning to pre-log-in screen after clicking OK. Sometimes a second or third login attempt may succeed; however, sometimes the PC must be manually rebooted. Messages observed are: -The Group Policy Client service failed the sign-in. The universal unique identifier (UUID) type is not supported. -The gpsvc service failed the sign-in. The remote procedure call failed. -The system cannot find the file specified. -The parameter is incorrect. -The task you are trying to do can't be completed because Remote Desktop Service is currently busy. Please try again in a few minutes. Other users should still be able to logon. [there is no Remote Desktop Session in progress] When able to successfuly log-in [usually as an administrator level account], there may be a message in the lower right corner stating "Windows could not connect to the gpsvc service. This preventsw standard users from sign-in." The message is only present briefly and is not consistently present. When log-in is successful, services MMC often shows Group Policy Client service as not running. The gpsvc service is set to Automatic. Although logged in with an administrator account, the buttons to Start the service are greyed out. Running "net start gpsvc" from administrator command prompt results in "Access is denied" Ran "sfc /verifyonly" with result of "Windows Resource Protection did not find any integrity violations." Set gpsvc to startup type 10, as described in https://support.microsoft.com/en-us/help/2976660/first-login-fails-with-the-universal-unique... -Symptoms did not change. Restored gpsvc to startup type 20. Created new account. New account displays the same issues; although it appears to be less frequent. Added GPSvcGroup to HKLM\Software\Microsoft\Windows NT\CurrentVersion\SVCHOST as described in https://answers.microsoft.com/en-us/windows/forum/windows_8-security/windows_8-group-policy-client-service-failed-sign... Restored SVCHOST to baseline condition, as this did not work. gpsvc is correctly a part of netsvcs. Reloaded old image of System and performed upgrade to Windows 10 version 1703 and problem occurred again. Faulty condition is present before and after applying patches. Application Event logs contain numerous Error 1000 entries for application name "svchost.exe_gpsvc" faulting module named "ntdll.dll" or "auditcse.dll" or "combase.dll" or "msvcrt.dll" Application Event logs contain numerous Information 1001 entries for "APPCRASH" associated with svchost.exe_gpsvc and DllHost.exe. System Event logs contain enties of "The Group Policy Client service terminated unexpectedly. It has done this x time(s)." The number has been as high as 10 times. The Event logs for "Application and Services Logs\Microsot\Windows\GroupPolicy" and "User Profile Service" contain Information events which appear normal when compared to other systems (which do not exhibit the issue). The gpsvc service may or may not be running after a successful login (as viewed in services MMC). Normally running "gpupdate /force" results in "User Policy Update failed"; however, "gpresult /R" shows that User Policy has been updated in the last 24 hours. A lot of man-hours have been burned in troubleshooting, without success. Reload of system to Windows 10-1703 is not a preferred option, as special applications require extensive reload time and configuration.
    Friday, December 15, 2017 10:35 PM

All replies

  • Hi Dwight,

    Have you got a temporary profile?

    Try the following (sorry - Shot in the Dark).

    From an Admin User:

    Open Registry Editor

    Navigate to:  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList

    Click each S-1-5 folder and double-click the ProfileImagePath entry to find out which user account it relates to

    double-click RefCount and change the Value data to 0  (has to be done from a different user name)

    S-1-5-21-514980757 … 1001 profile is (maybe) user name

    S-1-5-21-514980757 … 1007 profile is check here

    S-1-5-21-514980757 … 1019 profile is check here

    Close out and restart the computer.

    Besides, look at this similar case for a hint.

    Windows 10 - GPSVC service Failed the Sign on



    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, December 18, 2017 2:13 AM
  • Would you mind letting me know the update of the problem? If you need further assistance, feel free to let me know.

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, December 26, 2017 9:42 AM
  • The problem still exists, although it is becoming less frequent.  I opened a ticket with Microsoft [117121817340694] and sent a lot of event logs and time line for when the events were plentiful.  Still no luck in identifying a cause or fix.

    I am not getting a temp profile when the issue happens.

    The event log error messages are still present, even when able to login successfully.

    Basically, no fix, just that the events appear to be less frequent.

    Tuesday, January 9, 2018 9:13 PM
  • Have you had any progress with this issue?

    I've been dealing with the exact problem, Win 10 v1703, offline systems as well as domain offline network systems. Although, admin & regular user accounts have experienced login issues. I have observed if you enter password slowly on the first login attempt before submitting the login the issue occurs less frequent. We have a few of Win 10 v1709 machines in testing with just admin logins and we have not experienced the login issues.

    Could the issue be resolved in v1709? 

    Thursday, July 19, 2018 3:46 PM