We've recently been working on the new local account management PowerShell cmdlets and found an issue with the Get-LocalGroupMember cmdlet
If a user group has a member that cannot be resolved normally most APIs will return just the SID of the account, and certainly the Computer Management MMC shows the user as the SID and as an unknown account.
![]()
Unfortunately the Get-LocalGroupDetails PowerShell cmdlet fails completely with the following error
Get-LocalGroupDetails. An unspecified error occurred: error code = 1789
If you use an -ErrorAction SilentlyContinue parameter the cmdlet will return with no members which is obviously misleading as there may be other, valid accounts in the group.
If a user group has a member that cannot be resolved normally most APIs will return just the SID of the account, and certainly the Computer Management MMC shows the user as the SID and as an unknown account.
Unfortunately the Get-LocalGroupDetails PowerShell cmdlet fails completely with the following error
Get-LocalGroupDetails. An unspecified error occurred: error code = 1789
If you use an -ErrorAction SilentlyContinue parameter the cmdlet will return with no members which is obviously misleading as there may be other, valid accounts in the group.