Control Userpasswords2: How It Works, Benefits, Security Risks, and Safe Use

QUICK ANSWER

control userpasswords2 opens the legacy Advanced User Accounts interface in Windows. It is effectively an alternative way to launch netplwiz, where administrators can inspect user accounts, change certain local account properties and group memberships, and—in configurations where the option is available—set up automatic sign-in.

The command does not remove or bypass a Windows account password. Automatic sign-in stores credentials so Windows can submit them during startup. This reduces physical security and should not be enabled on laptops, shared computers, business workstations, or any device containing sensitive information.

 

What Is Control Userpasswords2?

control userpasswords2 is a Run command that opens Windows’ legacy Advanced User Accounts dialog. On current Windows versions, it normally opens the same interface as:

netplwiz

You can use either command without including .exe.

Although Windows still includes this interface for compatibility and advanced administration, Microsoft directs most routine account management through Settings > Accounts. Settings is generally the preferred interface for adding or removing users, managing Microsoft accounts, and configuring sign-in methods.

Do not confuse control userpasswords2 with User Account Control, commonly called UAC. UAC controls elevation and administrator approval; control userpasswords2 manages certain user-account and sign-in settings.

How to Open Control Userpasswords2

1. Press Windows key + R.

2. Enter:

   control userpasswords2

3. Select OK or press Enter.

You can alternatively enter:

netplwiz

The command should open the User Accounts dialog. Opening the dialog normally does not require elevation, but Windows can request administrator approval or credentials when you attempt a protected change.

What the User Accounts Dialog Can Do

Available controls vary by Windows edition, account type, organizational policy, and device configuration.

View Sign-In Accounts

The Users tab displays accounts that the legacy interface recognizes for interactive sign-in. This can help administrators verify:

• Which local or connected accounts are available

• The user name Windows associates with an account

• Whether an account is a standard user or administrator

• Which account is selected for automatic sign-in

The list is not necessarily a complete inventory of every security principal, service identity, hidden system account, or cloud identity associated with the device.

To list local accounts separately, open Command Prompt and run:

net user

Microsoft documents net user as a command for displaying, adding, modifying, and deleting local or domain user accounts.

Add or Remove Users

Depending on the Windows edition and configuration, the dialog may provide Add and Remove controls.

Removing an account can delete its local profile data or make it inaccessible, depending on the method used. Before removing an account:

• Sign in with a different administrator account.

• Back up required files.

• Confirm that another working administrator exists.

• Do not remove an unfamiliar account merely because its purpose is unclear.

For normal account creation and removal, use:

Settings > Accounts > Other users

Microsoft’s current account-management guidance documents this Settings-based method.

Change Account Properties and Group Membership

The Properties option may allow an administrator to change details such as:

• Display information

• Local user name, where applicable

• Standard-user or administrator membership

• Custom local-group membership

Changing an account to Administrator grants it extensive control over the computer. Use a standard account for everyday work and grant administrator access only when necessary.

Renaming an account does not necessarily rename its existing profile folder under C:\Users. Attempting to rename that folder manually can break profile paths and application settings.

Reset Certain Local Account Passwords

The dialog may offer password-management controls for local accounts. These controls should not be treated as a general password-reset method for Microsoft, work, school, or domain accounts.

An administrator resetting another local user’s password may cause that user to lose access to information protected with credentials derived from the old password, including some encrypted files and stored credentials. Use the normal password-change or recovery process whenever possible.

Configure Secure Sign-In

Some configurations expose an option requiring users to press Ctrl+Alt+Delete before signing in. This key sequence is handled by Windows and helps ensure that the genuine Windows sign-in interface receives the credentials rather than a program imitating it.

Organization-managed devices may enforce this behavior through security policy, preventing users from changing it through the dialog.

Using Control Userpasswords2 for Automatic Sign-In

What Automatic Sign-In Actually Does

Automatic sign-in instructs Windows to log on to a specified account during startup without waiting for someone to enter the account password.

It does not:

• Remove the account password

• Convert the account to a passwordless account

• Disable authentication for network access

• Eliminate prompts after every lock, sign-out, or security event

• Bypass organizational policies

• Make the computer safe from unauthorized physical access

How to Configure It

Only consider these steps for a physically secured, single-purpose computer:

1. Press Windows key + R.

2. Run:

   control userpasswords2

3. Select the account that should sign in automatically.

4. Clear Users must enter a user name and password to use this computer.

5. Select Apply.

6. Enter the account’s user name and password when requested.

7. Confirm the password and select OK.

8. Restart the computer and verify the result.

Use the account’s actual password—not its Windows Hello PIN. A PIN is tied to the device and is not interchangeable with the account password.

For a Microsoft account, Windows may expect the Microsoft account address and its current password. If that password later changes, automatic sign-in may fail until the stored credentials are updated.

How to Disable Automatic Sign-In

1. Run control userpasswords2 or netplwiz.

2. Select the relevant account.

3. Select Users must enter a user name and password to use this computer.

4. Select Apply, followed by OK.

5. Restart and confirm that Windows requests sign-in credentials.

If automatic sign-in was configured with Microsoft Sysinternals Autologon, run that utility and select Disable instead.

Why the Automatic Sign-In Checkbox May Be Missing

The Users must enter a user name and password to use this computer option is not displayed on every device.

A common reason is the Windows Hello setting that allows only Windows Hello sign-in for Microsoft accounts. This setting disables password-based sign-in for those accounts. Microsoft places it under:

Settings > Accounts > Sign-in options > Additional settings

Its wording is similar to:

For improved security, only allow Windows Hello sign-in for Microsoft accounts on this device

Microsoft notes that available sign-in settings vary with the device configuration.

If you are evaluating automatic sign-in on an appropriate device, turning off this Windows Hello-only setting may make password-related controls available after you close and reopen netplwiz. Do not weaken Windows Hello protection merely to avoid entering a PIN on a general-purpose computer.

The checkbox may also be unavailable because:

• The computer is managed by an organization.

• Group Policy or mobile-device management enforces sign-in requirements.

• Passwordless Microsoft-account settings are active.

• The account or Windows edition does not support the expected legacy option.

• Security software or an organizational configuration restricts autologon.

On a managed computer, contact the IT administrator instead of attempting to bypass policy.

Security Risks of Automatic Sign-In

Automatic sign-in creates significant risks:

• Anyone who starts the computer can access the selected account.

• Stolen devices can expose local files and signed-in applications.

• Email, browsers, cloud storage, and VPN software may become accessible.

• Applications launched at sign-in run with that user’s permissions.

• An automatically signed-in administrator account greatly increases potential damage.

• Password changes can leave invalid stored credentials and cause sign-in errors.

Microsoft warns that automatic logon allows anyone with physical access to start the computer and use the configured account.

Do not enable it on:

• Laptops or tablets

• Shared family computers

• Public-access computers

• Administrator workstations

• Domain controllers or servers containing sensitive data

• Devices with confidential, financial, healthcare, or business information

• Computers subject to compliance or organizational security policies

Disk encryption such as BitLocker protects data while a device is powered off and locked, but it cannot protect files from someone who is automatically signed in after startup.

Microsoft Sysinternals Autologon

For a legitimate kiosk, display system, lab device, or other controlled deployment that genuinely requires automatic sign-in, Microsoft’s Sysinternals Autologon utility is preferable to manually placing a password in a registry string.

Sysinternals Autologon configures Windows’ built-in autologon mechanism and stores the supplied password as an encrypted Local Security Authority secret. Microsoft cautions that an administrator can still retrieve and decrypt it.

Therefore, encrypted storage reduces casual exposure but does not make automatic sign-in risk-free.

Why Manual Registry Configuration Is Discouraged

Windows autologon can be configured through values under:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon

However, Microsoft’s documented registry method can require the password to be stored in the DefaultPassword value. Microsoft explicitly warns that this value is stored in plain text and presents a security risk.

Manual registry configuration is also error-prone. Incorrect account, domain, or password values can produce failed logons or duplicate-looking entries on the sign-in screen. Prefer Sysinternals Autologon when automatic sign-in is an approved requirement.

Benefits of Control Userpasswords2

Used carefully, the tool offers several practical benefits:

• Quickly opens advanced account controls

• Provides a compact view of interactive user accounts

• Helps verify local account roles and group membership

• Supports certain legacy account-management tasks

• Provides access to automatic sign-in where Windows exposes the option

• Can help technicians diagnose account-selection and startup sign-in problems

• Works without navigating several Settings pages

Its primary advantage is convenience. It does not provide stronger security or broader management than current Windows administration tools.

Limitations

control userpasswords2 has important limitations:

• It is a legacy interface and may change or expose fewer options on newer builds.

• It does not replace Settings > Accounts.

• It does not fully manage Microsoft Entra ID, Active Directory, or Microsoft accounts.

• It is not a complete inventory of system and service identities.

• Windows Home does not include every administration console available in Pro or Enterprise.

• Organizational policies can override or hide its settings.

• Automatic sign-in may not work when a logon banner is enforced or when certain password restrictions apply. Microsoft documents these restrictions for Windows autologon.

• Changes to automatic sign-in do not necessarily change what happens after manually locking the computer.

Safer Alternatives

Use Windows Hello

For personal computers, Windows Hello provides convenient sign-in through a device-bound PIN, facial recognition, or fingerprint recognition. Microsoft describes Windows Hello as a more secure alternative to entering an account password directly.

Configure it under:

Settings > Accounts > Sign-in options

Use Windows Settings for Account Management

Use Settings > Accounts > Other users to add, remove, or change account types. This is the current, user-friendly management path documented by Microsoft.

Use Local Users and Groups

On supported professional Windows editions, administrators can run:

lusrmgr.msc

This console provides more detailed local-user and group management. It is not normally available in Windows Home.

Use Command-Line Administration

IT professionals can use documented commands such as:

net user

PowerShell and enterprise-management systems are more suitable when changes must be scripted, audited, or deployed consistently across multiple computers.

Troubleshooting

The Command Does Not Open

Try:

netplwiz

If neither command opens:

1. Restart Windows.

2. Install pending Windows updates.

3. Verify that C:\Windows\System32\netplwiz.exe exists.

4. Test from another administrator account.

5. On a managed device, check whether application-control policy blocks the executable.

6. Repair Windows system files only if other Windows components are also malfunctioning.

Automatic Sign-In Shows a Password Error

This usually means the stored credentials no longer match the account.

Common causes include:

• The account password changed.

• A Windows Hello PIN was entered instead of the password.

• The wrong account name or domain was stored.

• A Microsoft account address was entered incorrectly.

• The account was renamed, disabled, or removed.

• A new organizational policy prohibits automatic sign-in.

Re-enable the normal password requirement, confirm that the account can sign in manually with its password, and then reconfigure autologon only if it remains appropriate.

Two Similar Accounts Appear at Startup

This can occur when automatic sign-in contains an incorrect user name, account format, or password. Sign in using the valid account, disable autologon, restart, and verify the actual account name before configuring it again.

Do not delete an account merely because duplicate-looking sign-in tiles appear.

The Computer Still Requests Credentials

Determine when the prompt appears:

• At startup: Autologon may be incorrectly configured or blocked by policy.

• After locking: Lock-screen authentication can still be required.

• After sleep: Check sign-in requirements under Settings > Accounts > Sign-in options.

• After changing the password: Update or disable stored autologon credentials.

• Before a legal notice: A logon banner can prevent autologon.

• On a managed device: Group Policy or device-management rules may take precedence.

FAQ

Frequently Asked Questions

Are control userpasswords2 and netplwiz the same?

On current Windows systems, both normally open the same Advanced User Accounts dialog. netplwiz is the executable name, while control userpasswords2 is a legacy Control Panel command.

Does control userpasswords2 remove my password?

No. Clearing the password requirement for startup configures automatic sign-in by storing credentials. The account still has a password.

Should I enter my PIN when configuring automatic sign-in?

No. Use the account password. A Windows Hello PIN is a device-bound sign-in gesture and is not the account password.

Does the command work on Windows 10 and Windows 11?

It is commonly available on both, but the controls shown depend on the Windows build, edition, account type, Windows Hello configuration, and organizational policies.

Why can’t I see the automatic sign-in checkbox?

Windows Hello-only sign-in, passwordless-account settings, organizational policies, or device configuration may hide it. Check Settings > Accounts > Sign-in options, or consult the organization’s IT administrator.

Is automatic sign-in safe?

It is unsuitable for most personal and business computers because anyone with physical access can use the configured account. Consider it only for tightly controlled, single-purpose systems.

Can I use automatic sign-in with a Microsoft account?

It may work where Windows exposes the option, but it relies on the Microsoft account password rather than the PIN. Password changes can require reconfiguration.

Can control userpasswords2 manage domain or Microsoft Entra accounts?

It may display or modify limited properties for some connected accounts, but it is not a replacement for Active Directory, Microsoft Entra, Group Policy, or enterprise-management tools.

Is Sysinternals Autologon completely secure?

No. It stores credentials more safely than a plain-text registry password, but Microsoft states that an administrator can retrieve and decrypt the stored secret.

FINAL RECOMMENDATION / CONCLUSION

Use control userpasswords2 as a diagnostic and legacy account-management shortcut, not as the primary Windows account-management interface. Prefer Windows Settings for routine account changes and Windows Hello for convenient, secure sign-in.

Enable automatic sign-in only when there is a documented operational requirement and the computer is physically secured, centrally managed, and restricted to a low-privilege account. For approved deployments, use Microsoft Sysinternals Autologon instead of manually storing a password in the registry. Keep normal credential requirements enabled on laptops, shared computers, administrator workstations, and systems containing sensitive information.

 

#Windows #Windows11 #Windows10 #ControlUserpasswords2 #Netplwiz #UserAccounts #WindowsLogin #AutomaticLogin #WindowsAutologon #WindowsHello #Sysinternals #AccountSecurity #LocalAccount #MicrosoftAccount #ITSupport #WindowsAdministration #Troubleshooting

SOURCES

• Microsoft Support — Manage User Accounts in Windows.

• Microsoft Support — Sign-In Options in Windows.

• Microsoft Support — Configure Windows Hello.

• Microsoft Learn — Autologon (Sysinternals).

• Microsoft Learn — Configure Windows to Automate Logon.

• Microsoft Learn — Net User Command.