ERROR_LICENSE_QUOTA_EXCEEDED (0x80040201) on RDS: Real Fix

Yeah, that error is a gut punch when you've got users waiting. But the fix is usually straightforward once you know what's actually happening: your Remote Desktop license server has handed out all its Client Access Licenses (CALs), or it can't issue new ones because something's misconfigured.

Step 1: Confirm the license server is even reachable

Before you blame the CAL count, rule out a connection problem. On the RD Session Host (the machine users connect to), open an admin PowerShell and run:

wmic /node:localhost path Win32_TSLicenseServer get Name

If that returns a license server name, you're good. If it's blank or says 'Not Found', your session host isn't talking to any license server. That'll also throw 0x80040201.

Step 2: Check how many CALs you've installed and how many are used

Open Remote Desktop Licensing Manager on the license server. Right-click your server, pick Properties, then the Required CALs tab. You'll see:

• Total available – the CALs you bought and installed
• Issued – how many are currently checked out by active or disconnected sessions
• Available – the number left

If Available is 0, you've hit the quota. Period. Your only move is to buy more CALs and install them, or revoke unused ones.

Step 3: Revoke stale CALs (temporary relief)

Windows doesn't auto-revoke CALs from disconnected sessions for days by default. To force clean them up:

1. In Licensing Manager, right-click your server and choose Revoke Licenses.
2. You'll get a warning—this is a one-way operation. Once revoked, those CALs are gone forever from that license server (they're burned). But it frees up space now.
3. Type the number you want to revoke. I usually start with 5-10% of total.

Why this works short-term: Revoking forces the server to reissue those CALs to new connections. The catch: you just permanently destroyed those licenses, so you'll run out faster next time unless you buy more.

Step 4: Verify the licensing mode matches

If your session host is set to Per User but your license server only has Per Device CALs (or vice versa), the server refuses to hand any out. That's a config mismatch, not a real quota issue, but it shows the same error.

On the RD Session Host, open Server Manager → Remote Desktop Services → Collections. Right-click your collection, choose Properties, then look at Licensing. It should match what you bought.

Why step 3 works (the real reason)

Here's the nuance: Windows RDS licensing works on a borrow-checkout model. When a user connects, the session host asks the license server for a temporary license. That license stays checked out even after the user logs off, until the license server's cleanup cycle runs (default: every 2-3 days). Revoking manually bypasses that cycle, freeing CALs immediately. But those revoked CALs are gone—you're essentially burning them to solve an immediate shortage.

Less common variations

Per User CALs hitting the 90-day limit

Per User CALs expire after 90 days if the user never connects again. The license server won't reissue them until that timer runs out. If you see 'Available: 0' but 'Issued' is far below 'Total Available', check the Status column in Licensing Manager—stale Per User CALs show as 'Expired'. You can't manually force them to recycle. Only time fixes that.

Grace period expired without a license server

Windows Server gives you 120 days grace period after installing the RD Session Host role. If you never configured a license server in that window, the service stops working and throws exactly this error. The fix: point your session host to a valid license server (or install one if you haven't). No CAL purchase needed during grace period, but once it's gone, you must buy CALs.

Prevention going forward

• Monitor license usage weekly. I use a scheduled task that runs Get-RDSessionCollectionLicenseUsage and emails me a CSV.
• Buy CALs at 80% utilization, not 100%. Lead times from Microsoft's resellers can be 2-3 days on electronic delivery.
• If you run Per User CALs, set a group policy to enforce a session timeout that disconnects idle users after 4 hours. That prevents one user holding a CAL overnight.

That's it. The error is annoying but rarely cryptic. Check the server, check the CALs, fix the mismatch, or buy more.