Fix Windows Error 0X000008C6: Password Too Recent to Change

Cause 1: The Minimum Password Age Policy Is Blocking You

The most common culprit here is the Minimum password age setting in your domain's Group Policy. By default, Windows Server sets this to 1 day. That means if you changed your password yesterday, you can't change it again today. The system throws 0X000008C6 (which maps to NERR_PasswordTooRecent) to tell you to wait.

This policy exists to stop users from cycling through passwords quickly to get around the password history requirement. Annoying when you need to change it for a security issue, but that's the design.

To check and adjust it on a domain controller:

1. Open Group Policy Management Console (gpmc.msc).
2. Right-click your default domain policy (or whichever policy applies) and choose Edit.
3. Go to Computer Configuration > Policies > Windows Settings > Security Settings > Account Policies > Password Policy.
4. Double-click Minimum password age.
5. Set it to 0 if you want to allow immediate changes, or set a reasonable value like 1 day if you just need a temporary exception.

Remember, changing this affects all users in the domain. If you need a quick workaround for a single user without altering the policy, you can log into the domain controller and use Active Directory Users and Computers to reset the password for that user (resets bypass the age check). Or, if you're the administrator, you can always reset the password instead of changing it.

Cause 2: Password History Length Is Too High

The second common cause is the Enforce password history setting. This policy remembers the last N passwords and prevents reuse. If you're trying to set a password that's the same or similar to one you used a few changes ago, the system might flag it as too recent—even if the age policy isn't the issue.

Here's the deal: Windows compares the new password against the history list. If it matches one of the last, say, 24 passwords, you'll get an error. But the error message can be misleading—sometimes it says "password too recent" when it's really a history conflict.

To fix this, either choose a completely new password that you've never used before, or if you're the admin and need to allow reuse, lower the history count:

1. In the same Password Policy section, double-click Enforce password history.
2. Set it to 0 (not recommended for production) or a lower number like 5 if that works for your company policy.

But honest advice: keep the history high, like 10 or more. It's a security best practice. Just make sure users know they can't rotate back to an old password too quickly.

Cause 3: Local Account Policy on a Standalone Machine

Not on a domain? This error can also happen on a standalone Windows 10 or 11 machine if the local password policy has been tweaked. Most home machines have Minimum password age set to 0 days, but if someone changed it via secpol.msc or you're using an older Windows version, you might hit this.

To check locally:

1. Press Win + R, type secpol.msc, and hit Enter.
2. Navigate to Security Settings > Account Policies > Password Policy.
3. Look at Minimum password age and Enforce password history.

If the values are not 0, that's your problem. Set them to 0 for the minimum age (if you're admin), or wait the required days. You can also use the command line to see the policy:

net accounts

That shows you the current settings. To change minimum password age from command line (requires admin):

net accounts /minpwage:0

Run that and you're set. This is the quickest fix for a standalone machine.

Quick-Reference Summary

One last thing: if you're a regular user stuck with this error, don't try to hack around it. Talk to your IT admin. They can reset the password for you or adjust the policy if it's causing real problems. The error is annoying, but it's there for a reason.