Win10/Server2012 Login failures RRS feed

  • Question

  • I have a dozen computers that are running Win8.1 that authenticate to a Win2012R2 server with no problems.  I have now installed fresh Windows 10 installations on four machines.  I can log onto these machines locally or with a Domain admin account but cannot log on with any domain user accounts.  The error I get up is "The user profile service failed the sign-up.  User profile cannot be loaded".  

    I have seen plenty of fixes for this error on local profiles but none on domain ones.  The Win10 machines do not have the user profiles on them as they fail to authenticate to the server so there is nothing delete.

    I have one Win10 machine that does work fine but as they were all installed using the same image I can't see what the problem/solution is.

    Any ideas?

    Wednesday, November 25, 2015 7:13 AM


All replies

  • Did you try a different user ID ? YOu might need to delete the profile tht's giving this error. 

    Arnav Sharma | Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Thursday, November 26, 2015 2:59 AM
  • Try checking the registry whether there is some corrupted user profiles:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList

    Check the key profile image path whether the domain user accounts that you have tried to logon is listed there, delete the key and try again. Backup of course before doing any changes.

    Have you tried logging in with a profile connected with any hotmail account?

    Every second counts..make use of it. Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.
    IT Stuff Quick Bytes

    Thursday, November 26, 2015 7:18 AM
  • Hi Nathan_641,

    There're two related links below could be help with your issue: 

    (also used for domain account)

    Best regards,

    Thursday, November 26, 2015 9:57 AM
  • Hi Nathan_641,

    According your description, the problem may be caused by the same machine SID (one Win10 machine that does work fine but as they were all installed using the same image).

    To fix the problem, you need to change these computers security identifier. There is a Microsoft Sysprep tool available for changing machine SIDs.

    For detailed information about change SID with Sysprep.exe, here is a similar thread for your reference.

    The article below is about the problem of the same machine SID, you could have a look.

    The Machine SID Duplication Myth (and Why Sysprep Matters)

    Best Regards,


    Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact

    Friday, November 27, 2015 6:05 AM