Password cannot be changed at this time

[Billy DIamond]

Has anyone encountered this issue with Duo on Windows machines? We use the "Microsoft RDP" Application.

We've noticed a recurring problem where users are prompted to change their password due to expiration, but receive the following error message:

"The password on this account cannot be changed at this time."

Interestingly, if the user reboots their machine and tries again, the password change goes through successfully.

The only consistent factor we've observed is that all affected users have Duo installed. Has anyone else seen this behavior or found a reliable fix?

Any insights would be appreciated!

[DuoKristina]

Can you please contact Duo support about this issue? They will want you to provide some log output and other info from an affected machine in order to investigate as a possible bug.

[DrH]

We have this problem too. It only happens at sites where Duo Authentication for Windows Logon is installed.

There are threads on Reddit and Spiceworks about it going back years. I've never found a working solution. Some people have suggested that it is triggered when a user tries to enter a password that doesn't meet length or complexity requirements. After that, even a valid password will not be accepted.

Duo support has not been helpful. It's always blamed on an Active Directory problem.

I don't think we've tried rebooting. By that stage the user has called our helpdesk and we reset their password for them. Quite annoying.

[NetanelZ]

A customer of mine has also encountered this error recently.

This might not be related to the old posts @DrH encountered.

I will try to contact support later, but I thought I should comment here.

[pfreg824]

Yes! I’m having the same issue — I’ve had multiple tickets opened with Duo about this. It didn’t seem to be an issue on version 4.3.1, so we reverted some clients to that older version. The problem appears more frequently in versions 5.0 through 5.1.1. Duo techs told me this issue would be resolved in the latest release that was supposed to come out at the end of October. Have you found anything else on this or heard of any fixes?

thank you!

[Billy DIamond]

I was really hoping this would be resolved in 5.1.1.