KB: First logon to Windows 8 image deployed via ConfigMgr 2012 fails with "The universal unique identifier (UUID) type is not supported"

KB: First logon to Windows 8 image deployed via ConfigMgr 2012 fails with "The universal unique identifier (UUID) type is not supported"

  • Comments 3
  • Likes

KB73343332

After using System Center 2012 Configuration Manager or System Center 2012 R2 Configuration Manager to deploy a Windows 8 or Windows 8.1 image, when a user starts the system that has the image (physical or virtual) and tries to log on for the first time they receive the following error message:

The Group Policy Client service failed the sign-in.
The universal unique identifier (UUID) type is not supported.

This error message appears at first user logon after initial deployment of the image, however in some scenarios later user logons also result in the error.

After the message is displayed and the user clicks OK, the logon screen is displayed again.

For all the details including the cause and the steps to resolve the issue, please see the following:

KB2976660 - First logon fails with "The universal unique identifier (UUID) type is not supported" (http://support.microsoft.com/kb/2976660)

J.C. Hornbeck | Solution Asset PM | Microsoft GBS Management and Security Division

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

System Center All Up: http://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/
System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Windows Intune: http://blogs.technet.com/b/windowsintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The AD RMS blog: http://blogs.technet.com/b/rmssupp/

App-V Team blog: http://blogs.technet.com/appv/
MED-V Team blog: http://blogs.technet.com/medv/
Server App-V Team blog: http://blogs.technet.com/b/serverappv

The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • It's stupid that SCCM even has this problem. SCCM shouldn't be installing a Client-Side Extension (CSE) in the Windows image. MDT 2013 does not install a CSE, so there is no reason that SCCM should install a CSE either.

  • The workaround 1 doesn't work...
    I'll test soon workaround 2