How to fix Error 1379 on Windows 11

by

Troubleshooting Guide: Error 1379 – “The Specified Local Group Already Exists”

Why This Error Happens

Error 1379 occurs when a script, Group Policy, or administrative tool attempts to create a local group that already exists in the Security Accounts Manager (SAM) database. This is commonly triggered by duplicate entries in automated provisioning scripts, re-application of Group Policy Preferences (GPP), or residual group data left behind from an incomplete uninstall or system image deployment. In some cases, a corrupted or unsynced local SAM database can also cause Windows to misreport a group as duplicate even after apparent deletion.

Step-by-Step Resolution Guide

Step 1: Verify the Existing Local Group

  • Open Computer Management by right-clicking the Start menu and selecting Computer Management.
  • Navigate to Local Users and Groups > Groups.
  • Confirm whether the group name referenced in the error (e.g., via Event Viewer details) is already present in the list.

Step 2: Check the Source Script or GPO Configuration

  • If using PowerShell, review the script for a New-LocalGroup command and wrap it in a conditional check:
  if (-not (Get-LocalGroup -Name "GroupName" -ErrorAction SilentlyContinue)) {
      New-LocalGroup -Name "GroupName"
  }
  • If the group is being created via Group Policy Preferences, open Group Policy Management Console (GPMC), locate the relevant GPO under Computer Configuration > Preferences > Control Panel Settings > Local Users and Groups, and change the Action setting from “Create” to “Update.”

Step 3: Remove Duplicate or Orphaned Group Entries

  • If the group exists but is not needed, delete it manually via Computer Management or PowerShell:
  Remove-LocalGroup -Name "GroupName"
  • Re-run the original script or reapply the Group Policy to confirm the group is created cleanly without triggering Error 1379.

Step 4: Refresh Group Policy and SAM Sync

  • Run gpupdate /force in an elevated Command Prompt to refresh policy application.
  • Restart the Netlogon service (or reboot the machine) to ensure the SAM database reflects the most current group state.

Alternative or Verification Steps

  • Confirm the fix by running Get-LocalGroup in PowerShell and checking the Event Viewer (Windows Logs > Application) for any recurrence of Event ID 1379.
  • If the error persists despite the group not appearing in the GUI, use net localgroup from an elevated Command Prompt to cross-check for hidden or SID-orphaned entries, and consider running sfc /scannow to rule out SAM database corruption.