Fix it now
The password was accepted and the account is fine. Status 0xC000015B in a 4625 record means the user has not been granted the requested logon type at this machine, and for a Remote Desktop connection that logon type is governed by the Allow log on through Remote Desktop Services right. Grant it, or remove the deny that is beating it.
net localgroup "Remote Desktop Users"
gpresult /h C:\temp\gp.html
- Open
secpol.msc, then Local Policies, User Rights Assignment. Check Allow log on through Remote Desktop Services for the user or a group containing them. - Check Deny log on through Remote Desktop Services in the same list. A deny beats any allow, and security baselines routinely put Guests or a local-accounts category there.
- If either entry is greyed out it is coming from Group Policy. Open the report the second command wrote and find which policy object sets the right.
- Correct it at that policy object, run
gpupdate /forceon the host, and have the user retry. No reboot is needed.
On a domain controller the effective default for this right is Administrators only, so adding someone to Remote Desktop Users on a domain controller changes nothing. Member servers default to Administrators plus Remote Desktop Users.
If the user gets a session, you are done. If they are still refused, or there is no 4625 on the host at all, the next section explains what each of those means.
Why it happens
A Remote Desktop logon passes two gates, and this failure is at the second one. First the credentials are validated, which is what the credential-validation audit record covers when it happens against the local machine or a domain controller. Then Windows asks a separate question: is this account permitted to log on to this computer, in this way? Remote Desktop connections use the remote interactive logon type, recorded as logon type 10, and it is governed by its own user right rather than by any file or share permission.
The status field is what separates this from every other logon failure. Microsoft publishes 0xC000015B as ‘the user has not been granted the requested logon type (aka logon right) at this machine’. A wrong password, a disabled account, an expired password and a lockout all produce a 4625 with different status values. That is why resetting the password never helps here, and why the same person can often sign in at the console or reach a file share without any trouble.
The right itself is called Allow log on through Remote Desktop Services, its constant is SeRemoteInteractiveLogonRight, and it lives under Computer Configuration, Windows Settings, Security Settings, Local Policies, User Rights Assignment. Membership of the local Remote Desktop Users group is the normal way it gets granted, because on a member server and on a client that group is in the effective default list alongside Administrators. Two things break that assumption: a Group Policy object that replaces the list without including the group, and a domain controller, where the effective default is Administrators alone.
Neither the right nor the group membership is there
You have this one if The account is missing from Remote Desktop Users on the host and from the allow list, and it is a new user or a newly built host.
- Add a domain group the user belongs to, rather than the user, to the local Remote Desktop Users group on the Session Host.
- Confirm Remote Desktop Users is present in Allow log on through Remote Desktop Services on that host.
- Manage this from one Group Policy object across the collection rather than machine by machine.
- Have the user retry immediately; the right takes effect without a restart.
Microsoft’s own guidance is to control access by adding and removing people from the Remote Desktop Users group rather than by editing the user right directly.
A deny entry is winning
You have this one if The user is correctly in the allow list and still refused, and a group they belong to appears in Deny log on through Remote Desktop Services.
- Read the deny list carefully. Entries such as Guests, or a category covering local accounts, arrive with common security baselines.
- Work out whether the deny is deliberate. In a tiered administration model it usually is, and the answer is a different account rather than a policy change.
- If it is collateral damage, narrow the deny entry rather than removing it, then run
gpupdate /forceand retest.
Group Policy is overwriting the local setting
You have this one if The entries are greyed out in the local editor, or a correct local change reverts at the next policy refresh.
- Generate the report with
gpresult /h C:\temp\gp.htmland find the user rights section. - Note which policy object is winning and make the change there rather than locally.
- Check for a Restricted Groups or Group Policy Preferences setting rewriting the local Remote Desktop Users membership as well.
- Reapply policy and confirm the setting now holds through a refresh.
The target is a domain controller
You have this one if Users reach member servers and are refused by a domain controller, even after being added to Remote Desktop Users there.
- Understand the published default first: on a domain controller the effective default for this right is Administrators, and Remote Desktop Users is not in it.
- Decide whether non-administrators genuinely need an interactive session on a domain controller. Usually they do not.
- If it is genuinely required, grant the right to a specific group in the Default Domain Controllers Policy and record why.
Giving ordinary users a session on a domain controller is a security decision, not a ticket. Treat it as one.
Something above the host is refusing them
You have this one if There is no 4625 on the Session Host at all, and the user never reaches it.
- Check the user group configured on the session collection in a full deployment.
- Check the RD Gateway connection and resource authorisation policies if sessions arrive through a gateway.
- Read the Security log on the gateway or the broker rather than on the Session Host.
Full reference
Reading a 4625 record properly
| Field | What to look at |
|---|---|
| Failure Information, Status and Sub Status | 0xC000015B is the logon-type refusal. Other values mean password, account state or lockout |
| Logon Type | 10 is RemoteInteractive, a Remote Desktop session. Type 3 is a network logon and is a different problem |
| Account For Which Logon Failed | The account the right is missing for, which is not always the account the user thinks they used |
| Network Information | The workstation and source address, which is how you tell an internal client from one arriving via a gateway |
One record with logon type 10 and status 0xC000015B is a complete diagnosis on its own. It says authentication succeeded and authorisation for this logon type did not. Nothing else in the record changes that conclusion.
Effective defaults for the right
| Machine | Effective default for Allow log on through Remote Desktop Services |
|---|---|
| Domain controller | Administrators |
| Member server | Administrators, Remote Desktop Users |
| Client computer | Administrators, Remote Desktop Users |
Comparing two hosts that behave differently
secedit /export /cfg C:\temp\rights.inf
net localgroup "Remote Desktop Users"
gpresult /h C:\temp\gp.html /f
The exported security configuration lists the accounts and groups holding each right by SID, including SeRemoteInteractiveLogonRight and its deny counterpart. It is the definitive answer when the graphical editor is greyed out, and it is the fastest way to find the one host in a collection whose local policy has drifted. gpresult /h writes an HTML report; /f overwrites an existing file so you can re-run it without renaming anything.
Granting the right without making the deployment unauditable
- Grant to a group, never to an individual account. Per-user entries scattered across hosts are how collections become impossible to audit.
- Prefer adding the group to Remote Desktop Users and leaving Remote Desktop Users in the allow list, which is the pattern Microsoft recommends and the one every host already starts with.
- Apply it from one Group Policy object scoped to the collection’s organisational unit, so a rebuilt host inherits it rather than needing a manual step.
- Keep the deny list deliberate and short. Every entry in it is a refusal you will have to explain later, usually at the least convenient moment.
When this is not the problem
Several failures look similar from the user’s side and are diagnosed completely differently. A licensing shortage refuses the connection with a licensing message and produces its own events on the host, not an authorisation status in the Security log. A collection or gateway refusal happens before the Session Host is involved, so there is no 4625 there at all. A certificate or listener fault ends the connection during the handshake, before any account is evaluated. If you have a 4625 with logon type 10, you are in the right article; if you have no 4625, you are looking at the wrong machine.
This costs nothing to fix. User rights assignment is part of Windows Server, no licence changes who may log on, and no purchase alters the outcome.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
0xC000015B |
The user has not been granted the requested logon type, that is the logon right, at this machine | Microsoft Learn |
Event ID 4625 |
An account failed to log on. The status, sub status and logon type fields inside it are what identify the reason | Microsoft Learn |
Event ID 131 |
Not published by Microsoft. It appears in the RdpCoreTS operational log alongside inbound connections and is useful only for tying an attempt to a source address | not published by the vendor |
Event ID 4776 |
The domain controller attempted to validate the credentials for an account, which is how you confirm authentication itself succeeded | Microsoft Learn |
Confirm the fix worked
- The affected user connects and a session is created.
- A 4624 record with logon type 10 now appears for that account in place of the 4625.
- The exported security configuration on two hosts in the collection shows the same holders for SeRemoteInteractiveLogonRight.
- The change was made in Group Policy, so it survives the next refresh and a host rebuild.
- The deny list still contains only entries you can account for.
Questions people ask about this
Will resetting the password help?
No. This status means the password was accepted. The refusal is about the logon type, so a reset changes nothing and costs the user their morning.
Is this a CAL problem?
No, and it costs nothing to fix. A licensing shortage produces a licensing refusal with its own events, not an authorisation status in the Security log. This is user rights assignment, which is part of Windows Server.
Why can the user connect to one server and not another?
Because the right is per machine. Two hosts in one collection can have different local group membership or sit in different policy scopes. Export the rights from both and compare.
They are in Remote Desktop Users on the domain controller and still cannot connect. Why?
Because the effective default for the right on a domain controller is Administrators alone. Remote Desktop Users is not in that list, so membership of it achieves nothing there.
Should I add users directly to the allow policy?
Prefer adding a group to Remote Desktop Users and leaving that group in the allow list. Microsoft’s own guidance is to manage access through the group rather than by editing the right.
