Corrupted Local Windows Server Group

WojD4909 96 Reputation points

I have a problem on my Windows 2016 Server.
When I am opening "Computer Management->Local Users and Groups->Groups" I am getting an error
"The following error occurred while attempting to read group properties: The The specified local group does not exist". When I am clicking OK, there are 2 groups missing which are visible when running command "net localgroup" .
When I am trying to remove or add by command line those groups

C:\Users\user>net localgroup "Users-Editor" /delete
System error 1376 has occurred.

The specified local group does not exist.

C:\Users\user>net localgroup "Users-Editor" /add
System error 1379 has occurred.

The specified local group already exists.

Anyone have an idea how to fix the issue ?

Microsoft Graph
Microsoft Graph
A Microsoft programmability model that exposes REST APIs and client libraries to access data on Microsoft 365 services.
11,094 questions
Windows Server 2016
Windows Server 2016
A Microsoft server operating system that supports enterprise-level management updated to data storage.
2,416 questions
0 comments No comments
{count} votes

3 answers

Sort by: Most helpful
  1. Andy YOU 3,071 Reputation points

    1.what are 2 groups missing ?
    build-in group(remote desktop users) or your created new customized group

    2.what's characteristic for the missing group ?
    The group name must meet the following requirements:
    Must not exceed 256 characters
    Must not end in a period
    Must not include commas
    Must not include any of the following printable characters: ", /, \, [, ], :, |, <, >, +, =, ;, ?, *, @
    Must not include characters in the ASCII range 1-31, which are non-printable

    3.what's time did you first disover this issue?did your w2016 work fine before ? your issue server 2016 joined to domain ?

    5.did you try to create a new local admin account on this issue w2016 and logon by using this new local admin account then check if the same issue happen on this new local admin profile?

    6.if the problem persist ,can we run below command in command prompt(open as admin)then check if it can find and solve system file issue?
    sfc scannow
    dism /online /cleanup-image /scanhealth
    dism /online /cleanup-image /restorehealth

    0 comments No comments

  2. WojD4909 96 Reputation points

    Thank you JiaYou for answer. The server is in production now. We will try to move service to another one, then i will try your solution.

  3. Lou 1 Reputation point

    I have been struggling with the same problem on a Windows 7 system that I have finally been allowed to upgrade to Windows 10. The upgrade consistently fails after the 30% reboot that takes place when applying updates to the base W10 system. The logs indicate that the security template could not be successfully imported into the W10 system.

    Back on W7, net localgroup administrators was returning a system error 1387. lsurmgr.msc shows no members in the administrators group. Attempting to add a user to the administrators group - either via net localgroup or lusrmgr.msc -tell me that the user is already a member of the group. Attempting to remove a user from the administrators group with either tool always tells me that the user I am attempting to delete is not a member of the group. Both net user <userid> and the users option of lsrmgr.msc correctly show that the expected userids are indeed members of the administrators group. There are no similar issues with other groups; all of these commands return the expected results for groups other than administrators.

    Adding a new administrator userid and logging in with this userid changed the error that is returned by net localgroup administrators from 1387 to 87. lusrmgr.msc still shows the administrators group as being empty, but shows that the expected userids are members of the administrators group.

    scm /scanimage does not report any errors and the only errors reported by dism ... /scanhealth pertain to oem device drivers. dism /online /cleanup-image /restorehealth returns a system error 87 and then tells me that the restorehealth option is not recognized in this context.

    I'm still dead in the water. I've made a lot of noise about the need to upgrade the system I'm having this problem with to W10 for security reasons, and am now being asked why this task remains uncompleted. A fresh install of W10 is a desperation option at best. Others have reported this problem since 2017. The expertise of the folks at Microsoft is urgently needed to get this process moving forward.

    0 comments No comments