That message comes from Windows when a new password is checked against a local security policy — usually because the password is shorter than the Minimum password length, misses the Password must meet complexity requirements rules, or reuses a password blocked by Enforce password history. One fix does the job: make the password at least the required number of characters, include three of the four Windows character categories, and use something never set before on that account or computer. The exact thresholds are set in Local Security Policy or Group Policy, and the "age" part almost always concerns passwords changed too recently, not passwords that are too old.
This article is for anyone creating or resetting a password for their own account and for IT staff who manage the policy. It doesn't cover a Microsoft Entra ID cloud password policy, which shows different wording and enforces a banned-password list instead of the Windows complexity rules. The boundary matters because the two policies share a name but almost nothing else.
The message is a composite of five separate checks, and each one fails on its own. Length is a number of characters. Complexity is a count of character types. Age is a minimum and maximum number of days between changes. History is a count of remembered passwords. Once you know which check fired, the fix is usually a one-minute edit.
What each of the five policy checks actually enforces
Windows evaluates the policy at the moment you press Enter to set the password, and it reports a failure without telling you which rule you broke. Length and complexity are the two checks that stop most attempts. The default domain policy in a standard Windows Server environment requires seven characters and three of the four character categories, and Enforce password history is normally set to remember 24 passwords.
The four character categories in Windows are uppercase letters, lowercase letters, digits, and symbols. Complexity requires you to use at least three of them — so a password with upper and lower case plus a digit passes, even with no symbol. Uppercase counts only for characters A through Z; accented or non-English letters are treated as lowercase, which trips up people typing passwords in other scripts.
Two limits look unusual the first time you hit them. The password can't contain your account name or your display name, or any part of either that's three characters or longer. It also can't contain a run of more than two characters from the same set — "abc" or "123" or "qwerty" — which is why a long but alphabetical password can still fail.
Age runs in both directions, and only one direction produces this message. A maximum password age forces a change after a set number of days, and when the deadline passes Windows tells you the password has expired. A minimum password age blocks changes before a set number of days have passed, and that is the "age" failure people hit when they try to reset a password twice in a row.
Which of the five limits is failing on your machine
You can read the exact numbers instead of guessing. Open Local Security Policy from the Start menu search, then go to Account Policies and Password Policy. The right pane lists the six settings with their current values. If your computer is joined to a company domain, the numbers come from the domain and your local view may show "not defined" — that's expected.
For a domain-joined machine, run gpresult /r in a command prompt to see which Group Policy objects applied. The effective password policy normally comes from the Default Domain Policy on a domain controller, so a change made on your laptop won't move the numbers. Ask your IT team for the current thresholds if you can't read them yourself.
Here's a quick mapping from the message to the likely culprit:
| Policy setting | Default or common value | What fails | Typical symptom |
|---|---|---|---|
| Minimum password length | 7 characters in a standard domain policy | Password shorter than the value | Message appears with a very short password |
| Complexity requirements | Enabled | Fewer than three character categories, or a banned name or run | Long password still rejected |
| Enforce password history | 24 remembered passwords | Password equals a remembered one | Rejected right after a reset |
| Minimum password age | 1 day | Change attempted before the interval | Second reset same day fails |
| Maximum password age | 42 days in many older domain policies | Password kept past the deadline | Separate "expired" message |
A quick test narrows it down. Type a 20-character password mixing upper case, lower case, and digits that you have never used on this account. If it's accepted, the problem was length or complexity. If it's rejected, the problem is history or a settings mismatch.
How to build a password that passes complexity on the first try
The fastest reliable method is to build from a base you never reuse. Pick four unrelated words, join them without spaces, then add a digit and a capital letter where you'll remember them — for example a phrase built from a hobby, a street you lived on, and two random nouns. At 20-plus characters it clears every length limit in common use, and it mixes three categories if you add one digit and one capital.
Check the rules you're most likely to break before you submit. Confirm the password has at least three of the four categories, contains no run of three characters from the same set like "abc" or "789", and doesn't include your first name, last name, or username in any three-character-or-longer piece. Those three checks catch most "long password still rejected" cases.
Avoid the substitutions that look clever but add little. Turning an "a" into "@" or an "o" into "0" keeps the shape of the word and is one of the first transformations most cracking tools try. Length from unrelated words beats symbol swapping, and it's easier to remember.
Here's the sequence that works on a Windows 11 or Windows 10 local account:
1: Press Ctrl+Alt+Delete and choose Change a password, or open Settings, Accounts, Sign-in options, and select Password. 2: Type the current password, then the new one twice. 3: If the message appears, switch to a fresh 20-character password built as above and try once. 4: If it fails a second time, read the policy values in Local Security Policy before trying again.
Repeated failures don't lock the account, but they do waste a password change against the minimum age rule if one is configured. Make one careful attempt instead of five quick ones.
Why a password you've never used still fails the history check
History compares the new password against a stored list, and the list is per account, not per machine. A Windows local account and a domain account each keep their own record, so a password used on your domain login doesn't count against your local account and vice versa. The check uses the password's hash, which means changing one character is enough to pass — but changing case only often isn't, depending on how the hash is computed.
The common failure case is a forced reset. When IT resets your password from Active Directory Users and Computers, they set a temporary password that normally must be changed at next sign-in. If the change form rejects your new choice because of history, you're stuck until you pick something you've genuinely never used.
Another edge case catches people restoring an old machine. A restored system image can carry a password history that predates your last few changes, so the password you used six months ago counts as new. The fix is a fresh password rather than a remembered one.
If you manage the policy rather than follow it, history is one of the numbers you can lower without much gain — dropping from 24 to 10 trades a small amount of security for a lot fewer support calls from people cycling between two passwords.
The age rule is a floor, not a ceiling, and it trips up forced resets
A minimum password age of one day means you can't change a password again until a day has passed since the last change. That sounds harmless until you combine it with a forced change at next sign-in. If you reset twice within the same day — say you set a password, forget it, reset it, then want to change it again — the second change fails on age even though the password itself is perfectly valid.
The rule exists to stop people from cycling through the history list in a few minutes and landing back on their old password. With a history of 24 and no minimum age, a determined user could change the password 24 times in one sitting and return to the original. The floor of one day makes that impractical.
Administrators sometimes raise the minimum to several days on shared or high-turnover machines, which produces exactly this message for a user who is doing nothing wrong. If you hit it, the answer is to wait, not to keep trying — every attempt is rejected for the same reason.
The maximum age side is where the separate "password has expired" message comes from. A value of 42 days in older domain policies means the account prompts for a change every six weeks; setting it to 0 disables expiry entirely, which some modern guidance favors because forced rotation encourages predictable, incrementally changed passwords.
What the numbers look like on a domain controller versus a standalone PC
The defaults differ enough that the same password can pass on one machine and fail on another, which explains a lot of confusion when someone moves between a work laptop and a home PC.
| Environment | Minimum length | Complexity | History | Minimum age |
|---|---|---|---|---|
| Default Domain Policy (Windows Server) | 7 | Enabled | 24 passwords | 1 day |
| Windows standalone PC (Local Security Policy) | 0 | Disabled | 0 | 0 |
| Many corporate baselines after hardening | 12–14 | Enabled | 24 passwords | 1 day |
A standalone Windows installation ships with almost no password policy: zero minimum length, complexity off, no history, no minimum age. That's why the message never appears on a fresh home PC — there's nothing to fail. The moment the machine joins a domain, the domain's policy applies to the local account as well in most configurations, and the message starts appearing.
Hardened corporate baselines commonly push the minimum length to 12 or 14 characters and sometimes require longer for privileged accounts. If your organization has adopted one of those baselines, a 12-character password with three categories is the safe floor for an ordinary user account, and a 16-character passphrase is comfortable for anything with admin rights.
Where the message comes from in Windows and when it's a different problem
The message originates from the Windows security account manager when a password change is submitted, and it's triggered by the local security policy applied to the machine or the domain policy inherited from a controller. The same dialog appears in Settings, in the Ctrl+Alt+Delete screen, and in the netplwiz user accounts tool, so the wording is consistent no matter where you change the password.
Errors that look similar but aren't: "The password does not meet the password policy requirements" from a domain can also mean the password violates a fine-grained password policy applied to your user group, which overrides the domain default. If your department has a stricter policy, the numbers in Local Security Policy won't match what's actually enforced.
For Microsoft accounts and Entra ID cloud accounts, the wording differs. Those services reject passwords that appear on a banned list and don't apply the Windows complexity count, so a password that passes the local policy can still be rejected online. If the message names a corporate policy and your account signs in with a work email, confirm whether you're changing a domain password or a cloud one.
Network appliances and third-party applications sometimes reuse the Windows message for their own rules, particularly older file-sharing devices. When the wording appears in a non-Microsoft dialog, the policy it references is that product's, not Windows.
Fixing the policy as an administrator without breaking sign-ins
If you administer the policy, make changes on the domain controller rather than on individual PCs. Open Group Policy Management, edit the Default Domain Policy or a dedicated password policy object, and navigate to Computer Configuration, Policies, Windows Settings, Security Settings, Account Policies, Password Policy. Changes there apply at the next policy refresh, and gpupdate /force speeds that along on a test machine.
Order matters if you're tightening rules. Raise the minimum length first, then raise history, then enable complexity — and communicate the new numbers before you do. A sudden jump from 7 to 14 characters with complexity on generates a wave of locked-out users on the next expiry, and the help desk feels it for a week.
Test on a single pilot group before rolling out. Fine-grained password policies in Active Directory let you apply a stricter set to a test group and confirm that your users can still create and change passwords under the new numbers.
One trap for administrators: enabling complexity on a domain where users have passwords that predate the policy doesn't force an immediate reset. Users keep their existing passwords until the next scheduled change, at which point the new rule applies. That's usually the desired behavior, but it surprises people who expect the change to take effect at once.
Comparison: passphrase versus generated string versus vault-managed password
The three realistic approaches each pass the policy differently, and the trade-offs are about memory, not strength.
| Approach | Example shape | Passes length | Passes complexity | Remembered without help |
|---|---|---|---|---|
| Four-word passphrase | hobby street noun verb plus one digit and one capital | Yes, 20+ characters | Yes, three categories | Usually yes |
| Generated random string | 16 random mixed characters | Yes | Yes | Rarely |
| Password manager with a long generated password | 20+ random characters stored in the vault | Yes | Yes | Never |
A four-word passphrase is the most practical for a password you type daily, because it clears the policy and you can recall it. A generated random string is stronger per character but gets written on a sticky note within a week. A vault-managed password is the strongest overall, but it only works if you can reach the vault from the machine you're signing in to — a startup login on a machine with the vault locked is the failure case.
The verdict splits by use: passphrase for the Windows login you type every morning, vault-managed random password for everything else, and a generated string only for accounts you sign into once a quarter.
FAQ
Does changing just one character satisfy the history check?
Usually yes. History stores a hash of each remembered password, and a single changed character produces a different hash. The exception is when you change only the case of a letter on systems configured with certain hash settings, which can occasionally compare equal — so change a letter, a digit, or add a symbol rather than flipping case.
Can I get around the message by renaming my account?
No, and it can make things worse. The history and age checks attach to the account's security identifier, not its display name, so a rename keeps the same record. Renaming also breaks your profile path and any shortcuts tied to the old name, which is a lot of cleanup for no benefit.
Why does the password fail on my work laptop but work on my home PC?
Because the two machines apply different policies. A standalone Windows PC ships with no minimum length, complexity off, and no history, while a domain-joined laptop inherits the domain's policy, commonly 7 to 14 characters with complexity and a 24-password history. The password itself is fine; the policy in front of it is different.
How long do I have to wait if the minimum password age blocked the change?
Until the interval set in policy has passed, normally 24 hours. Windows won't count partial progress, so a change attempted at hour 23 fails the same as one at hour 1. If you need an immediate reset, an administrator can reset the password for you, which bypasses the minimum age rule by design.
Is a 14-character password with no symbols accepted?
Yes, if it uses three of the four categories. Complexity counts character types, not symbols, so upper case plus lower case plus digits satisfies it. A 14-character all-letter password fails because it only uses one category, which is the most common reason a long password gets rejected.
What's the difference between this message and "password has expired"?
Expiry is the maximum age rule firing after too many days since the last change; this message is a rejection at the moment of setting a new password. Expiry prompts you to change; this message blocks the change you attempted. Both come from the same policy, opposite ends of it.
One last note for anyone changing a password on a shared or corporate machine
Everything above is general technical information about how Windows password policy works and how the checks combine, not a security audit or a recommendation for your organization's policy. Corporate environments often add their own rules on top of the Windows defaults, and the numbers that apply to you come from your IT department or your domain administrator, not from this article. If you're locked out and can't resolve it with a fresh passphrase, contact your help desk; if the account is tied to sensitive systems, involve whoever owns the policy before changing anything yourself.