Issue with Windows Administrator Authentication / UAC Prompts

שמחה אגרונוב 0 Reputation points
2026-11-16T07:10:43.55+00:00

Dear Microsoft Support Team,

I am experiencing an ongoing issue with Administrator permissions (User Account Control / UAC) on my Windows computer.

Whenever I try to install software or open Terminal as an administrator, the system prompts me for an administrator username and password. Although I enter the credentials of authorized administrator accounts from our office, the system fails to recognize or accept them, preventing me from completing the action. It appears to be a system or software malfunction affecting administrator authentication.

Could you please advise on how to resolve this issue or escalate it to technical support?

Please let me know if you need any system logs, error messages, or device details to assist with troubleshooting.

Best regards,
simha
[PII Masked by MSFT Moderator]

Windows for business | Windows Client for IT Pros | User experience | Other
0 comments No comments

3 answers

Sort by: Most helpful
  1. Daphne Huynh (WICLOUD CORPORATION) 2,620 Reputation points Microsoft External Staff Moderator
    2026-11-17T03:12:06.1633333+00:00

    Welcome to Microsoft Q&A!

    Thank you for taking the time to provide the detailed dsregcmd /status output.

    Based on the information you provided, the device is Microsoft Entra joined, not domain or hybrid joined:

    AzureAdJoined : YES
    DomainJoined : NO
    DeviceAuthStatus : SUCCESS
    AzureAdPrt : YES
    

    The combination AzureAdJoined : YES and DomainJoined : NO identifies a Microsoft Entra joined device. DeviceAuthStatus : SUCCESS also indicates that the device is present and enabled in Microsoft Entra ID. Therefore, the information so far does not indicate that the device's Microsoft Entra join itself has failed.

    The important distinction here is that successfully signing in with a Microsoft Entra account does not automatically mean that account has permission to approve Windows UAC elevation. Administrator-level operations require the user to have the applicable local administrator rights on that Windows device.

    For a Microsoft Entra joined device, Microsoft documents several ways administrator rights can be provided, including the Microsoft Entra Joined Device Local Administrator role, the Global Administrator role, the user who performed the Microsoft Entra join depending on how the device was provisioned, or an account explicitly added to the device's local Administrators group.

    Please complete the whoami /groups command you started and check whether the following entry appears:

    BUILTIN\Administrators
    

    If it does not appear, I recommend asking your organization's Microsoft Entra administrator to verify the local administrator assignment before troubleshooting the UAC prompt itself.

    If the Microsoft Entra Joined Device Local Administrator role was only recently assigned, the change might not take effect immediately. Microsoft documents that it can take up to four hours for a new Primary Refresh Token (PRT) containing the appropriate privileges to be issued, and the user must sign out of Windows and sign back in rather than simply locking and unlocking the session.

    The following procedure for refreshing the PRT:

    dsregcmd /refreshprt
    

    After running it, wait one or two minutes, sign out of Windows completely, sign back in, and then run:

    whoami /groups
    

    Check again for BUILTIN\Administrators

    Moreover, I noticed the AADSTS130004 message in AcquirePrtDiagnostics, stating that the user principal does not have the NGC key configured. However, the same output currently reports AzureAdPrt : YES.

    AcquirePrtDiagnostics records information about a PRT acquisition or refresh failure, whereas AzureAdPrt : YES means a PRT is currently present for the logged-in user. Therefore, I would not treat the AADSTS130004 entry alone as confirmation that the Windows Hello/NGC condition is causing your UAC credentials to be rejected. The local administrator membership should be verified first.

    If the administrator membership is correct but UAC still rejects the credentials, if BUILTIN\Administrators is present after the administrator assignment and PRT refresh, but Windows still rejects the credentials at the UAC prompt, the issue would need deeper investigation using information that is not available through a public forum, such as device-specific authentication events and potentially tenant-side Microsoft Entra authentication data.

    Furthermore, I understand that you originally asked whether this could be escalated to technical support. Unfortunately, Microsoft Q&A cannot create or escalate a Microsoft Support ticket on your behalf.

    Microsoft Q&A is a public community technical forum. I can help interpret the diagnostic information you provide, explain Microsoft documentation, and recommend documented troubleshooting steps, but forum responders do not have access to your organization's Microsoft Entra tenant, backend authentication logs, or Microsoft's support-case systems.

    In addition, a Microsoft Q&A thread and a Microsoft Support ticket are separate support channels and cannot be linked together as one support case. Posting the diagnostic information here does not create a Support incident and I cannot convert this Q&A thread into one or transfer/escalate it internally to a Microsoft Support engineer.

    Therefore, if the administrator membership is confirmed and the issue persists, please ask your organization's IT or Microsoft Entra administrator to open a new Microsoft Support request through your organization's available Microsoft support channel. The support engineer assigned to that ticket can then collect and correlate the required tenant/device authentication logs and investigate information that cannot be accessed from Microsoft Q&A.

    You can include the information already collected here in the new support request and please note to remove or mask any sensitive information before posting additional diagnostic output in this public forum, and never provide passwords, authentication codes, recovery keys, or other credentials.

    References: Troubleshoot devices by using the dsregcmd command - Microsoft Entra ID | Microsoft Learn

    How to manage local administrators on Microsoft Entra joined devices - Microsoft Entra ID | Microsoft Learn

    No local administrator group privileges on Microsoft Entra joined device | Microsoft Learn

    Troubleshoot Microsoft Entra hybrid joined devices - Microsoft Entra ID | Microsoft Learn

    Contact Microsoft customer support | Microsoft Support

    If you find it useful, please click Accept Answer.

    Thank you for choosing Microsoft Q&A.

    Was this answer helpful?

    0 comments No comments

  2. שמחה אגרונוב 0 Reputation points
    2026-11-16T07:14:21.2766667+00:00

    +----------------------------------------------------------------------+

    | Device State |

    +----------------------------------------------------------------------+

             AzureAdJoined : YES
    
          EnterpriseJoined : NO
    
              DomainJoined : NO
    
           Virtual Desktop : NOT SET
    
               Device Name : ?????
    

    +----------------------------------------------------------------------+

    | Device Details |

    +----------------------------------------------------------------------+

                  DeviceId : 3cbc1bae-4abd-44a8-8a1b-0ca7c70caae5
    
                Thumbprint : D8B154217BE60F91DFA679E351D3F5A6C79696C9
    

    DeviceCertificateValidity : [ 2026-10-04 11:26:58.000 UTC -- 2036-10-04 11:56:58.000 UTC ]

            KeyContainerId : 66c85a8c-f7bf-4c1e-a264-a8117891f67b
    
               KeyProvider : Microsoft Platform Crypto Provider
    
              TpmProtected : YES
    
          DeviceAuthStatus : SUCCESS
    

    +----------------------------------------------------------------------+

    | Tenant Details |

    +----------------------------------------------------------------------+

                TenantName : ???? ?????
    
                  TenantId : 80ce01bf-a80d-465e-8b31-699094a5a630
    
               AuthCodeUrl : https://login.microsoftonline.com/80ce01bf-a80d-465e-8b31-699094a5a630/oauth2/authorize
    
            AccessTokenUrl : https://login.microsoftonline.com/80ce01bf-a80d-465e-8b31-699094a5a630/oauth2/token
    
                    MdmUrl :
    
                 MdmTouUrl :
    
          MdmComplianceUrl :
    
               SettingsUrl :
    
            JoinSrvVersion : 3.0
    
                JoinSrvUrl : https://enterpriseregistration.windows.net/EnrollmentServer/device/
    
                 JoinSrvId : urn:ms-drs:enterpriseregistration.windows.net
    
             KeySrvVersion : 1.0
    
                 KeySrvUrl : https://enterpriseregistration.windows.net/EnrollmentServer/key/
    
                  KeySrvId : urn:ms-drs:enterpriseregistration.windows.net
    
        WebAuthNSrvVersion : 1.0
    
            WebAuthNSrvUrl : https://enterpriseregistration.windows.net/webauthn/80ce01bf-a80d-465e-8b31-699094a5a630/
    
             WebAuthNSrvId : urn:ms-drs:enterpriseregistration.windows.net
    
    DeviceManagementSrvVer : 1.0
    
    DeviceManagementSrvUrl : https://enterpriseregistration.windows.net/manage/80ce01bf-a80d-465e-8b31-699094a5a630/
    
     DeviceManagementSrvId : urn:ms-drs:enterpriseregistration.windows.net
    
                   KerbSpn : adrs/enterpriseregistration.windows.net
    
                   KerbUrl : https://login.microsoftonline.com/80ce01bf-a80d-465e-8b31-699094a5a630/kerberos
    
     JoinResourceSrvTlsUrl : https://certauth.enterpriseregistration.windows.net/EnrollmentServer/device/resource/80ce01bf-a80d-465e-8b31-699094a5a630/
    

    +----------------------------------------------------------------------+

    | User State |

    +----------------------------------------------------------------------+

                    NgcSet : YES
    
                  NgcKeyId : {6C457E08-85B8-4941-A539-784970ED80EF}
    
                  CanReset : DestructiveOnly
    
           WorkplaceJoined : YES
    
          WorkAccountCount : 1
    
             WamDefaultSet : YES
    
       WamDefaultAuthority : organizations
    
              WamDefaultId : https://login.microsoft.com
    
            WamDefaultGUID : {B16898C6-A148-4967-9171-64D755DA8520} (AzureAd)
    

    +----------------------------------------------------------------------+

    | SSO State |

    +----------------------------------------------------------------------+

                AzureAdPrt : YES
    
      AzureAdPrtUpdateTime : 2026-11-11 06:09:41.000 UTC
    
      AzureAdPrtExpiryTime : 2026-11-30 05:04:29.000 UTC
    
       AzureAdPrtAuthority : https://login.microsoftonline.com/80ce01bf-a80d-465e-8b31-699094a5a630
    
     AcquirePrtDiagnostics : PRESENT
    
      Previous Prt Attempt : 2026-11-16 07:06:18.181 UTC
    
            Attempt Status : 0xc00000d0
    
             User Identity : ******@odedlandau.com
    
           Credential Type : Certificate
    
            Correlation ID : 10050c14-35c0-477e-9542-0c3d8aacf032
    
              Endpoint URI : https://login.microsoftonline.com/80ce01bf-a80d-465e-8b31-699094a5a630/oauth2/token
    
               HTTP Method : POST
    
                HTTP Error : 0x0
    
               HTTP status : 400
    
         Server Error Code : invalid_request
    

    Server Error Description : AADSTS130004: UserPrincipal doesn't have the NGC key configured. Trace ID: aa170c16-89b4-4594-bcd4-83c63a43ac00 Correlation ID: 10050c14-35c0-477e-9542-0c3d8aacf032 Timestamp: 2026-11-16 07:06:18Z

             EnterprisePrt : NO
    
    EnterprisePrtAuthority :
    
                 OnPremTgt : NO
    
                  CloudTgt : YES
    
         KerbTopLevelNames : .windows.net,.windows.net:1433,.windows.net:3342,.azure.net,.azure.net:1433,.azure.net:3342
    

    +----------------------------------------------------------------------+

    | Work Account 1 |

    +----------------------------------------------------------------------+

         WorkplaceDeviceId : 2e6a70fb-a76b-48b7-9955-cfbfd3104868
    
       WorkplaceThumbprint : D87F0A204893BF275414F7D57712295C066D5A96
    

    DeviceCertificateValidity : [ 2026-10-07 11:58:06.000 UTC -- 2036-10-07 12:28:06.000 UTC ]

            KeyContainerId : 4b46e951-bb0a-4cf8-915a-27455710cc62
    
               KeyProvider : Microsoft Platform Crypto Provider
    
              TpmProtected : YES
    
         WorkplaceTenantId : d193fce0-3b0e-4057-bfea-381bf33d9f22
    
       WorkplaceTenantName : ???? ????? ????? ???????
    
           WorkplaceMdmUrl :
    
      WorkplaceSettingsUrl :
    
                    NgcSet : NO
    

    +----------------------------------------------------------------------+

    | Diagnostic Data |

    +----------------------------------------------------------------------+

        AadRecoveryEnabled : NO
    
    Executing Account Name : AzureAD\???????????, ******@odedlandau.com
    
               KeySignTest : PASSED
    
        DisplayNameUpdated : YES
    
          OsVersionUpdated : YES
    
           HostNameUpdated : YES
    
      Last HostName Update : NONE
    

    +----------------------------------------------------------------------+

    | IE Proxy Config for Current User |

    +----------------------------------------------------------------------+

      Auto Detect Settings : YES
    
    Auto-Configuration URL :
    
         Proxy Server List :
    
         Proxy Bypass List :
    

    +----------------------------------------------------------------------+

    | WinHttp Default Proxy Config |

    +----------------------------------------------------------------------+

               Access Type : DIRECT
    

    For more information, please visit https://www.microsoft.com/aadjerrors

    PS C:\Users\שמחהאגרונוב> whoami /groups

    Was this answer helpful?

    0 comments No comments

  3. AI answer

    2026-11-16T07:12:39.9333333+00:00

    If the office account is already authorized as a local administrator on this PC, enter it in the UAC prompt as AzureAD\[Email]; this selects the Microsoft Entra authentication context rather than treating the name as a local account.

    This format does not grant administrator rights—it only resolves the account correctly when that Entra identity already has local administrator permission. Since the credentials were already attempted normally, this is a different, low-risk test.

    Identify the device’s join state and current permissions

    Open a normal, non-administrator Command Prompt and run:

    dsregcmd /status
    whoami /groups
    

    Record these fields from dsregcmd /status:

    • AzureAdJoined
    • DomainJoined
    • WorkplaceJoined
    • AzureAdPrt

    In whoami /groups, look for BUILTIN\Administrators. If it appears with Group used for deny only, that is normal for an administrator’s non-elevated UAC token and still indicates group membership.

    Use the following routing:

    Join state Device type Required administration path
    AzureAdJoined : YES, DomainJoined : NO Microsoft Entra joined Entra role or Intune policy
    AzureAdJoined : YES, DomainJoined : YES Microsoft Entra hybrid joined Active Directory, Group Policy, or a hybrid-supported Intune policy
    AzureAdJoined : NO, DomainJoined : YES Active Directory domain joined Domain IT, Group Policy, or LAPS
    AzureAdJoined : NO, WorkplaceJoined : YES Entra registered, not Entra joined Existing local administrator or organizational management policy
    All three are NO Workgroup/local device Existing local administrator or Windows recovery

    A UAC credential prompt normally appears for a standard user and requires credentials belonging to a valid administrator account; changing or disabling UAC does not create the missing permission.^1^

    If the device is Entra joined only

    An administrator with at least the Privileged Role Administrator role can assign the Microsoft Entra Joined Device Local Administrator role:

    1. Open the Microsoft Entra admin center.
    2. Go to Entra ID → Devices → All devices → Device settings.
    3. Select Manage Additional local administrators on all Microsoft Entra joined devices.
    4. Select Add assignments, choose the approved administrator, and select Add.

    This option requires Microsoft Entra ID P1 or P2 and grants the role across all Entra-joined devices; it cannot be scoped to only this computer. Use it only if that tenant-wide scope matches organizational policy.^2^

    After assignment, sign out and back in—not merely lock and unlock. Propagation can take up to four hours. To request an immediate Primary Refresh Token refresh, run:

    dsregcmd /refreshprt
    

    Wait one or two minutes, sign out, sign back in, and verify:

    whoami /groups
    

    BUILTIN\Administrators should now appear.^3^

    If the device is hybrid joined or managed by Intune

    Do not use the Entra Joined Device Local Administrator role as the device-level fix for a hybrid-joined PC. IT should use one of these approved mechanisms:

    • Active Directory or Group Policy to manage the local Administrators group.
    • Windows LAPS if the organization maintains a unique local administrator credential.
    • Intune: Endpoint Security → Account protection → Create Policy → Windows → Local user group membership. For hybrid devices, select users with hybrid-supported identifiers such as a SID or domain\username.^4^

    The Intune profile supports Windows 10 20H2 or later and Windows 11. IT should check for conflicting Replace and Update rules because Replace takes precedence.

    If no usable administrator remains

    For an organization-owned or managed device, obtain IT approval before resetting it because this removes applications, settings, and potentially all local data.

    From the Windows sign-in screen:

    1. Hold Shift while selecting Power → Restart.
    2. Select Troubleshoot → Reset this PC.
    3. Choose the retention/removal option approved by IT.

    Microsoft’s supported guidance is that if no administrator account is available to change the affected account, the Windows device must be reset. Support cannot retrieve or bypass a lost administrator password.^5^

    For escalation, provide IT with:

    • The exact UAC rejection message or screenshot
    • The three join-state values above
    • AzureAdPrt status
    • Whether BUILTIN\Administrators appears in whoami /groups
    • Whether AzureAD\[Email] was tested
    • Whether the device is managed by Intune, Autopilot, Group Policy, or LAPS

    Do not send passwords, recovery keys, or authentication codes.


    References

    1. How User Account Control works
    2. How to manage the local administrators group on Microsoft Entra joined devices
    3. No local administrator group privileges on Microsoft Entra joined device
    4. Account protection policy for endpoint security in Intune
    5. Change or reset your local account password in Windows | Microsoft Support
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.