Fix 0xC0000154: Local Group Already Exists

The 30-Second Fix: Check Group Name & Try Again

What's actually happening here is you're trying to create a local group (like "Backup Operators" or "MyCustomGroup") and Windows already has one with that exact name. The error code 0xC0000154 means the group exists, period.

First: look at the group name you typed. Did you miss a letter? Add a space? Windows local group names are case-insensitive but not forgiving with spaces. "BackupOps" and "BackupOps " (trailing space) are considered different.

Try these quick things:

Rename your group to something slightly different: "BackupOps2" or "BackupOps_New"
Check if you accidentally used a built-in group name. Windows has groups like "Administrators", "Users", "Guests", "Backup Operators", "Remote Desktop Users". If you pick any of these, you'll get this error.
If you're in PowerShell or a script, look for a typo. I've seen people write New-LocalGroup -Name "Administrators" and wonder why it fails. That group exists by default.

If you're sure the name is unique and you still get the error, move to the next step.

The 5-Minute Fix: Find the Duplicate Group & Delete or Rename It

Sometimes a group exists but you don't see it in the GUI. Happens on domain-joined machines or after some software installs. Let's find it.

Open PowerShell as Administrator and run:

Get-LocalGroup | Where-Object { $_.Name -like "*Backup*" }

Replace "Backup" with part of your group name. This will show all local groups with that string. If you see your group listed, you know it exists.

If you find it and you don't need it, delete it:

Remove-LocalGroup -Name "YourGroupName"

Or rename it to something else (only works on Windows 10/11 Pro or Server):

Rename-LocalGroup -Name "OldName" -NewName "OldName_Archive"

The reason this works is that Windows doesn't allow duplicate group names at all, even if they're in different containers. Local group names are unique per machine.

If you can't see the group with Get-LocalGroup, try the old-school command:

net localgroup

This lists all local groups. If yours shows up, you know it's there.

The 15+ Minute Fix: Check for Hidden Groups, SID Conflicts, or Corrupted SAM

If you still get 0xC0000154 after checking names and deleting the visible group, we're dealing with something deeper. This usually happens with:

Groups created by third-party software that don't show in default tools
Corrupted Security Account Manager (SAM) database
SID conflicts from restoring a system backup

Start by checking the registry for local groups. Open regedit and go to:

HKEY_LOCAL_MACHINE\SAM\SAM\Domains\Account\Aliases\Names

You'll need to take ownership of the SAM key first. Backup your registry before touching this. Under Aliases\Names, each subkey is a local group name. Find yours and delete it (right-click > Delete). Then reboot.

If registry editing sounds risky, use the command-line tool wmic (still available in Windows 10/11):

wmic group where name="YourGroupName" delete

If that fails, run a system file checker to rule out corruption:

sfc /scannow

Then check the SAM with:

dism /online /cleanup-image /restorehealth

Last resort: create a new local account or group using a different name, then migrate permissions manually. I've had to do this twice in 10 years — once after a botched domain migration, once after a virus messed up the SAM.

Pro tip: If you're on a workgroup machine and you don't care about the group, just make a new one with a different name. It's faster than hunting down ghosts.