Mouse/Keyboard stops working after connecting controller

[vinikmv]

When using Duo V1.5.7, when the client connects to the session and pair/connects a controller (Xbox 360 Controller for Windows - Device Manager) the mouse stop working. The controller is connected using a 2.4GHz dongle instead of bluetooth
Tried reconnecting or connecting with another client but this problem persists until I restart the Duo Instance.

Tested locally in my PC and in a remote session in another network with other notebooks.

Patch Settings:
Only "Isolate HID Devices" and "Isolate Steam" activated

[Black-Seraph]

For starters: You can't have "Isolate Steam" enabled without also having "Process Patching" enabled.

Steam isolation is implemented as part of our AppCompat module.

Could you also explain what you mean by the mouse stops working and where it stops working? Are we talking about the remote session or the console session?

Overall it would help a lot if you could go into more detail and write a recipe of sorts to reproduce the issue from scratch.

If in doubt, too much info is better than too little, be detailed.

[vinikmv]

Looking more carefully, "Isolate Steam" was greyed out even with the toggle set to true, so I ended up reporting it incorrectly.

Here are the steps to reproduce (Tried with and without having the "Process Patching" enabled):
1 - Have Duo 1.5.7 installed
2 - Create an instance and start it in Duo Manager
3 - Have the user establish a remote connection to that instance with Moonlight
3.1 - At this point, mouse input works normally
4 - The user connects a controller to use in the remote session
4.1 - Instantly the mouse no longer moves and/or responds to inputs, as if disconnected.

Only during the remote connection does the mouse stop responding after these steps are reproduced.
If I, as the host, switch users to the account where the instance is associated, the mouse works normally.

To get the mouse working again for the user on the remote connection (Moonlight), I have to restart the instance in Duo Manager.

This issue was reproduced in two ways with the same results reported above:

A - Locally (Same network and same PC)
Connecting to the instance using Moonlight on the same host PC and connecting a controller;

B - Remotely
Connecting to the instance using Moonlight from different physical locations and network on a separate laptop with another controller;

Both controllers are connected using a 2.4GHz Dongle

[Black-Seraph]

Is the 2.4GHz dongle plugged into the host PC or the remote client?

[vinikmv]

In the Scenario A, the dongle is plugged on the host PC
In the Scenario B, the dongle is plugged on the remote client.

Different controllers are used in each scenario.
In Scenario A, the controller is a Machenike G5 Pro V2.
In Scenario B, the controller is an EasySMX X05 Pro.

[Black-Seraph]

When you encounter your mouse issue, is the stream itself still working?

For example, can you watch the Windows taskbar clock progress in your stream as time passes?

[vinikmv]

Yes, in the stream time continues updating on the taskbar clock through the stream. I also opened Task Manager and it also keeps its information updated as time passes after I connect the controller.
I was also able to confirm that it's not just the mouse but rather any input from the remote client, including the keyboard.
Mouse and keyboard input is not being transmitted in the remote session, but Moonlight still captures it since the session-ending shortcut works (Ctrl+Alt+Shift+Q)