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

Raphnet adapter manager Failed to open adapter? Windows 11 #22

Open
Loliconera opened this issue Mar 24, 2024 · 5 comments
Open

Raphnet adapter manager Failed to open adapter? Windows 11 #22

Loliconera opened this issue Mar 24, 2024 · 5 comments
Assignees

Comments

@Loliconera
Copy link

Loliconera commented Mar 24, 2024

Hello, I am using Windows 11, the program works but I could not update the firmware of the Classic controller to the USB adapter - V3 using Windows 11, it is only possible to update the firmware of the Classic controller to the USB adapter - V3 using Windows 10. The problem is that since today I received a big update from Windows Update on my Windows 11... and now every time I try to select the device from the Raphnet adapter management program it does not work or load, also when I try to configure USB gaming devices. I see 2 WUSMote v2.2 USB devices connected but when I try to select and test the buttons I get an error in the game controller, what about Windows 11 incompatibility issues?

but when it comes to selecting the controller within the GUITAR HERO WORLD TOUR game everything seems to work perfectly so the problem is in the Raphnet adapter manager program

image
image
image

@claabs
Copy link

claabs commented Mar 26, 2024

After scouring my Windows update history, I found the update that broke this:

image

The "Logitech - USBDevice - 1.0.51.4614" driver update had a bunch of people complaining online about it. To fix it for the Raphnet adapter, you just need to disable the Logitech LampArray Service.

  1. Open Task Manager (CTRL+SHIFT+ESC)
  2. Go to Services, and search for logi
  3. Right click the logi_lamparray_service, click Stop
    image
  4. Right click the logi_lamparray_service, click Open Services
  5. Locate Logitech LampArray Service, right click, click Properties
  6. Under Startup type, change it to Disabled. This ensures it doesn't start after a restart.
  7. Your Raphnet Manager should work immediately

@Loliconera
Copy link
Author

Thank you, you solved my problem and now I can access the raphnet administrator and also the configuration of the gaming device
Sin título
image

@Gabriel2Silva
Copy link

After scouring my Windows update history, I found the update that broke this:

image

The "Logitech - USBDevice - 1.0.51.4614" driver update had a bunch of people complaining online about it. To fix it for the Raphnet adapter, you just need to disable the Logitech LampArray Service.

  1. Open Task Manager (CTRL+SHIFT+ESC)
  2. Go to Services, and search for logi
  3. Right click the logi_lamparray_service, click Stop
    image
  4. Right click the logi_lamparray_service, click Open Services
  5. Locate Logitech LampArray Service, right click, click Properties
  6. Under Startup type, change it to Disabled. This ensures it doesn't start after a restart.
  7. Your Raphnet Manager should work immediately

Thank you so much!

@raphnet
Copy link
Owner

raphnet commented Apr 13, 2024

Thank you for this information. I will be getting logitech input devices to try to reproduce this and hopefully find a way to avoid such issues.

@raphnet
Copy link
Owner

raphnet commented Apr 25, 2024

This is solved in adapter manager release 2.1.29. Confirmed with a G512 keyboard, Windows 11 + G HUB and Windows Dynamic Lighting.

So for some reason many RGB light control services and software open HID devices in shared mode. No idea why they don't skip devices with non-matching vendor IDs...

Anyway, due to those services holding a shared mode handle for the adapter, opening fails when the adapter manager tries to acquire an exclusive handle. The workaround implemented in the new adapter manager release is to simply retry opening the adapter in shared mode, since there is no other choice.

See commit 64abff9 for details.

Regarding the other issue mentioned in the initial post, this is not a Windows 11 compatibility issue. Adapters work fine with Windows 11. A minority of users have reported seeing double adapters sometimes in joy.cpl since i think the days of Windows 7. There are workarounds for this documented here:

https://www.raphnet-tech.com/support/testing/index.php#joycplerror

@raphnet raphnet self-assigned this Apr 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants