[BUG] The computer with RDP gamepad installed won't сonnect via windows rdp default client.

[pold500]

Describe the bug
The computer with RDP gamepad installed won't сonnect via windows rdp default client.
To Reproduce
Steps to reproduce the behavior:

1. Install the software (RdpGamepad)
2. Leave computer running
3. Try to connect with windows remote desktop after some time (8 hours will do for sure, but I guess it's much less)
4. Remote machine doesn't respond to any connect attempts. Responds only after a reboot.
5. We have 40+ machines in our office and only machines with RdpGamepad show such behavior.

Expected behavior
Remote machine connects normally on rdp request.

Screenshots
https://imgur.com/a/msJ03fO

Please complete the following information:

• OS: Windows 10

This bug is extremelly annoying, many users suffer from it.

[jpflouret]

Can you please look at the Windows Logs/Application in the Event Viewer of the affected computers? Looking for errors probably with Winlogon as the event source.

[HappySapeta]

Is this issue active?
I have a similar issue where my RDP client would show a blank screen for a few seconds, and then display a disconnection error.
The problem only goes away after restarting the remote computer.

My client is running on a Windows 11 PC, and my remote computer is running Windows 10.

I wish I could add more info, but I don't have anything at the moment.

[jpflouret]

I believe this is an issue with the ViGEm bus driver. See nefarius/ViGEmBus#22

[mysticalfoxie]

And is there anything to fix it? A workaround? Something to install? A fork? The thread in ViGEmBus never seems to be resolved to a fix.