it77

Hello Michel,

thank you for the detailed explanation. Here are the results from our side.

1. Registry (EnableRDPHooking)

We checked two machines (both Windows 11, build 10.0.26200.9711, AMD x64 devices, so not ARM):

- Machine A: the Launcher fails with our RDP entry.

- Machine B: Remote Desktop Manager works with the same entry.

On both machines the value EnableRDPHooking is not set (reg query returns "value not found") under all four keys:

- HKLM\SOFTWARE\Policies\Devolutions\RemoteDesktopManager

- HKCU\SOFTWARE\Policies\Devolutions\RemoteDesktopManager

- HKLM\SOFTWARE\DevolutionsLauncher

- HKCU\SOFTWARE\DevolutionsLauncher

So no policy differs between the machines. In Remote Desktop Manager the "Enable API hooking" option is set to "Default".

2. Launcher log

We cannot find "Help > Troubleshooting > Application logs" in Launcher 2026.3.15.0. [Entries we see under Help: ...] Where is the Launcher log stored, or how can we open it? Could you also tell us whether there is a log or debug option for the MsRdpEx hooking in the Launcher?

3. More details

- All machines on which the Launcher is used are affected. Machines using Remote Desktop Manager are not. [CONFIRM]

- Only one target server fails. Other RDP entries through the same gateway work in the Launcher. [CONFIRM]

- A workaround: with "Force using IP address for RDP connections" enabled on one of our two gateways, the sessions in the Launcher worked immediately (tested twice). This option is set per gateway. We know it should not be needed with hooking.

- We will also check whether MsRdpEx.dll is loaded into mstsc.exe with "tasklist /m MsRdpEx.dll" while the error window is open, and compare it with an external session started from Remote Desktop Manager. Result: [mstsc.exe loaded / not loaded in the Launcher session; loaded in the RDM session].

Please let us know what else you need.

Best regards

Hello,

after upgrading our environment to 2026.3, RDP entries that go through the Devolutions Gateway fail when started from the Devolutions Launcher on some machines, but work in Remote Desktop Manager.

Environment

- Devolutions Server 2026.3.12.0 (upgraded from 2025.2.5.0), Console 2026.3.10.0

- Devolutions Gateway 2026.3.0, two gateways (one side-by-side with DVLS, one standalone)

- Remote Desktop Manager 2026.3.15.0, Devolutions Launcher 2026.3.15.0

- Gateway "Force using IP address for RDP connections" is a per-gateway setting

Problem

The Windows RDP client (mstsc) shows:

"The connection cannot be completed because the remote computer that was reached is not the one you specified. This could be caused by an outdated entry in the DNS cache. Try using the IP address of the computer instead of the name."

(error code 0x0)

What we see

- The same RDP entry works in RDM (API hooking enabled under File > Settings > Types > Sessions > Remote Desktop (RDP)).

- Direct RDP from the same machines (without the gateway) works.

- Gateway log: for the failing attempts the gateway logs "Upstream forwarding" and then "Forwarding ended abruptly ... os error 10054" within 44 to 80 ms. We counted 16 such attempts from three client machines to one target server, plus a few to a second server. Successful sessions to the same targets from other machines last for minutes.

- All RDP sessions show up in the gateway log as generic_client (plain TCP forwarding), so we assume the name validation happens end-to-end between mstsc and the target server.

- With "Force using IP address for RDP connections" disabled, the sessions fail as described above.

- After enabling "Force using IP address for RDP connections" on one of our two gateways (the standalone one), the Launcher sessions through this gateway worked immediately (tested twice).

- In RDM we can find the "Enable API hooking" setting, but we cannot find an equivalent setting in the Launcher.

Questions

1. Does the Launcher apply Microsoft RDP API hooking (MsRdpEx) for external mstsc sessions through the Devolutions Gateway? If yes, where is it configured, and is the EnableRDPHooking policy honored?

2. Is "Force using IP address for RDP connections" meant to be required for Launcher clients? Are there side effects, for example a fallback from Kerberos to NTLM?

3. Is this a known issue in 2026.3.x?

Thanks!

Hello Devolutions Support Team,

we are currently experiencing an issue with our Devolutions Server after refreshing the license.

Issue description:

After clicking “Refresh License”, all users were logged out of the Devolutions Launcher and are no longer able to authenticate using Microsoft (Entra ID).

We are receiving the following error message on the login screen:

Invalid license (Product: Launcher)

Current situation:

• Licenses are displayed as fully assigned (e.g. 9/9 users)

• AD groups are still correctly assigned

• No changes were made to authentication configuration

• The issue started immediately after refreshing the license

Additional observations:

• When attempting to re-add the product license, the “Add” button is greyed out

• This suggests the license cannot be validated or re-applied

• Users are completely blocked from accessing the Launcher

Environment:

• Devolutions Server version: 2025.2.5.0

• Authentication: Microsoft (Entra ID)

• License type:

  • Remote access management package (9 users)

  • Remote desktop management & IT operations (5 users)

Troubleshooting already performed:

• Verified license is still valid and not expired

• Confirmed AD group assignments are intact

• Attempted to re-add license (button disabled)

• Issue persists across all users

Kind regards

Omar

Hello Devolutions Support Team,

we are experiencing an issue with the Devolutions Launcher in combination with Netwrix Password Secure.

Issue description:

When opening the entry through the Devolutions Launcher, the fields “Database” and “Username” on the Netwrix Password Secure login page are not filled in automatically.

However, when accessing the same URL directly via Microsoft Edge, the fields are populated correctly.

Environment:

• Access via: Devolutions Launcher

• Target application: Netwrix Password Secure (web login)

• Browser used in Launcher: integrated/embedded browser

• Direct access via Edge: works as expected

Expected behavior:

The fields “Database” and “Username” should be automatically filled with the values stored in the Devolutions entry, just like when opening the page directly in Edge.

Actual behavior:

Both fields remain empty and must be entered manually.

Could you please advise whether a specific configuration is required in the Launcher, or if this is a known issue?

Thank you in advance.

Ait Malek Omar

Dear Support Team,

we would like to report an issue with the Launcher.

Problem description:

When a server is selected in the Launcher and a session is started, the message “Authenticating” briefly appears and then disappears. After that, nothing happens.

The session is not established and no further error message is displayed.

The users authenticate via Microsoft authentication.

The Microsoft authentication itself is working correctly and has been tested successfully.

The Devolutions Server is currently running version 2025.2.5.0.

Observations:

• With version 2025.2.23.0, session startup works without any issues.

• With newer versions, the described problem occurs and sessions no longer start.

• The server and session configuration has not been changed.

• Access via RDP works correctly; the issue affects only the Launcher.

We kindly ask for your support in analyzing this issue and let us know if this behavior is known or if there is a recommended fix or workaround.

Thank you very much for your assistance.

Kind regards,

Ait Malek Omar