• Happy holidays, folks! Thanks to each and every one of you for being part of the Tom's Hardware community!

Question Xinput controller stalls Google Chrome while plugged in after reinstalling Windows 10

Dec 13, 2020
2
0
10
I have a ZD-T408 xinput controller, and I have never had any software problems with it before until just recently., where, after completely reinstalling Windows 10 from scratch, connecting it with Chrome open results in the application stalling, and attempting to interact with it causes it to report as Not Responding. It continues to be completely unresponsive until I unplug the controller, at which point it immediately resumes normal operation. I have installed all DirectX packages using the Web Installer, and have all Xinput drivers necessary. The odd thing is that I never had this issue before reinstalling Windows. I have also tried connecting it, then opening Chrome, with the same result. I have had this issue before installing any other software other than Chrome, and before installing the DirectX packages. No other applications respond in this manner as far a s I can tell. I am wary of reinstalling Chrome, since doing so will result in needing to relog into all websites again (over 50), which I will only do as a last resort. What steps can I follow to further diagnose the problem? Is there a fix? Has anyone else encountered similar problems? Any help is appreciated.
 
Update: I have since installed all .NET Framework versions and security updates, as well as all MSVC Redistributables, and now the issue doesn't happen anymore. I have not installed any other software other than those and VirtualBox. I have absolutely no idea which install fixed it, as I used software from MajorGeeks to update them all at once, so I couldn't test one at a time. The real question is, how could outdated versions of either of these types of software even remotely affect Google Chrome? I don't see any reason for Chrome to use MSDN except for installed Apps (which are run in their own sandboxed memory space), and I've never seen a MSVC-dependent feature in Chrome in my entire life. What gives?
 
I'm having the same issue with a new x-input controller as well (https://www.nacongaming.com/en-GB/wired-compact-controller).
As soon as I plug it in it will stall any browser I'm using (tried Chrome, Firefox and Edge) making them not respond; and if I plug it out again they go back to working normally as if nothing had happened...
I'm clueless as of why and would appreciate any help.

EDIT: Tried using every single USB port I have and in one of them the problem doesn't occur. :??: It's a USB 3.0 port if that changes anything
 
Last edited: