Keyboard Input Lost in RouteMatch Application When Using Seamless Mode in Parallels RAS

0 users found this article helpful

Symptoms

Users accessing the RouteMatch application through Parallels Remote Application Server in Seamless Mode (Published Application / memshell) may experience intermittent keyboard input issues.

The issue may present as follows:

Cause

This issue is caused by an application-specific interaction between RouteMatch and the Parallels RAS seamless engine (memshell).

RouteMatch may take additional time to process internal focus changes. When users switch back to the session, this can lead to a timing conflict between the application's internal focus handling and the memshell window activation process.

As a result, the application window appears active, but keyboard input is not properly routed to text input controls.

Resolution

Option 1: Apply registry workaround

Apply the following registry setting on each affected RDSH server:

Path: HKLM\Software\Parallels\Wow6432Node\MemShell
Value Name: ActivationMode
Value Type: REG_DWORD
Value Data: 1

This setting adjusts the memshell activation behavior and prevents input handling issues.

Note: This workaround requires Parallels RAS 21.1 Update 1 or later.

Important considerations

Setting ActivationMode = 1 disables the use of AttachThreadInput().

While this improves keyboard input reliability, it may introduce minor side effects, such as:

Option 2 (Recommended): Upgrade RAS

For a permanent resolution without side effects, upgrade to Parallels RAS 21.2 or later.

This version includes improvements to the seamless engine activation logic and resolves the issue without requiring registry changes.

Additional Notes

Was this article helpful?

Tell us how we can improve it.