MCP RDP problems and fixes — Docs

Start with the last observation

Keep the error, the connection ID and the last useful screenshot. Do not share passwords, private desktop content or raw audio in a support report.

Connection and session problems

SymptomNext step

Unknown profileUse the supplied profile name; the deployment owner checks loading

DNS, refused or handshake failureVerify the approved target and its RDP service

Authentication errorFix the credentials before retrying; avoid repeated attempts

Unknown connectionIdCheck rdp_connection_list in the current session

All IDs lost after reconnectKeep one stable transport connection

Connection cap reachedDrop unused connections first

Symptom

Unknown profile

Next step

Use the supplied profile name; the deployment owner checks loading

Symptom

DNS, refused or handshake failure

Next step

Verify the approved target and its RDP service

Symptom

Authentication error

Next step

Fix the credentials before retrying; avoid repeated attempts

Symptom

Unknown connectionId

Next step

Check rdp_connection_list in the current session

Symptom

All IDs lost after reconnect

Next step

Keep one stable transport connection

Symptom

Connection cap reached

Next step

Drop unused connections first

Screenshots are black or stale

The first capture can be black before the desktop paints: wait briefly and capture again. With H.264, screenshots need the OpenH264 library on the host running MCP RDP; the server log shows AVC decode-to-RGBA unavailable when it is missing. If you cannot add it, recreate the connection with graphicsMode: "rfx", or legacy as a fallback. Keep maxSize at zero when you measure coordinates.

Pointer and typing problems

Check the target, focus and resolution before clicking again: repeated clicks can submit twice. After a timeout or reconnect, typed text can be duplicated, so reconcile it first. Split long text into shorter calls. Always read typed text back from a fresh screenshot. Clipboard send and receive do not transfer content in this release.

Recording and condensing problems

After requesting saveVideo, check that recording or analysisRecording is true. Run one recording at a time and call rdp_stop_video before the next. A condensed recording with no events on H.264 points at the missing OpenH264 library. Condensed savings depend on the content.

Notifications or resources are missing

HTTP transport does not deliver settled notifications; use bounded waits and screenshots. Resource reads need the owning session, and later captures can overwrite earlier files. Export evidence before the next recording or the end of the session.

Audio problems

A capture can start before the first remote audio arrives, so cause a sound and inspect the file. Microphone playback needs 16-bit PCM WAV, or raw input matching the negotiated format, from a file on the server host. A non-zero bytesDropped means audio was produced faster than the connection carried it.

A graphics channel error, a server disconnect or a redirection

A graphics channel error means the server closed the channel painting the screen: drop and recreate the connection. A logged server disconnect is the server ending the session, often by policy; take a repeated one to the server owner. A failed redirection names its reason; fix the server or broker configuration, or connect directly to the per-user endpoint, then recreate the connection.

What you getA remote desktop you can see and drive, with evidence saved before the session ends.