It's laughable that people think they can tear windows apart to make it run better.
It's laughable because Microsoft could fix it but hasn't. This forces the user community to find work arounds.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
When playing any of my games launched through Battle.net my entire PC will crash, when checking the Reliability Monitor 100% of the time the crash is preceded by a "Successful application reconfiguration" of Microsoft GameInput. I have zero need for GameInput and for what I play I have no issues when I uninstall GameInput, but Microsoft forces the install each time my computer restarts.
I've looked for this issue an is appears it started for users with Windows 10 but there's no solution ever found. Microsoft support has people check their drivers, etc (all of my drivers are up to date and Windows is fully up to date) but no actual solution is offered. As far as I'm concerned I own my computer and should be able to determine which services I do or do not have installed on my PC but Microsoft is forcing this buggy install and I am unable to delete or otherwise modify the root folder this application is contained in.
I'm desperate for some sort of solution to this problem and it would be great if Microsoft would fix whatever this issue is. Having to remember to uninstall this app every time I want to play a game on my gaming PC is frustrating.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
It's laughable that people think they can tear windows apart to make it run better.
It's laughable because Microsoft could fix it but hasn't. This forces the user community to find work arounds.
Although GameInput is part of the GDK (GamingDevKit) it is the new input mechanism on all Windows devices including XBox and Windows. It is written to be the replacement for all previous input systems. And it will eventually be moved to the Window SDK. You can think of it as part of Windows. App developers will use it because it's recommended, and it supersedes the previous API's. It's not just for gaming. That's just in the name, are you afraid of the word 'game'?
If GameInput is exhibiting crashes, then report those crashes to MS, don't try to uninstall GameInput service. It's a live COM service that is providing input to applications (and games). How do you expect those applications to work if you keep ripping out their input services. lol. It's laughable that people think they can tear windows apart to make it run better.
First of all, don't confuse "GameInput" and its service(s) with "Gaming Services"...
Now try this (found on Reddit): https://www.reddit.com/r/WindowsHelp/comments/18bb6e0/comment/kcw2mem/?utm_source=share&utm_medium=web2x&context=3
In short, just open your installed app panel and isolate "gameinput": if you find something dated around feb-march 2023 UNINSTALL IT (it seems an old MS leftover for Win10), and cross your fingers 🤞🏻:
EDIT:
Tested this myself and on next reboot Win11 23H2 silently reinstalled it (same version 10.1.22621.3036), BUT now I have a single GameInput Service (Auto, triggered. "Restart service" when it fails) and no uninstall option in the App list:
I started face with this issue after recent Microsoft updates. On my Asus Rog Laptop with Windows 11, it usually restarts due LSP not signed issue after Windows Installer reconfigures Microsoft Game Input even though i disabled or delete any related services, files or stop any tasks. I've done quite many steps here and there through registery, command and configuration. After spending tremendous amount of attempts until Microsoft finds a solution i found this solution works for me;
Unplug the power cable and run the laptop on battery. ( Strange, isn't it ? )
Hope that is works for anyone out there having the issue. It is a real bugger.
Did you do anything specifically to fix it? As ur last post of 17th december mentions you still have the issue.
Maybe I buried the fix in the response. But here's what I did:
Good luck