Xbox/XInput blocking through UI Client broken

[nefarius]

Reminder to do a test run and pinpoint why apparently Xbox controller (and similar variants) blocking is either not working at all or not reliably.

[ShiveringLampshade]

Hi, I'm currently running into this issue with an Xbox 360 controller on Windows 10. The controller is currently selected with device hiding enabled but the game I have tested (Rocket League) is still recognizing it. Happy to provide any further info to aid with the investigation

[nefarius]

I know, still broken, haven't had time to look into it ❤️

[ShiveringLampshade]

No problem 🙂 In my testing its only the 360 controller having the issue, 1st generation Xbox One controller works perfectly fine with HidHide

[Serfrost]

I can also confirm this is happening with my Dualsense (PS5) controller.

Edit: Seems this was caused by Windows update / upgrading to Windows 11. Uninstalling HidHide using the installation MSI, rebooting, and then reinstalling the HidHide using the MSI seems to have resolved this problem.

[nefarius]

It works reliably using the CLI instead as a workaround and not using Beta products like Windows 11 😜💙

[Serfrost]

It works reliably using the CLI instead as a workaround and not using Beta products like Windows 11 😜💙

Maybe you missed my edit. All's good. lol

[Kanuan]

IIRC, some Windows update break HidGuardian / HidHide. There were many similar reports from users with Windows 7/8/10 in the past (me included). Luckily it just seems to clear the registry entry and the solution is just to reinstall the driver.

[nefarius]

@Serfrost I didn't miss it, just like the chance to bash Windows 11 😁

[Serfrost]

@Serfrost I didn't miss it, just like the chance to bash Windows 11 😁

Oh. lmao I should have caught that since it was only a part of the edit. I have my own grievances with 11, but it's mainly that they took away my ability to move the taskbar to the left / right of the screen. Broke a lot of my automated tasks with Autohotkey. Assholes. Other than that I've had a decent time since June.

[nefarius]

There is so much wrong with Windows 11. The absolutely avoidable planned obsolescence with their ridiculous hardware requirements (I don't care if workarounds exist, it's about the mentality), forcing TPM which improves literally nothing in regards to exploitability, having changes introduced that break core functionalities without having the documentation updated so nobody has any clue why software breaks that worked flawlessly for every Windows 10 revision etc. and so on and so forth.... It's a dumpster fire for me as a developer.

Rant over 😛

[Serfrost]

Yeah, I come from strictly on the user side. As for ya'll on the dev side of the fence, I can see how it's just getting increasingly worse so long as everything keeps getting thrown under the bus. Hopefully that changes for the better.