About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
An Application log event from source SceCli, ID 1202, with the code 0x534 means that a security setting in one of the Group Policy objects (GPOs) applied to the computer names an account that Windows cannot resolve to a security identifier (SID). Microsoft documents the causes as a mistyped name, an account deleted after it was added to the setting, or an account that sits across a trust that has since broken.
The fix is to find the unresolved name, find the GPO and setting that holds it, and then remove or replace that entry. A short debug log on the affected computer names the account, so nothing needs guessing.
What the error means
The Security Configuration client-side extension (the part of Group Policy that applies security templates) reads a list of accounts from a GPO, for example the groups allowed to log on locally, and translates each name to a SID. When a name cannot be translated, the extension logs a warning. The event description reads "Security policies were propagated with warning. 0x534 : No mapping between account names and security IDs was done." Microsoft's page headings show the same code as "0x534: No mapping between account names and security IDs was done."
Microsoft places the error in the User Rights section or the Restricted Groups section of the security policy setting, and says it can also occur when an account lives across a trust that later breaks. Do not assume the event is harmless. Microsoft's page says that for the WdiServiceHost case described below the event "doesn't prevent Windows computers from applying security policy", and in the same passage that there is "no way to distinguish a false positive event caused by this issue from a legitimate misconfiguration that will prevent security policy from applying". Treat every 0x534 event as a real fault until winlogon.log shows otherwise.
The first step Microsoft gives for any SCECLI 1202 event is to read the Win32 error code in the event's Description field, because the code decides the type of failure. The steps here cover 0x534. Microsoft's page lists 0x6fc ("The trust relationship between the primary domain and the trusted domain failed") beside 0x534 in its opening and summary. Other codes on the same page are different faults: 0x2 (the system cannot find the file specified, which the page calls similar to 0x534 and 0x6fc and caused by an irresolvable account name, tied to Restricted Groups), 0x5 (access denied, tied to service permissions) and 0x4b8 (a generic extended error).
Likely causes
| Cause | What you see | How to confirm |
|---|---|---|
| Account name mistyped in the setting | winlogon.log reports "Cannot find" with a name that is spelt differently from any real account | Compare the name in the log with the directory |
| Account deleted after it was added | The name is spelt correctly but no such account exists | Look the name up in Active Directory Users and Computers |
| Account sits across a trust and the trust is broken | The account exists in the other domain, yet the name does not resolve from this computer | Test the trust and the other domain's availability |
| Wrong policy applying to this computer | The entry is valid in one environment, but this computer receives a GPO written for another | Trace the GPO from the cached template and check its scope |
| Windows Server 2008 R2 domain controller after an edit in the Default Domain Controllers Policy | winlogon.log shows "Cannot find WdiServiceHost" | The page's symptom section: the SeSystemProfilePrivilege entry reads *S-1-5-32-544,WdiServiceHost |
The last row is a documented false positive with its own scope. Microsoft says a code defect in the Group Policy Management Console on Windows 7 or Windows Server 2008 R2 drops the NT Service\ prefix when any security setting in the Default Domain Controllers Policy is edited. The page adds that the event does not stop the policy applying, and that the event alone cannot distinguish this case from a real misconfiguration. Check winlogon.log to tell them apart.
Prove the cause before changing anything
Start with reads.
- In Event Viewer, open the Application log and find the SceCli 1202 event. Read the code in the Description field. If it is not 0x534, use the matching section of Microsoft's page instead.
- Note the time of the event and which computers log it. A single computer points at a policy that reaches only that computer. Every server in an organisational unit (OU) points at the GPO linked to the OU.
The next step needs a small change, because the log that names the account does not exist until it is switched on.
Risk: the following registry edit changes the behaviour of the Security Configuration client-side extension. Microsoft documents adding the value but does not describe removing it. To back out, delete the ExtensionDebugLevel value you added. Export the key first if you want a copy of its earlier state.
In Registry Editor, go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\GPExtensions\{827D319E-6EAC-11D2-A4EA-00C04F79F83A} and add a DWORD value named ExtensionDebugLevel with the data 2.
Risk: gpupdate /target:computer /force reapplies all computer policy settings, not just the ones that changed (Microsoft's gpupdate page: "Reapplies all policy settings"). Run it on one affected server out of hours. There is no undo for a reapplication. As advice, expect it to write the policy the computer would receive at its next refresh.
gpupdate /target:computer /force
This creates Winlogon.log in %SYSTEMROOT%\Security\Logs. The next commands only read.
find /i "cannot find" %SYSTEMROOT%\security\logs\winlogon.log
Microsoft shows the output as a line such as "Cannot find MichaelPeltier", where the user does not exist in the domain or is spelt differently (MichellePeltier in its example). A good result is no matching lines. A bad result names one or more accounts.
Now find which setting holds the name. Replace the quoted text with the name from the log.
find /i "MichaelPeltier" %SYSTEMROOT%\security\templates\policies\gpt*.*
The page's example output shows a file such as GPT00002.INF and a line such as SeInteractiveLogonRight = TsInternetUser,*S-1-5-32-549,...,MichaelPeltier,.... The file is the cached security template from the problem GPO, and the constant on the line names the setting. Here SeInteractiveLogonRight is displayed as "Logon locally".
Search that template for GPOPath=. The page's example shows GPOPath={6AC1786C-016F-11D2-945F-00C04FB984F9}\MACHINE, where the GUID in braces is the GPO. Then, on a domain controller or a server with the Remote Server Administration Tools (RSAT) installed, turn the GUID into a name:
Get-GPO -Guid 6AC1786C-016F-11D2-945F-00C04FB984F9
Microsoft's example output shows a DisplayName of "Default Domain Controllers Policy". You now have the account, the setting and the GPO.
Example (illustrative): three of the 24 servers in the Servers\Member OU of CONTOSO (3 of 24, or 12.5 percent) log event 1202 with 0x534 after a clean-up of old service accounts. On fs01, winlogon.log reports "Cannot find svc-oldbackup". The search of the cached templates finds the name in GPT00003.INF on a line that begins SeServiceLogonRight, and the GPOPath= line gives a GUID that Get-GPO resolves to "Member Servers Baseline". The other 21 servers do not log the event because a security filter keeps the GPO off them. The account was deleted in the clean-up, so the entry is removed from the GPO. No other change is needed.
Fix
Pick the row that matches what the log showed.
Mistyped name. Correct the spelling in the GPO setting. In Microsoft's words, you "remove or replace the problem entry".
Disruptive step: editing a GPO setting changes every computer and user in its scope on their next refresh. Before the edit, copy the complete current list of accounts from the setting so it can be re-entered. To back out, put the original list back.
Deleted account. Remove the entry from the setting. If the account should still exist, restore it before touching the GPO.
Disruptive step: removing an entry from a user-rights or Restricted Groups setting can lock out people or services that depended on it. Copy the full current list first. To back out, put the original list back.
Broken trust. Repair the trust or the reachability of the other domain first. Removing the entry only hides the fact that the account no longer resolves. Microsoft's page gives no repair steps for the trust.
Risk: trust repair changes how every account across that trust is authenticated. Record the current trust settings before you change them, and back out by restoring those settings.
Wrong policy. Correct the link or the scope so the computer no longer receives the GPO.
Disruptive step: changing a GPO link or scope changes which computers receive every setting in that GPO, not only the failing entry. Note the current link and security filtering first. To back out, restore them.
Windows Server 2008 R2 domain controller (WdiServiceHost). Microsoft's workaround edits the policy file by hand. In %SystemRoot%\Sysvol\domain\Policies\{6AC1786C-016F-11D2-945F-00C04fB984F9}\MACHINE\Microsoft\Windows NT\SecEdit\GPTTMPL.INF, change SeSystemProfilePrivilege = *S-1-5-32-544,WdiServiceHost to SeSystemProfilePrivilege = *S-1-5-32-544,nt service\WdiServiceHost. Microsoft's note says NT Service\ goes after the comma and must not be prefixed with an asterisk.
Disruptive step: this edits a file in SYSVOL, which replicates to every domain controller. Copy the file before changing it and keep the copy; restoring it is the way back. Microsoft says the edit must be repeated every time any security setting in the Default Domain Controllers Policy is administered with GPMC on the affected versions.
Confirm the fix
After the GPO or template change has reached the server, run gpupdate /target:computer /force again. Check the Application log for a new SceCli 1202 event with 0x534 and read winlogon.log again. For the WdiServiceHost case, Microsoft's step is the same: view the Application log for the event and, if it appears, check winlogon.log to see whether WdiServiceHost caused it.
A fix has worked when no new event appears after the refresh and the find /i "cannot find" search returns nothing from the new run. If the event returns with a different name, the setting held more than one bad entry, which can happen after a mass clean-up of accounts.
What to watch afterwards
- Search winlogon.log again after the next account clean-up, and remove entries from the GPO before deleting the account rather than after.
- Keep the Win32 code in view. A 0x2 or 0x5 event on the same server is a different fault with its own steps on Microsoft's page.
- Switch the debug value off when the diagnosis is finished, by deleting the
ExtensionDebugLevelvalue you added.
Read next
Related articles you may want next.
- TroubleshootingGroup Policy Not Applying: gpresult, Events and SYSVOLA Group Policy setting missing on a hosted server: read gpresult as the affected user, check loopback, filter one run's events, then check SYSVOL state.Read article
- TroubleshootingNetlogon event 5719 or Group Policy event 1129 at start-up: network not ready, or a broken trust?"This computer was not able to set up a secure session with a domain controller" at boot, or Group Policy failing at start-up. Tell a harmless start-up race from a broken trust relationship, prove which one you have, and fix the right thing.Read article
- Backup & RecoveryRestoring files with their permissions: SIDs, cross-domain restores and orphaned access entriesUnderstand SIDs, restored accounts, NTFS permissions, SID history, ownership and auditing when restoring files across Windows environments.Read article
Risks and limits
These commands have not been run or lab-tested. Microsoft's SCECLI page applies to supported versions of Windows Server and Windows client, and its examples show older folder paths such as D:\WINNT; paths on your build can differ. Microsoft's page describes the WdiServiceHost behaviour for Windows Server 2008 R2 domain controllers and for management computers running Windows 7 or Windows Server 2008 R2. It does not say whether later versions are affected.
Microsoft's page does not state the background refresh interval for security policy, so test with one server before assuming a result is final. Confirm which accounts and groups still need a right before you save a change to that setting.
Sources
- Troubleshoot SCECLI 1202 events — Microsoft Learn, page dated 2026-02-12, accessed 18 November 2026
- Event 1202 with status 0x534 logged — Microsoft Learn, page dated 2026-02-12, accessed 18 November 2026
- gpupdate — Microsoft Learn, page dated 2023-02-03, accessed 18 November 2026
- Get-GPO — Microsoft Learn, date not shown, accessed 18 November 2026
This article was originally published on .