RDCMan 3.x regression: incorrect Bulgarian keyboard layout injected into RDP sessions

Hello,

I would like to report a keyboard layout regression in RDCMan 3.x.

When connecting to a remote Windows Server using RDCMan 3.x, an additional incorrect keyboard/input method is injected into the RDP session:

English (United States) → Bulgarian (Typewriter)

This input method is not configured on either the client or the remote user profile.

The expected configured input methods are:

English (United States) → US

Bulgarian → Bulgarian (Phonetic Traditional)

The issue is consistently reproducible with the same client PC, same user account, same remote server and same RDG configuration:

mstsc.exe → PASS

RDCMan 2.93 → PASS

RDCMan 3.x → FAIL

RDCMan 3.x creates the following three input methods inside the remote session:

ENG English (United States) → Bulgarian (Typewriter) [incorrect]

ENG English (United States) → US [correct]

BGR Bulgarian → Bulgarian (Typewriter) [session display]

The incorrect first entry reappears after disconnecting and reconnecting with RDCMan 3.x.

I verified the persistent Windows language configuration on both the RDP client and the remote server.

Get-WinUserLanguageList reports:

LanguageTag : en-US

InputMethodTips : {0409:00000409}

LanguageTag : bg

InputMethodTips : {0402:00040402}

The corresponding keyboard layouts are:

00000409 = US

00000402 = Bulgarian (Typewriter)

00040402 = Bulgarian (Phonetic Traditional)

On the client PC the registry configuration is:

HKCU\Keyboard Layout\Preload

1 = 00000409

2 = 00000402

HKCU\Keyboard Layout\Substitutes

00000402 = 00040402

Therefore, the client is correctly configured for:

en-US → US

bg → Bulgarian (Phonetic Traditional)

No en-US → Bulgarian (Typewriter) association exists in the persistent language configuration.

I also verified the remote user profile. Its language profile contains only:

HKCU\Control Panel\International\User Profile\en-US

0409:00000409 = 1

HKCU\Control Panel\International\User Profile\bg

0402:00040402 = 1

Get-WinDefaultInputMethodOverride is not configured.

Therefore, the additional English (United States) → Bulgarian (Typewriter) input method appears to be created transiently during RDP session initialization by RDCMan 3.x.

This behavior does not occur with mstsc.exe or RDCMan 2.93.

This is a significant issue in our environment because I manage more than 200 servers through RDG files. Modifying the keyboard configuration on individual RDP servers is therefore neither appropriate nor a viable workaround, particularly because the same servers work correctly with mstsc.exe and RDCMan 2.93.

Expected behavior

RDCMan should preserve the configured keyboard/input methods and should not create an English (United States) → Bulgarian (Typewriter) input method during connection.

Actual behavior

RDCMan 3.x introduces an additional English (United States) → Bulgarian (Typewriter) input method into the active RDP session. It may also become the active input method, causing Bulgarian characters to be typed while the language indicator reports English.

Regression summary

Same client PC

Same Windows user

Same remote server

Same remote user profile

Same RDG configuration

mstsc.exe PASS

RDCMan 2.93 PASS

RDCMan 3.x FAIL

Please investigate the keyboard layout/KLID handling during RDP session initialization in RDCMan 3.x, particularly how the RDP client/ActiveX control handles the Bulgarian base KLID 00000402 together with the substitution to 00040402.

I can provide screenshots, RDG configuration details, PowerShell/registry output, or additional tracing if required.