How To Remove Password Policy In Windows 7

Unable to change Windows password and keep getting the error "The password you typed does not come across the countersign policy requirements"? How to make the system lock your account when a hacker tries to guess your password continuously? In this guide we'll show yous how to change the account lockout and password complexity requirement policy from Command Prompt, Local Security Policy Editor, or past exporting / importing your policy. These methods work on Windows x, viii, 7, Vista and XP.

Part 1: Local Security Policy
Office 2: Alter Countersign Complexity Requirement Policy
Part 3: Change Account Lockout Policy
Role iv: Change Local Security Policy by Exporting and Importing

Local Security Policy

Local Security Policy allows enforcing many arrangement-wide, user and security-related settings, such as password policy, account lockout policy, audit policy and user rights.

When you desire change a security setting this is how you launch the Local Security Policy Editor:

Press the Windows central + R to bring up the Run box.
Type secpol.msc and striking Enter.

When the Local Security Policy Editor opens, you can navigate to the security policy you're interested.

Note that the Local Security Policy Editor is not available on the Home edition of Windows. So if you lot're running Windows x/8/7/Vista/XP Home, you have to change the local security policy from Command Prompt.

Change Password Complexity Requirement Policy

In the left pane of Local Security Policy Editor, expand Account Policies then click Countersign Policy. In the right pane you come across a listing of password policy settings. Double-click on the policy you desire to modify, it will open the Properties box and yous can change the setting to desired value.

password-policy

Maximum password age
Gear up the maximum number of days that a countersign is valid. After this number of days, the countersign is expired and Windows will force y'all to alter the password at the adjacent logon. You lot tin can set the Maximum countersign age between i and 999, or ready it to 0 so your password volition never expire.
Minimum countersign historic period
This security setting determines the period of time (in days) that a countersign must exist used before the user tin can change it. Yous can set up a value between 1 and 998 days, or set information technology to 0 for allowing to modify password anytime. This policy allows y'all to limit how oftentimes a user may change the password.
Annotation: The Minimum password age must be less than the Maximum password historic period, unless the Maximum password age is set up to 0.
Minimum password length
Specify the least number of characters a password can have. You can set a value of betwixt 1 and xiv characters, or ready to 0 if you permit blank password. This policy can reject a user to set a brusque password that does not encounter a minimum password length. For security reasons you'll generally want passwords of at least six characters because long passwords are usually harder to crack than short ones.
Password must meet complication requirements
If this policy is enabled, passwords must meet the post-obit minimum requirements:
1. Be at least vi characters long
2. Contain a combination of at least iii of the post-obit characters: uppercase letters, lowercase letters, numbers, symbols (punctuation marks)
3. Don't incorporate the user's user name or screen name

You can too change the countersign policy from an elevated Control Prompt. This is especially useful if you're running Windows Habitation edition.
For example, if y'all want to change Maximum password age to 42 days, type the command:
net accounts /maxpwage:42

Prepare Minimum countersign age to ii days, type:
net accounts /minpwage:2

Set Minimum countersign length to iii characters, blazon:
net accounts /minpwlen:3

change-password-policy

Change Account Lockout Policy

In the left pane of Local Security Policy Editor, expand Account Policies and then click Account Lockout Policy. In the correct pane you come across three policy settings. Double-click on the policy and you can change the setting to desired value.

account-lockout-policy

Account lockout duration
Specify the number of minutes that a locked account remains inaccessible before it automatically becomes unlocked. Yous can ready the account lockout duration between i and 99,999 minutes. If you set information technology to 0, then a locked out account volition remain locked until an administrator manually unlocks that account. This policy has to ready along with Account lockout threshold policy.
Business relationship lockout threshold
Set the number of invalid logon attempts that are allowed before an business relationship becomes locked out. The lockout threshold can be prepare to any value from 0 to 999. If the lockout threshold is ready to zero, accounts will never exist locked out due to invalid logon attempts.
Reset account lockout counter after
Specify the time (in minutes) that must elapse after a failed logon attempt before logon endeavour counter is reset to 0. The available range is i minute to 99,999 minutes.
Note: The Account lockout duration must be greater than or equal to the Reset account lockout counter after time.

Here is how y'all can alter the account lockout policy from an elevated Command Prompt.
For example, if you want to set Account lockout duration to 30 minutes, type:
net accounts /lockoutduration:30

Prepare Account lockout threshold to five bad logon attempts, blazon:
net accounts /lockoutthreshold:five

Set Reset account lockout counter later to 10 minutes, type:
net accounts /lockoutwindow:10

change-account-lockout-policy

Change Local Security Policy by Exporting and Importing

How to copy local group policy objects from 1 auto to another? Is it possible to disable the "Password must run across complexity requirements" policy using Command Prompt? All these can be achieved by exporting & importing the local security policy. Here'south how:

Open an elevated Control Prompt.
Type the following command and press Enter. This will export all the settings of local security policy to a text file.
secedit.exe /export /cfg C:\secconfig.cfg
Open the C:\secconfig.cfg file with NotePad and you can view and alter the policy for your own purpose. For example, if yous want to disable the password complexity requirements policy, just set the value PasswordComplexity to 0 and salvage your changes.
Type the following control to import the local security policy from the file C:\secconfig.cfg. Of course, you tin move the secconfig.cfg file to some other figurer then import the policy.
secedit.exe /configure /db %windir%\securitynew.sdb /cfg C:\secconfig.cfg /areas SECURITYPOLICY
Restart your estimator and the imported security policy will take effect.