Game Controller Settings Window (Windows Common Shell DLL) freezes

As the title says, I've had this issue since around 1st the June now when a Windows update came out.

What happens is that seemingly regardless if I have controllers plugged in or not, and if it's plugged in, it doesn't matter what kind of controller I plug in, the Game Controller Settings (Windows Common Shell DLL, shell32.dll) window keeps freezing all the time. It'll unfreeze for a little moment before freezing once more.

This wouldn't be too big of an issue - if it wouldn't also impact Steam and games, making it take few minutes for first Steam to recognize the controller - and then a minute or more for Steam to actually assign the controller to work in-game.

I've gone to Microsoft Support about this all the time now. They've made me do:
- System Restore
- Rolling Back to older version
- In-Place Upgrade
- Rolling Back again to older version
- PC Reset
- and Windows Clean Re-Installation

And each time the problem persists.

I've added the crash report and the msinfo32.txt into the attachment for people to check. Let me know what else I can offer to give more info about.

Thanks in advance.

I have the same problem have you solved it yet and if so please indicate how you solved it thanks!

SMERSH said:

I have the same problem have you solved it yet and if so please indicate how you solved it thanks!

I have solved it, and it's the most stupidest thing ever

...The keyboard I had was making it do that. Once I unplugged my Corsair K55 from my computer, everything works like normal. Once it's back plugged it the game controller settings window jams once more.

Thank you Finngon!! I made an account just to reply to this post. I was having the same issue with the same keyboard!

Thank you so much! I have had this problem forever and could not figure out what it was. I always blamed the Corsair keyboard but I could not prove it.

Is there no way to get around this besides getting a new keyboard? I tried killing the iCue software that runs with the keyboard but it did not help. Maybe I will try preventing that from starting with Windows and see if it gets better.

rngeoff said:

Thank you so much! I have had this problem forever and could not figure out what it was. I always blamed the Corsair keyboard but I could not prove it.

Is there no way to get around this besides getting a new keyboard? I tried killing the iCue software that runs with the keyboard but it did not help. Maybe I will try preventing that from starting with Windows and see if it gets better.

When I discovered it I found no ways to go around it. I returned the item as I had the return policy available for it. I had to plug in my reserve keyboard (old as heck, but hey, it works) until I went to buy a new keyboard (Gamdia Hermes P1).