Dear Russell McDowell
I think this issue often occurs when the password reset process is happening on a device or network that cannot properly communicate with your domain controllers or identity provider. When the change is not fully synchronized, the new password might appear accepted in the moment but fails afterward. Another reason is that cached credentials on your device may override your newly created password until the next successful sync with your account service. In those scenarios, the system reverts to the old password the next time you attempt to sign in.
Additionally, make sure your device has stable internet connectivity at the time you change the password, especially if you're using Azure AD or a hybrid environment. If the device is offline during the reset, the password update may only occur locally rather than in your directory. It’s also worth checking whether your organization enforces password complexity or history policies that may silently reject the change after it’s created. If the new password accidentally violates those policies, the system may accept it temporarily but not store it as the active credential.
In a few cases, conflicting sign-in methods like Windows Hello, cached PINs, or third-party credential providers may also interfere with your newly set password. If so, clearing cached credentials or re-registering your sign-in options often resolves the issue. I also recommend trying a password reset from a different device or browser to rule out local profile corruption. If you're in a domain environment, verifying replication health between domain controllers is another important step.
Please let me know if you'd like me to guide you through any of these checks in more detail. Your issue is absolutely solvable we just need to pinpoint which mechanism is blocking the new password update. If my explanation helps you move forward, feel free to hit “Accept Answer” so others with similar issues can find the solution easily .