Fix ERROR_NO_SUCH_ALIAS (0X00000560) in Windows

Quick answer (for the impatient)

Open Command Prompt as admin and run net localgroup "GroupName" to verify the group exists. If you get the error, you typed the name wrong or the group was deleted. Use net localgroup to list all groups, then recreate any missing ones with net localgroup "GroupName" /add.

Why this happens

This error code 0X00000560 (decimal 1376) shows up when you try to add, remove, or modify a local group on Windows—usually via net localgroup, PowerShell, or the Local Users and Groups MMC snap-in (lusrmgr.msc)—and the system can't find it. I've seen this most often in two scenarios: someone fat-fingers the group name (like "Administrators" vs "Administrator"), or a group gets deleted by a script, a cleanup tool, or a well-meaning admin doing maintenance. On domain-joined machines, you might also hit this if you're trying to manage a group from a remote workstation and the connection drops or the domain controller isn't reachable. The error itself is part of the Windows security subsystem—it's the system's way of saying "I checked my local account database, and that group ID doesn't exist." Frustrating, sure, but it's a clear signal to verify the group exists before anything else.

Fix steps (numbered, start here)

Open Command Prompt as admin. Press Win+R, type cmd, then press Ctrl+Shift+Enter. Click Yes on the UAC prompt.
List all local groups. Run this command:
```
net localgroup
```
You'll get a list like *Administrators, *Users, *Backup Operators. Compare the name you were using with what's listed—typos are painfully common. For example, if you wrote net localgroup admin, it won't work. It's Administrators.
Check the specific group. Run:
```
net localgroup "Name of Group"
```
Replace Name of Group with the exact name from the list. If you get "The specified local group does not exist" again, the group is missing.
Recreate the group if missing. Only do this if you're sure the group should exist. For example, if Backup Operators is gone, replace it with:
```
net localgroup "Backup Operators" /add
```
Then add users back: net localgroup "Backup Operators" DOMAIN\UserName /add. Built-in groups like Administrators and Users can't be deleted normally, but some third-party tools might. If one of those is missing, you're looking at a deeper system corruption—skip to the alternative fixes below.
Try the command again. After recreating or verifying the group, rerun your original operation. It should work now.

Alternative fixes (if the main steps don't work)

Use PowerShell to create the group

Sometimes net localgroup fails due to environment issues (I've seen it on Windows Server 2012 R2 after a botched update). Try PowerShell instead:

New-LocalGroup -Name "GroupName" -Description "Description"

Then check it: Get-LocalGroup -Name "GroupName". If New-LocalGroup throws an error, you might have a permission problem—ensure you're running PowerShell as admin.

Check for corruption in the SAM database

Local groups are stored in the Security Account Manager (SAM) registry hive. If it's corrupted, you'll see errors like this. Run sfc /scannow to check system files. Then run DISM /Online /Cleanup-Image /RestoreHealth. Reboot and try the group commands again.

Use the MMC snap-in (lusrmgr.msc)

On Windows Pro, Enterprise, or Server editions, you can use the GUI: Press Win+R, type lusrmgr.msc, and hit Enter. If the snap-in loads but shows no groups, the SAM may be damaged—restore from backup or consider a repair install. If the snap-in won't open, try control userpasswords2—but that only handles user accounts, not groups directly.

Domain-joined machines: check connectivity

If you're managing groups remotely via PowerShell or net localgroup /domain, the error could mean the domain controller isn't responding. Run nltest /dsgetdc:YourDomain to verify. If it fails, fix your network or DNS first.

Prevention tip

Always double-check group names before running commands. I keep a text file with the exact names of groups I manage frequently. If you're automating group creation with scripts, add a check that lists groups first: if (Get-LocalGroup -Name "GroupName" -ErrorAction SilentlyContinue) { ... } else { New-LocalGroup ... }. Also, take regular system state backups—especially the SAM hive—so you can restore a missing group without recreating it from scratch.