When attempting to sign into a corporate, educational, or enterprise workstation running Windows 11, authentication may abruptly halt with the security alert: “The security database on the server does not have a computer account for this workstation trust relationship” accompanied by Win32 system error code 0x80070533 (or STATUS_NO_TRUST_SAM_ACCOUNT / 0xC000018B). This error prevents domain users from logging in, accessing mapped corporate network drives, or querying Active Directory resources. The error indicates that the mutual cryptographic trust relationship between your local computer account and the Active Directory domain controller is broken.
What Causes Error 0x80070533 in Windows 11?
Every workstation joined to an Active Directory domain maintains a computer account (represented as ComputerName$) in the domain database. Windows automatically negotiates and updates a secure machine account password every 30 days. Error 0x80070533 appears when:
- Desynchronised Machine Password: The workstation was disconnected from the corporate network for an extended period, or was restored from a virtual machine (VM) snapshot or system restore point, reverting the machine password to an obsolete hash.
- Computer Account Deleted or Disabled in AD: An Active Directory administrator inadvertently deleted, disabled, or moved the computer object to an inactive organizational unit (OU).
- Duplicate Computer SID: The Windows installation was imaged using Sysprep improperly, resulting in duplicate Security Identifiers (SIDs) conflicting on the domain controller.
- DNS Resolution Mismatches: The workstation is failing to resolve domain SRV records, communicating with an outdated domain controller that lacks replicated account changes.
Step 1: Sign in with a Local Administrator Account
Because domain logon is broken, you cannot sign in using your standard domain user credentials. You must access the machine using local administrator privileges.
- On the Windows 11 sign-in screen, click Other user.
- In the username field, specify the local machine name followed by a backslash:
(or.\AdministratorComputerName\LocalAdminUserName) - Enter the local administrator password and sign in.
Step 2: Test and Reset the Secure Channel via PowerShell
Windows PowerShell includes dedicated cmdlets to test and repair the secure machine channel without requiring an administrative unjoin and rejoin cycle.
- Right-click the Start Menu and choose Terminal (Admin) or PowerShell (Admin).
- Verify the status of the secure trust channel:
Test-ComputerSecureChannel -Verbose - If the output returns
False, the trust relationship is broken. - Execute the repair command, providing domain administrator credentials to re-authenticate the workstation:
Test-ComputerSecureChannel -Repair -Credential (Get-Credential) - In the authentication dialogue that appears, enter valid domain administrative credentials (e.g.,
domain\admin_user). - If the command returns
True, restart your computer and test domain user login.
Step 3: Reset the Machine Account via Netdom
If PowerShell cannot establish an automatic repair, the classic netdom command-line utility forces an immediate machine password sync against a specified domain controller.
- Open Command Prompt as administrator.
- Run the following command:
(Example:netdom resetpwd /s:<DomainControllerName> /ud:<Domain>\<AdminUser> /pd:*netdom resetpwd /s:dc01.corp.local /ud:corp\administrator /pd:*) - Enter the administrator password when prompted.
- Upon confirmation that the machine password was successfully reset, reboot the workstation.
Step 4: Unjoin and Rejoin the Active Directory Domain
If Active Directory administrative objects were recreated or severely damaged, performing a clean domain unjoin to a temporary workgroup completely rebuilds local trust tokens.
- Press Windows Key + R, type
sysdm.cpl, and press Enter to launch System Properties. - On the Computer Name tab, click Change….
- Under Member of, select Workgroup and enter
WORKGROUP. Click OK. - Enter local administrator credentials if prompted, and restart the PC when instructed.
- After rebooting into the local administrator account, return to
sysdm.cpl. - Click Change…, select Domain, enter your fully qualified corporate domain name (e.g.,
corp.local), and click OK. - Provide domain administrative credentials to create a brand-new computer account object in Active Directory.
- Reboot the system once more. Domain users will now authenticate smoothly.