none
Computers Not Registering User Profile GUID RRS feed

  • Question

  • Hi,

    I have an issue where some users on some of my Windows 10 machines aren't registering their GUIDs in the registry from Active Directory.

    There should be a string value called Guid under the following registry key: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList\<profile>

    For these particular user accounts, it's missing. This is breaking some security software I use that relies on this. It's only happening to some users on some computers. They should be pulling the objectGUID attribute from Active Directory and using that value to populate the local computer's Guid string in the profile list.

    I'm thinking it's something computer-related instead of AD related because if it were AD, I would think it would be affecting all the machines. Beyond that though, I'm not sure where to go from here. I couldn't find anything on Google related to this. Could someone point me in the right direction? Thanks.

    Friday, May 29, 2020 2:52 PM

Answers

  • Unfortunately, I never found a fix for this. I had to fix this manually on each machine.

    I ran the following powershell on a DC to grab the SID and GUID:

    $username = "<username>"
    $identity = Get-ADUser $username -Properties ObjectSid
    $sid = [string]$identity.ObjectSid
    $guid = "{" + [string]$identity.ObjectGUID + "}"
    $sid
    $guid

    I ran the following on the PCs to add the key:

    REG ADD "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList\<sid>" /v Guid /t REG_SZ /d "<guid>"

    And I verified with the following:

    reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList\<sid>"

    Replace anything within the <> with the appropriate values for your environment.

    • Marked as answer by asifuentes Tuesday, July 7, 2020 3:50 PM
    Tuesday, July 7, 2020 3:49 PM

All replies

  • Hi,

    Thanks for sharing here!

    Before going further, I would appreciate your help in clarifying the following situations:
    The issue happened for some users in some win10 machines,right?
    Are there any related events ?
    When the users log into the machines , any errors happened?

    I would recommend you using the netlogon.log file for troubleshooting .The netlogon.log file located in %SystemRoot%\Debug can be invaluable for troubleshooting client logon and related issues.

    To enable Netlogon logging, use the following command:
    > nltest /dbflag:0x2080ffff
    To disable Netlogon logging, use the following command:
    > nltest /dbflag:0x0

    Also, the logon process can also be monitored  for troubleshooting by using the process monitor.

    Best Regards,
    Fan




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

    Monday, June 1, 2020 1:07 AM
  •  

    Hi,

     

    Just want to confirm the current situations.

    If there's anything you'd like to know, don't hesitate to ask.

     

    Best Regards,

    Fan


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

    Wednesday, June 3, 2020 1:14 AM
  • Yes, it is only happening for some users on some Windows 10 machines.

    I checked both event viewer and netlogon.log and didn't find anything unusual. Could you point me in the direction of what I should be looking for?

    Wednesday, June 3, 2020 2:22 PM
  • Hi,

    Then i would recommend you use the process monitor and the network monitor to capture more information for troubleshooting.

    If there are any updates ,welcome to share it.

    Best Regards,

    Fan


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

    Thursday, June 4, 2020 1:41 AM
  • Has a fix for this been identified? So far we've had to manually copy the GUID from AD and paste it into the User's registry. This is only happening with a handful of users so far, but the number is increasing over time. Any help would be appreciated.
    Monday, July 6, 2020 11:13 PM
  • Unfortunately, I never found a fix for this. I had to fix this manually on each machine.

    I ran the following powershell on a DC to grab the SID and GUID:

    $username = "<username>"
    $identity = Get-ADUser $username -Properties ObjectSid
    $sid = [string]$identity.ObjectSid
    $guid = "{" + [string]$identity.ObjectGUID + "}"
    $sid
    $guid

    I ran the following on the PCs to add the key:

    REG ADD "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList\<sid>" /v Guid /t REG_SZ /d "<guid>"

    And I verified with the following:

    reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList\<sid>"

    Replace anything within the <> with the appropriate values for your environment.

    • Marked as answer by asifuentes Tuesday, July 7, 2020 3:50 PM
    Tuesday, July 7, 2020 3:49 PM