Skip to content

Commit a7e7544

Browse files
author
Simonx Xu
authored
Merge pull request #7948 from MicrosoftDocs/repo_sync_working_branch
Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/SupportArticles-docs (branch main)
2 parents 64feb8a + 51aa374 commit a7e7544

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

support/windows-server/windows-security/sids-not-resolve-into-friendly-names.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ searchScope:
1414
---
1515
# Some SIDs don't resolve into friendly names
1616

17-
This article provides some information about the issue where some security identifiers (SIDS) don't resolve into friendly names.
17+
This article provides some information about the issue where some security identifiers (SIDs) don't resolve into friendly names.
1818

1919
_Original KB number:_   4502539
2020

@@ -43,7 +43,7 @@ Windows 10, version 1809 uses more than 300 Capability SIDs.
4343
## More information
4444

4545
> [!Important]
46-
> Don't delete Capability SIDS from either the registry or file system permissions. Removing a Capability SID from file system permissions or registry permissions might cause a feature or application to function incorrectly. After you remove a Capability SID, you cannot use the UI to add it back.
46+
> Don't delete Capability SIDs from either the registry or file system permissions. Removing a Capability SID from file system permissions or registry permissions might cause a feature or application to function incorrectly. After you remove a Capability SID, you cannot use the UI to add it back.
4747
4848
When you're troubleshooting an unresolved SID, make sure that it isn't a Capability SID. To get a list of all of the Capability SIDs, follow these steps:
4949

0 commit comments

Comments
 (0)