What Actually Causes 0XC000015B?
You see STATUS_LOGON_TYPE_NOT_GRANTED (0XC000015B) when Windows explicitly blocks the type of logon you're trying to use. This happens most often with Remote Desktop (RDP) connections, but also with network shares, printer connections, or scheduled tasks. The system isn't saying your password is wrong — it's saying you're not allowed to log in that way.
Common triggers:
- You just changed a user password on an RDP machine
- A Group Policy update pushed new restrictions
- You're using a local account instead of a domain account
- Network Level Authentication (NLA) is mismatched between client and server
Let's walk through the fixes from easiest to most involved. You can stop after any section that works for you.
Fix 1: Check Network Level Authentication (30 seconds)
This is the fix you try first because it's nearly instant. Half the time this is the culprit.
- On the machine you're trying to connect to (the remote computer), right-click the Start button and select System.
- On the left side, click Remote Desktop.
- Make sure Enable Remote Desktop is turned on.
- Under that, look for a checkbox that says Require devices to use Network Level Authentication to connect.
Here's the trick: If this box is checked, uncheck it, click Apply, and try connecting again. You should see the credentials prompt instead of the error. If that works, you've got an NLA mismatch — the remote machine is demanding NLA, but your client isn't meeting the requirement. You can re-enable NLA later by making sure both machines have the same Windows update level and NLA enabled.
After unchecking, wait 10 seconds and test. If the error's gone, you're done. If not, move on to Fix 2.
Fix 2: Adjust Local Security Policy (5 minutes)
This is where we fix the actual policy that denies Remote Desktop logons. The error's full name — STATUS_LOGON_TYPE_NOT_GRANTED — means this policy is set to deny "Remote Interactive" or "Network" logons for your user account.
- Press Windows Key + R, type
secpol.msc, and hit Enter. This opens the Local Security Policy editor. - In the left pane, expand Local Policies, then click User Rights Assignment.
- Scroll down to find Deny log on through Remote Desktop Services. Double-click it.
- Look in the list for your username, your computer name, or any group like "Users" or "Everyone." If you see anything, select it and click Remove.
- Click Apply and OK.
- Now find Allow log on through Remote Desktop Services. Double-click it.
- Click Add User or Group, type your username, and click Check Names to verify it resolves. Click OK.
- Click Apply and OK.
Important: After making these changes, close the Remote Desktop client completely, not just disconnect. Wait about 30 seconds for group policy to refresh, then try connecting again. If you still see the error, run gpupdate /force in Command Prompt as admin, then retry.
This fix works for about 80% of cases. If you're still stuck, let's go deeper.
Fix 3: Remove Stored Credentials and Check Services (15+ minutes)
This is the advanced fix. It's for when the policy is correct but Windows still refuses the logon. Usually this happens after a password change or a domain migration.
Step 3a: Clear Stored Credentials
- Open Control Panel > User Accounts > Credential Manager.
- Click Windows Credentials.
- Look for any entries under Generic Credentials that reference the remote computer's name or IP address. They might look like
TERMSRV/192.168.1.100orMicrosoftAccount:user@domain.com. - Click the arrow to expand each one, then click Remove. Confirm when prompted.
- Close Credential Manager.
Step 3b: Verify Remote Desktop Services Are Running
- Press Windows Key + R, type
services.msc, and hit Enter. - Find Remote Desktop Services (also called TermService). Double-click it.
- Make sure the Startup type is Automatic and the Status shows Running.
- Find Remote Desktop Services UserMode Port Redirector (also called UmRdpService). Double-click it.
- Set Startup type to Automatic and click Start if it's not running.
- Close the Services window.
Step 3c: Check Network Service Account Permissions
This one trips up a lot of people. The NETWORK SERVICE account needs specific permissions on the remote machine.
- Open Local Security Policy again (
secpol.msc). - Go to Local Policies > User Rights Assignment.
- Find Impersonate a client after authentication. Double-click it.
- Click Add User or Group, type
NETWORK SERVICE, and click OK. - Click Apply and OK.
After all this, restart the remote computer. Not just log off — a full restart. Wait for it to come back up, then try your connection again.
What If None of This Works?
If you've run through all three fixes and still get 0XC000015B, you're likely dealing with a Group Policy from a domain controller overriding local settings. In that case:
- Contact your domain admin and ask them to check the Default Domain Policy for the "Deny log on through Remote Desktop Services" setting.
- Check if your user account is part of the Remote Desktop Users group on the target machine. You can do this by running
lusrmgr.mscon the remote computer, going to Groups, and verifying your account is listed.
The error is frustrating but it's Windows doing exactly what it's been told to do. You just have to find out who told it to deny you, and fix that instruction.