Windows 11 Local Users and Groups: Open, alternatives, and tips

If you need to create, edit, or troubleshoot accounts on a Windows 11 PC, the Local Users and Groups tool remains one of the fastest and most precise ways to manage local accounts — and this guide walks through every supported method to open it, explains what to do when the snap‑in is unavailable (most commonly on Windows 11 Home), and lays out safe alternatives, automation options, and risks to watch for.

Background / Overview​

Local Users and Groups is a Microsoft Management Console (MMC) snap‑in that exposes local user accounts, groups, and membership management on a single machine. It is the go‑to tool for administrators who must set passwords, change group membership, enable or disable built‑in accounts, and apply granular local account changes that the Settings UI doesn’t expose. The typical console filename is lusrmgr.msc and it can be launched like any MMC snap‑in on Windows systems that include it.
Historically, Local Users and Groups is available in Professional, Enterprise, and Education SKUs but is not present by default in Home SKUs of Windows — a restriction that continues in Windows 11. That omission is important: if you try to run lusrmgr.msc on Windows 11 Home you will either get an error or nothing will happen, and you will need to use Settings, command‑line tools, or a controlled workaround to get the same results. fileciteturn0file0turn0file10

---

Quick methods: five reliable ways to open Local Users and Groups​

Below are the most common, supported ways to open Local Users and Groups in Windows 11. Each method is short and works on systems that include the snap‑in (typically Pro and above).

1. Run box (fastest)​

• Press Windows + R to open Run.
• Type lusrmgr.msc and press Enter.

This launches the Local Users and Groups console directly. It’s the shortest route for admins who prefer a direct MMC invocation.

2. Computer Management (recommended for context)​

• Right‑click the Start button or press Windows + X and choose Computer Management.
• In the left pane expand System Tools → Local Users and Groups → Users or Groups.

Computer Management bundles other admin tools (Event Viewer, Disk Management, Services) so it’s ideal when you need to do more than just user/group edits.

3. Command Prompt (elevated)​

• Open Start, search cmd, right‑click Command Prompt and choose Run as administrator.
• Type lusrmgr.msc and press Enter.

This method is useful for remote scripted workflows or when you already have an elevated shell open.

4. PowerShell (elevated)​

• Open Windows Terminal or PowerShell as administrator (Win + X → Windows PowerShell (Admin) or Terminal).
• Run: lusrmgr.msc

PowerShell and Command Prompt both simply call the same MMC snap‑in; use whichever command environment fits your workflow.

5. Control Panel → Administrative Tools​

• Open Control Panel → Administrative Tools → Computer Management.
• Expand System Tools → Local Users and Groups.

This is the classic GUI route for admins who navigate via the Control Panel. It’s slower but useful when you prefer menu paths over typed commands.

---

When the snap‑in is missing (Windows 11 Home and other cases)​

If lusrmgr.msc does not start, first confirm the Windows edition. Local Users and Groups is typically absent on Windows 11 Home and some specialized SKUs; attempting to open the MMC there will fail. If you are on Home, use Settings > Accounts for basic tasks, or rely on command line alternatives described below. fileciteturn0file0turn0file10
If you expect the snap‑in to be present (Pro/Enterprise/Education) but it doesn’t appear, the MMC may simply lack the snap‑in registration. You can add it manually:

• Open an MMC console: press Windows + R, type mmc and press Enter.
• In the new MMC window choose File → Add/Remove Snap‑in.
• Select Local Users and Groups → Add → Local computer → Finish → OK.

This restores the snap‑in in environments where the MMC was reset or the snap‑in was removed.

---

Alternatives when Local Users and Groups is unavailable​

Windows provides built‑in command‑line and GUI alternatives that match most administrative needs even on Home:

• Settings → Accounts → Other users: add and manage accounts at a basic level (create local accounts, switch account types). This is the supported UI alternative on Home.
• net user and net localgroup commands: universal, scriptable, and available on Home and Pro alike. For example: net user NewUser NewPass /add and net localgroup Administrators NewUser /add. These commands provide immediate account creation and group membership changes. fileciteturn0file0turn0file3
• PowerShell cmdlets: New‑LocalUser, Add‑LocalGroupMember, Set‑LocalUser provide a more modern, object‑oriented interface for scripted operations. Example: New‑LocalUser -Name "NewUser" -Password (ConvertTo‑SecureString "P@ssw0rd" -AsPlainText -Force). fileciteturn0file0turn0file3
• Netplwiz (User Accounts dialog): press Win + R → netplwiz for a lightweight UI that can create and change account properties. This utility remains useful for autologin and quick user creation.

If you need full lusrmgr.msc functionality on Home for one‑off administrative work, consider temporarily upgrading to Pro, or use an IT‑grade workaround—bearing in mind the security and support tradeoffs noted below.

---

Common tasks — step by step (using Local Users and Groups and alternatives)​

Create a new local user (MMC)​

• Open Local Users and Groups → Users.
• Right‑click the Users folder and select New User….
• Enter username, password and options (Password never expires, User must change password at next logon, etc.).
• Click Create and Close. Optionally add the new account to Administrators via the Groups tab.

Create a new local user (Command Prompt)​

• Open elevated Command Prompt.
• Run: net user NewUser NewPassword /add
• (Optional) Run: net localgroup Administrators NewUser /add to give admin rights.

Create a new local user (PowerShell)​

• Open PowerShell (Admin).
• Run: New‑LocalUser -Name "NewUser" -Password (ConvertTo‑SecureString "P@ssw0rd" -AsPlainText -Force) -FullName "User Name"
• Add to group: Add‑LocalGroupMember -Group "Administrators" -Member "NewUser". fileciteturn0file0turn0file3

Disable or enable built‑in Administrator​

• GUI: right‑click the Administrator account → Properties → check/uncheck Account is disabled.
• Command line: net user administrator /active:yes or net user administrator /active:no. This is the standard approach to enable or disable the hidden built‑in Administrator account. fileciteturn0file1turn0file2

---

Troubleshooting: why lusrmgr.msc fails and how to fix it​

• Edition mismatch: the most common cause is running Windows 11 Home. Verify your edition in Settings → System → About. If you’re on Home, use the Settings UI, net commands, or PowerShell instead. fileciteturn0file0turn0file10
• Snap‑in missing from MMC: add it manually using mmc → Add/Remove Snap‑in. This fixes cases where the underlying MMC registry entries were removed.
• UAC or permission blocking: run the console elevated. If the console opens but operations fail, ensure you’re using an account with administrative rights or a true elevated shell.
• Group Policy or corporate management: on domain‑joined or managed devices some local tools are restricted. Check with your IT policy or use domain management tools instead. If a device is managed, local changes could be overwritten by policy at next refresh.

When none of the supported approaches work and you must perform one‑off changes on Home, avoid unsupported third‑party “hacks” unless you fully understand the security implications.

---

Workarounds and automation (for power users and IT)​

For technicians and deployment scenarios there are supported and community methods to create local accounts at setup or automate account management after install:

• Autounattend.xml and unattended setup: the supported enterprise method to preseed local administrator accounts and skip OOBE Microsoft account requirements during imaging. Use Windows System Image Manager (Windows ADK) to produce the file and place it on the installation USB. This is repeatable and auditable for imaging fleets.
• Rufus installer customizations: Rufus offers an option when writing an ISO to remove the Microsoft Account requirement during OOBE or to predefine a local account. This is a community tool and depends on the image build — test before using at scale. Treat it as an image‑preparation convenience, not a universal solution. fileciteturn0file8turn0file13
• In‑OOBE command bypasses: experienced technicians have used Shift+F10 to open a Command Prompt during OOBE and run helper commands that switch installer flows to local account creation. These methods are build‑sensitive and may be blocked on newer builds; they should be treated as experimental. fileciteturn0file8turn0file18

---

Security and operational considerations (what to watch for)​

Local Users and Groups grants powerful control. A few important cautions:

• Do not delete built‑in groups (Administrators, Users, Guests): removing standard built‑in groups can break application and OS behaviors and cause system instability. The built‑in groups are referenced by many services and apps.
• BitLocker and Microsoft Account ties: if you remove or change a Microsoft Account that stored BitLocker recovery keys, retrieve or export the recovery key first — otherwise encrypted drives may become unrecoverable. For devices moved from MSA to local accounts, plan key escrow in advance. fileciteturn0file17turn0file13
• Use strong passwords and rotate elevated accounts: local admin accounts are attractive attack targets. If you create or preseed local admin credentials in images or answer files, ensure they are temporary or rotated and stored securely. Unattended files with plaintext passwords are a security risk unless handled properly.
• Audit and logging: changes to accounts and groups should be tracked where possible. On standalone devices, ensure local logs are examined; in managed environments use centralized auditing.

---

FAQs and quick answers​

• Why can’t I find Local Users and Groups on my PC? It is not included in Windows 11 Home by default. Confirm your edition and use Settings / net commands / PowerShell on Home, or upgrade to Pro for full MMC snap‑ins. fileciteturn0file0turn0file10
• Can I manage accounts without lusrmgr.msc? Yes — Settings → Accounts (basic tasks), net user and net localgroup commands, PowerShell New‑LocalUser/Add‑LocalGroupMember, and Netplwiz can cover almost all needs. fileciteturn0file0turn0file3
• How do I enable the built‑in Administrator? Use net user administrator /active:yes from an elevated command prompt or enable it from Local Users and Groups by clearing the “Account is disabled” checkbox. fileciteturn0file1turn0file2
• Is it safe to remove a user group? Avoid deleting built‑in groups (Administrator, Users, Guests). Creating custom groups is fine, but remove built‑in groups only if you fully understand the dependency implications.

---

Practical checklist for admins: safe steps to manage users in Windows 11​

• Confirm Windows edition before relying on lusrmgr.msc.
• Always run MMC or command shells elevated for user/group management.
• Back up BitLocker recovery keys and important data before changing primary accounts or removing MSAs.
• Use PowerShell cmdlets for repeatable scripts: New‑LocalUser, Add‑LocalGroupMember, Set‑LocalUser.
• For deployments, prefer autounattend.xml or enterprise imaging rather than in‑OOBE tricks.
• Avoid deleting built‑in groups; prefer adding finer custom groups where needed.
• If using community tools or GitHub workarounds to expose missing snap‑ins on Home, treat them as unsupported and test in a safe environment first. fileciteturn0file17turn0file8

---

Closing analysis: strengths and risks​

The Local Users and Groups MMC is a compact, powerful administrative interface that remains unmatched for granular local account control on standalone Windows systems. For Pro and Enterprise users it’s fast, visual, and safe. For Home users, Microsoft’s decision to omit the snap‑in nudges everyday tasks toward Settings and scriptable alternatives; that’s reasonable for mainstream consumers but a friction point for power users and technicians.
Strengths:

• Direct, granular control over users and groups.
• Visual tools for auditing membership and account properties.
• Seamless integration with other Computer Management tools. fileciteturn0file5turn0file3

Risks and tradeoffs:

• Absent on Home edition, requiring command‑line alternatives or unsupported workarounds.
• Deleting or misconfiguring built‑in groups and accounts can produce system instability.
• Workarounds (community utilities, modified installers) carry security, support, and compatibility risks — use them only with full understanding and testing. fileciteturn0file8turn0file17

When managing accounts, choose the tool appropriate to the task: the MMC for visual, one‑off edits on Pro; PowerShell and net commands for automation and Home edition tasks; and enterprise deployment methods (autounattend.xml, image‑based provisioning) for repeated, auditable installs. Treat any unofficial workaround as experimental, back up critical keys and data first, and avoid destructive changes to built‑in groups.
Local Users and Groups remains an essential skill for serious Windows administrators. Knowing how to open it — and how to achieve the same results when it’s unavailable — gives you control and flexibility while helping you avoid the pitfalls that come with unsupported editing and automation.

---

Source: Windows Report How to Open Local Users and Groups in Windows 11