While logging into Windows, there are some crucial background processes are propagating. The Group Policy Service (GPSVC) is part of one of those processes in which this service communicates with Winlogon service via a Remote Procedure Call (RPC). The aim of this communication is to make a cross check on Computer Configuration and User Configuration of Group Policy Objects and load policies accordingly.
Generally, when this scenario is going on, the GPSVC is taking part in the chain of events separately from the beginning. But when the same service, i.e. GPSVC takes part in the processing, in combination with other processes, there are chances of following error to occur.
Group Policy Client Service failed the sign-in.
The universal unique identifier (UUID) type is not supported.
Due to this error your attempts to logon into the system will go into vain. The explanation behind this error is given as follows:
The case in which GPSVC is working into shared process environment, and its separation from the same environment plus failure to connect with Winlogon causes this error. Actually, the System Configuration Manager in the Windows Image, installs Client Side Extension which isolates GPSVC. Since RPC was made already, the GPSVC now can’t connect to Winlogon. In this way, the sign-in can’t proceed and Winlogon generates the error mentioned above.
Most probably you’ll face this error after creating a new user and logging into that user account, for the very first time. Here is how you can solve it:
FIX : ‘The Group Policy Client Service Failed The Sign-in. The Universal Unique Identifier (UUID) Type Is Not Supported.’ In Windows 10/8/7
Registry Disclaimer: The further steps will involve registry manipulation. Making mistakes while manipulating registry could affect your system adversely. So be careful while editing registry entries and create a System Restore point first.
FIX 1 – By Isolating GPSVC From Being Shared Process
1. Press + R and put regedit in Run dialog box to open Registry Editor (if you’re not familiar with Registry Editor, then click here). Click OK.
2. In the left pane of Registry Editor, navigate to following registry key:
3. Here, at this registry location, you need to take ownership of gpsvc key. You can adopt either of these two ways to take ownership:
4. Once you’ve successfully taken ownership of registry key, close Registry Editor. Open elevated or administrative Command Prompt and type following command, hit Enter key then:
reg add "HKLM\SYSTEM\CurrentControlSet\Services\gpsvc" /v Type /t REG_DWORD /d 0x10 /f
You must receive “The operation completed successfully” message. In case if you’ve not taken ownership of the registry key mentioned in step 3, the command will not execute and you’ll get Access is denied message.
So by executing the command successfully, we force the GPSVC to initiate as a separate process from the beginning rather than to act as shared process. Thus now GPSVC can communicate correctly with Winlogon and there is no error during sign-in process, hence user logon becomes successful.
FIX 2 – By Fixing GPSVC Startup (UPDATED: 21 Aug, 2017)
If you can’t boot and have single user/admin account on the machine, fix this issue by booting from Windows 10 installation media. Check following video for complete steps:
Hope this helps!