This error typically occurs when the password change request is sent to a domain controller that doesn’t yet have the current password or required configuration, or when access to the domain controller is blocked.
Use these steps to fix it:
- Retry against a local domain controller
If the password was recently reset on a different (remote) domain controller, wait for Active Directory replication to complete, then try again.
To avoid replication latency, perform the password reset/change on a domain controller in the same site as the user:- Open Active Directory Users and Computers.
- Right‑click the top node in the left pane and select Connect to Domain Controller.
- Choose a domain controller in the user’s site.
- Reset the user’s password and, if needed, select User must change password at next logon.
- Check for replication delays
If users in remote sites see this error when changing passwords, verify that:- The PDC emulator and other domain controllers are replicating correctly.
- Site links and replication schedules are configured so that password changes replicate promptly.
- Have the user log on with the latest password before changing it
In scenarios where a helpdesk reset the password (for example, frompassword1topassword2), ensure the user:- Logs on using the newly set password (
password2). - Then changes the password once replication has reached the local domain controller.
- Logs on using the newly set password (
- Try the password change again after replication
Once replication has completed and the local domain controller knows the current password, retry the password change. The operation should succeed when the domain controller recognizes the “old password” supplied during the change.
References: