Raphnet adapter manager Failed to open adapter? Windows 11 about gcn64tools

[claabs]

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

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
   
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]

Thank you, you solved my problem and now I can access the raphnet administrator and also the configuration of the gaming device

[Gabriel2Silva]

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

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
   
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]

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]

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