Windows 10: replacing xinput

so i have three xbox controllers 2 new ones and one old the two new one use xinput drivers while the old one uses hid compliant game controller which lets it work for the game i need it for but i wanna use my new controllers for this game and xinput is making problems whenever i use the new ones in this game while my old controller doesn't have these problem so i wanted to know if there was a way to remove xinput for these new controllers and install HID compliant game controller driver instead without disabling driver updates

:)

 

XBOne Controller not working, XINPUT missing from Device Manager. HELP!

Okay, so a quick rundown. I just purchased Final Fantasy IX for PC (Steam) and it has some issues with controllers yet, since it was just released. I followed some steps that had been recommended, and now XINPUT does not appear under Device Manager > Human
Interface Devices... Also, now my XBOne Controller does not function. I've ran the directx redist package, and also reinstalled my graphics drivers as advised in other forum posts, but this issue remains. Help! I really appreciate it!

NOTE: I fear one of the steps I took, running CCleaners registry cleaner option may be the root cause of my troubles at this point, as I noticed this issue just after completing that suggestion.

 

Remove account

I suggest you backup your personalized files first before removing the account.
To delete an account, follow these steps:

1. Press WIN + X keys and click Command Prompt (Admin) from the menu.
2. Type the following command and press Enter. Replace test with the name of your sister's account. Code:

 

Disable XInput Keyboard/Mouse Simulation?

In my original post I state clearly that ALL XInput controllers do this for me. Xbox 360, Xbox One, Gamecube Controller Adapter, anything XInput.

I also have an XInput gamepad that's wireless and it has the same problems. I'm not sure why wired/wireless would even matter because it's a problem with the Creator's Update and how it handles XInput APIs as a whole.

If you read my initial post, I don't mention any error messages, I mentioned that I tried multiple, I mentioned that it happens inside games AND on windows desktop, and I quite literally stated that it was the Creator's Update
being the only change.

As for "Is this issue affecting other parts of your controller?" What does this have to do with anything? The problem isn't with my controllers, it's with how W10 Creator's
Update (1703) handles XInput.

I know this sounds rude, but I mean it in the most sincere way: Please read my first post. Also I've already checked those "helpful" resources out. They don't contain any info on this problem.