Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
pold500 opened this issue Feb 9, 2022 · 3 comments
Labels
bug Something isn't working question Further information is requested

Comments

@pold500
Copy link

pold500 commented Feb 9, 2022

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.

@pold500 pold500 added the bug Something isn't working label Feb 9, 2022
@jpflouret jpflouret self-assigned this Feb 18, 2022
@jpflouret
Copy link
Contributor

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.

@jpflouret jpflouret added the question Further information is requested label Feb 18, 2022
@jpflouret jpflouret changed the title [BUG] [BUG] The computer with RDP gamepad installed won't сonnect via windows rdp default client. Feb 18, 2022
@HappySapeta
Copy link

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
Copy link
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants