Fix it now
TermDD Event 50 is “The RDP protocol component X.224 detected an error in the protocol stream and has disconnected the client”, and Microsoft’s documented cause is a corrupted certificate on the terminal server. Event 56 is logged for every unsuccessful RDP attempt where the server’s security layer and the client cannot agree. Neither is a licensing fault.
reg export "HKLM\SYSTEM\CurrentControlSet\Services\TermService\Parameters" C:\Temp\termservice-params.reg
- With the export saved, delete the values Certificate, X509 Certificate and X509 Certificate ID under
HKLM\SYSTEM\CurrentControlSet\Services\TermService\Parameters. - Restart the server. Windows regenerates the certificate values on start-up.
- If the server is also an RD Licensing server, reactivate it afterwards using the Telephone connection method, which is the route Microsoft documents for this repair.
- For Event 56, check the RDP listener’s security layer: Remote Desktop Session Host Configuration, Connections, right-click the RDP listener, Properties, General, Security Layer.
- If clients cannot support TLS, set Security Layer to RDP Security Layer. No restart of the server or the service is needed.
Setting RDP Security Layer means the server is not authenticated to the client. Treat it as a diagnostic step or a last resort, not a default.
If sessions hold you can stop here. If not, the next section covers the network faults that produce the same events for different reasons.
Why it happens
TermDD is the Remote Desktop device driver, and these events are it giving up on a connection rather than passing on data it cannot trust. Because the events look like network noise, they get treated as network noise, and the two causes Microsoft actually publishes get skipped.
Event 50 is the one with real published text: “The RDP protocol component X.224 detected an error in the protocol stream and has disconnected the client.” X.224 is the connection-establishment layer, which is why the disconnect happens at or near the start of a session rather than in the middle of one. Microsoft documents this event alongside the client-side message “Because of a security error, the client could not connect to the Terminal server”, and gives the cause plainly: a certificate on the terminal server is corrupted. The remedy is to back up and remove the X509 certificate values under TermService\Parameters, restart, and reactivate.
Event 56 is documented more thinly, and it is worth being straight about that. Microsoft records that you may see Event ID 56 with source TermDD in the system event logs on the RD server for every unsuccessful RDP attempt, in its article on the client-side error “The Local Security Authority cannot be contacted”. The causes it gives there are network congestion preventing a secure connection, and the RD server being configured for TLS when the connecting client does not support it. The remedy is to change the listener’s security layer to RDP Security Layer. Microsoft does not publish a message text for this event, so treat any quotation you find of one with care.
Two cautions before you act on either number. Event 56 is reused across sources – TerminalServices-Licensing and Application Popup both have one, meaning quite different things – so read the source column. And Event ID 226 is not published by Microsoft for TermDD or any Remote Desktop source at all; read its own description on your server rather than trusting a meaning found elsewhere, including here.
The terminal server’s certificate is corrupted
You have this one if Event 50 from TermDD, and clients getting “Because of a security error, the client could not connect”.
- Back up the key:
reg export "HKLM\SYSTEM\CurrentControlSet\Services\TermService\Parameters" C:\Temp\termservice-params.reg. - Delete the Certificate, X509 Certificate and X509 Certificate ID values under that key.
- Restart the server so the values are regenerated.
- If the machine is also an RD Licensing server, reactivate it using the Telephone method afterwards.
On an RD Session Host the equivalent values live under HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM, which Microsoft names in its RD Licensing troubleshooting for the same class of fault.
Server and client cannot agree on a security layer
You have this one if Event 56 from TermDD on every failed attempt, and clients reporting an authentication error or that the Local Security Authority cannot be contacted.
- Open Remote Desktop Session Host Configuration and look under Connections.
- Right-click the RDP listener and open Properties, then the General tab.
- Read the current Security Layer. Negotiate uses TLS where the client supports it; SSL requires TLS and a valid certificate; RDP Security Layer uses RDP encryption and does not authenticate the server.
- Where old clients cannot do TLS, set RDP Security Layer to restore connectivity, and plan to update the clients rather than leaving it there.
This change does not need a restart of the server or the Remote Desktop Services service.
The network path is corrupting the stream
You have this one if Disconnects during large screen redraws or file copies, clustered on one subnet, one VPN or one site.
- Test for fragmentation from an affected client:
ping -f -l 1472 rdshost.contoso.local, reducing the payload until it succeeds. A figure well below 1472 means something on the path is shrinking the usable packet size. - Force RDP onto TCP as a test using Select RDP transport protocols under Computer Configuration, Administrative Templates, Windows Components, Remote Desktop Services, Remote Desktop Session Host, Connections, then
gpupdate /force. - If sessions cross a firewall or SSL VPN that inspects traffic, exclude RDP from inspection for a test window.
- Check for a duplex mismatch on the switch port and update the network adapter driver and firmware on the host.
NIC offload is mangling the traffic
You have this one if The fault follows one host rather than one client, and appeared after a driver or firmware update.
- Disable the usual offloads on the host for a test:
Disable-NetAdapterLso -Name Ethernet,Disable-NetAdapterRsc -Name Ethernet,Disable-NetAdapterChecksumOffload -Name Ethernet. - Retest, then re-enable them one at a time to identify which one is responsible.
- Raise the specific offload with the adapter vendor rather than leaving all of them off permanently.
Each of these cmdlets restarts the adapter, so run them in a maintenance window and not over the RDP session you are trying to fix.
A licensing fault is producing the same client message
You have this one if Event 50 together with TermService Events 1004, 1010 or 1088, or TermServLicensing Event 28.
- Read the neighbouring events rather than only the TermDD one; Microsoft documents them together for a reason.
- Fix the licensing fault and the certificate repair above, in that order, then retest.
Full reference
The neighbouring events Microsoft names
| Event | Source | What it says |
|---|---|---|
| 1004 | TermService | The terminal server cannot issue a client licence |
| 1010 | TermService | Could not locate a licence server; confirm licence servers are registered in WINS or DNS, accepting requests, and running the licensing service |
| 1088 | TermService | The licensing grace period has expired and the service has not registered with a licence server |
| 28 | TermServLicensing | Terminal Services Licensing can only run on a domain controller or a server in a workgroup |
What is actually published
| Event | Source | Published position |
|---|---|---|
| 50 | TermDD | “The RDP protocol component X.224 detected an error in the protocol stream and has disconnected the client.” Documented cause: a corrupted certificate on the terminal server |
| 56 | TermDD | Logged on the RD server for every unsuccessful RDP attempt, in the context of a security-layer mismatch or network congestion preventing a secure connection. No message text is published |
| 226 | – | Not published by Microsoft for TermDD or any Remote Desktop source |
Event numbers that collide
| Number | Other source | Meaning there |
|---|---|---|
| 56 | TerminalServices-Licensing | Key-pack decryption failed; use the Telephone method to install RDS CALs |
| 56 | Application Popup | Driver SCSI returned an invalid ID for a child device – unrelated and safely ignored |
| 21 | TerminalServices-LocalSessionManager | Session logon succeeded |
This is why the source column in Event Viewer is not decoration. A two-digit event number on a Remote Desktop server tells you almost nothing on its own.
The three security layers
| Setting | What it does |
|---|---|
| Negotiate | Uses TLS to authenticate the server if the client supports TLS. If not, the server is not authenticated |
| RDP Security Layer | Uses RDP encryption. The server is not authenticated |
| SSL (TLS) | Requires TLS to authenticate the server. Without TLS support the connection cannot be established. Available only with a valid certificate |
Dropping to RDP Security Layer restores connectivity for old clients and gives up server authentication to do it. It is a legitimate diagnostic step and an acceptable short-term measure, but it is not somewhere to leave a production deployment – update the clients instead.
Where to look on each machine
- System log on the RD Session Host – TermDD and TermService events, including 50, 1004, 1010 and 1088.
- Applications and Services Logs, Microsoft, Windows, TerminalServices-LocalSessionManager – session logon, logoff, disconnect and reconnect.
- Applications and Services Logs, Microsoft, Windows, TerminalServices-RemoteConnectionManager – connection manager events including 1128, 1130 and 1131.
- Applications and Services Logs, Microsoft, Windows, TerminalServices-Licensing on the licence server – the licensing side of anything that looks like a licence problem.
- Applications and Services Logs, Microsoft, Windows, RemoteApp and Desktop Connections – for published application deployments.
Working out whether it is really the network
- Establish the pattern: one client, one subnet, one site, or everyone. Everyone points at the host; one subnet points at the path.
- Check whether the disconnects correlate with throughput – large screen redraws, file copies, printing – which points at fragmentation or offload.
- Test the path MTU with
ping -f -l 1472and reduce until it passes. - Force TCP transport as a test to remove UDP from the picture.
- Only after all of that, start disabling offloads, one at a time, with a maintenance window.
Do this in that order and the certificate and security-layer causes get ruled in or out in ten minutes, before anyone touches a switch port. Do it the other way round, as the common advice for these events does, and you can spend a week on MTU while a corrupted certificate sits there unread.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
Event ID 56 |
Microsoft records Event ID 56 with source TermDD on the RD server for every unsuccessful RDP attempt, in the context of network congestion preventing a secure connection or the server requiring TLS where the client cannot support it. No message text is published for it. Event 56 from other sources is unrelated: TerminalServices-Licensing 56 is a key-pack decryption failure, Application Popup 56 is a SCSI child device message | Microsoft Learn |
Event ID 50 |
Source TermDD: “The RDP protocol component X.224 detected an error in the protocol stream and has disconnected the client.” Microsoft’s documented cause is a corrupted certificate on the terminal server | Microsoft Learn |
Event ID 226 |
Seen on some hosts alongside RDP disconnects. No Microsoft page publishes an Event ID 226 for TermDD or any Remote Desktop source; read its own description and source on your server rather than assuming a meaning | not published by the vendor |
Confirm the fix worked
- The Certificate, X509 Certificate and X509 Certificate ID values under TermService\Parameters have been regenerated after the restart.
- The RDP listener’s Security Layer is set to something the connecting clients can actually use.
- A test session survives a large screen redraw and a file copy without disconnecting.
- TermDD Events 50 and 56 stop appearing in the System log during normal use.
- No TermService 1004, 1010 or 1088 events are being logged alongside them, which would mean a licensing fault is still in play.
Questions people ask about this
Is this a CAL or licensing problem?
Not by itself. TermDD 50 and 56 are certificate and security-layer faults. But Microsoft documents them alongside TermService 1004, 1010 and 1088, which are licensing events, so read the neighbouring entries before ruling licensing out entirely.
Is it safe to delete the certificate registry values?
It is Microsoft’s own documented remedy for this failure, and Windows regenerates them on restart. Export the Parameters key first so you can put it back, and if the machine is also an RD Licensing server, expect to reactivate it afterwards using the Telephone method.
Should we leave the security layer on RDP Security Layer?
Preferably not. That setting means the server is not authenticated to the client, which removes a real protection. Use it to confirm the diagnosis or to restore service for old clients, then update those clients and put a TLS-capable setting back.
What does Event ID 226 mean?
Nothing that Microsoft publishes. There is no documented Event ID 226 for TermDD or any Remote Desktop source. Open the event on your own server, read its description and its source, and treat any confident external explanation with suspicion.
Everyone disconnects at once, several times a day. Where do I start?
With the host, not the network. A fault that hits every client simultaneously is on the server – certificate, security layer, driver or offload – whereas a fault confined to one subnet, VPN or site is on the path.
