How to fix Error 1326 on Windows 11

by

Troubleshooting Guide: Error 1326 – “The User Name or Password is Incorrect”

Why This Error Happens

Error 1326 typically occurs when Windows 11 attempts to authenticate against a network resource, mapped drive, or domain controller using cached, expired, or mismatched credentials. This can be caused by outdated entries in Credential Manager, a mismatch between the local account and the remote server’s authentication requirements, or account lockout policies (such as password expiration) on the target machine or domain. It may also arise from SMB protocol restrictions or NTLM authentication settings blocking the connection.

Step-by-Step Resolution Guide

Step 1: Clear Cached Credentials in Credential Manager

  • Open Control Panel > User Accounts > Credential Manager.
  • Look under Windows Credentials for any entries related to the target server or share.
  • Select the relevant entry and click Remove.
  • Restart the connection attempt to force Windows to prompt for fresh credentials.

Step 2: Verify Username and Account Status on the Target System

  • Confirm the username format matches the target’s requirement (e.g., DOMAIN\Username vs. Username@domain.com vs. local PCName\Username).
  • Check if the account is locked, disabled, or if the password has expired on the target server or domain controller.
  • If applicable, reset the password directly on the target machine and update it wherever it is used.

Step 3: Adjust Network and Security Policy Settings

  • Open Local Security Policy (secpol.msc).
  • Navigate to Local Policies > Security Options.
  • Locate Network security: LAN Manager authentication level and ensure it is set to Send LM & NTLM – use NTLMv2 session security if negotiated (or match the target server’s requirement).
  • Confirm Network security: Minimum session security for NTLM SSP based clients does not exceed what the remote server supports.

Step 4: Re-Map the Network Drive or Resource

  • Open File Explorer and select This PC.
  • Click Map network drive from the ribbon.
  • Enter the correct UNC path (e.g., \\ServerName\ShareName).
  • Check Connect using different credentials and manually enter the verified username and password.

Step 5: Check for Group Policy or Account Lockout Restrictions

  • Run gpresult /h report.html in Command Prompt to review applied policies.
  • Look for restrictions on Account Lockout Policy or Password Policy that may be rejecting valid credentials due to complexity or history rules.
  • Contact your domain administrator if Group Policy Objects (GPOs) are blocking authentication.

Alternative or Verification Steps

  • After completing the steps above, test the connection by accessing the network share or logging into the application again with the updated credentials — if successful, no further action is needed.
  • If the issue persists, try connecting from a different device using the same credentials to isolate whether the problem is local (client-side) or specific to the target server/domain configuration.