RDM 2023.2.28.0 64-bit not opening sessions with display "External"

Implemented

RDM 2023.2.28.0 64-bit not opening sessions with display "External"

avatar

Hi all,

as title I have the problem that opening sessions with display "External" closes immediatly.
example:



This is the log:



as you see I have this problem from days. Trying using for example "Undocked" works
how can I resolve?

3e2c0ae4-2a82-478f-a131-231457f64436.png

a7109230-c5a4-4e96-baeb-d5a0b924ab5a.png

All Comments (7)

avatar

Hello,

An internal ticket has been created for an issue that appears similar to yours. To confirm whether your issue is related to the other one, could you please perform the following tests or answer the following questions?

1.     Have you installed the latest version of Windows (KB5030219)?

2.     Could you try disabling RDP API hooking and then restart RDM to see if it resolves the issue? For instructions, please refer to his link: https://docs.devolutions.net/kb/remote-desktop-manager/knowledge-base/microsoft-rdp-api-hooking

3.     If disabling RDP API hooking doesn't help, please re-enable it. This time, turn on the RDP logs provided by RDP API hooking to help us better understand Microsoft RDP's internal behavior. For instructions, please refer to this link: https://docs.devolutions.net/kb/remote-desktop-manager/knowledge-base/microsoft-rdp-api-hooking/#microsoft-rdp-logging

If you have any further questions, concerns, or require additional support, please don't hesitate to let me know. I'm here to assist you.

Best regards,

Carl Marien

avatar
Hello,

An internal ticket has been created for an issue that appears similar to yours. To confirm whether your issue is related to the other one, could you please perform the following tests or answer the following questions?

1.     Have you installed the latest version of Windows (KB5030219)?

2.     Could you try disabling RDP API hooking and then restart RDM to see if it resolves the issue? For instructions, please refer to his link: https://docs.devolutions.net/kb/remote-desktop-manager/knowledge-base/microsoft-rdp-api-hooking

3.     If disabling RDP API hooking doesn't help, please re-enable it. This time, turn on the RDP logs provided by RDP API hooking to help us better understand Microsoft RDP's internal behavior. For instructions, please refer to this link: https://docs.devolutions.net/kb/remote-desktop-manager/knowledge-base/microsoft-rdp-api-hooking/#microsoft-rdp-logging

If you have any further questions, concerns, or require additional support, please don't hesitate to let me know. I'm here to assist you.

Best regards,


Hi,

  1. Yes
  2. Disabling api hooking made it work again with external settings, thx


Can you tell me the difference between external and internal RDP? wich is the most stable?

avatar

Hello,

Are you referring to the distinction between "external" and "undocked" sessions?

  • "Undocked" refers to sessions that RDM initiates but displays in a separate window.
  • "External" implies that another application is responsible for launching the session.


Best regards,

Carl Marien

avatar

We have also experienced this since KB5030219. Will there be a more permanent solution than disabling API Hooking?

avatar

Hello,

Our development team is actively working on resolving the issue you've reported. We will keep you updated on our progress.

Best regards,

Carl Marien

avatar
Hello,

Are you referring to the distinction between "external" and "undocked" sessions?
  • "Undocked" refers to sessions that RDM initiates but displays in a separate window.
  • "External" implies that another application is responsible for launching the session.

Best regards,


I meant the difference between the external application and the "internal" (undocked or docked) RDP application.
What's the key difference?

avatar

Hello,

I apologize for the confusion.

To clarify, there is no functional difference between the "undocked" and "docked" modes. There is no version that is more stable than the other.

Best regards,

Carl Marien