Did almost everything but compatibility mode could put it in windows 10 the non working games

F310 controller has both XInput and DInput support. You can flip the switch, on the controller to switch b/t the two.

Another problem might be some older games don't support controllers - and at that point, might be best to go online and look for Controller Emulators and/or any games w/ profiles online to download, which can make it just like its console version.

For example - I use with BG&E GOG Version a gamepad app called AntiMicroX and a profile for that which someone made for BG&E.

Microsoft updates are notorious for breaking compatibility.

I did play in the compatibilty for bastion it worked but having a hard time to make other work do not know which file to look for ,is it the launcher in the folder ?

Actually Microsoft has about the best compatibility of all.
Try using a PS1 controller on a PS5 .... no? Or run games from 1995 on a PS5
Or use a PS5 controller on a PS4. Or run a PS3 game on a PS4 without that emulator chip installed. Only from 4 to 5 there is a certain compatibility.

I found the steam configuration options for controllers were really good for Dead Space original which otherwise has big issues with sensitivity and the deadzone was too large. But I was able to fine tune it to perfection, at 60fps (game defaults at 30). I too use an Xbox one and a series controller on PC.

Not from what i usually see. Every couple months it's Dosbox issue after update (like keyboard won't work, won't full screen or other issues), controllers don't work after updates, game won't start after update, game is very sluggish after update. Game crashes after update.

Maybe they are doing better, i don't know. But i just don't see updates as helpful.

The DosBox fullscreen problem has nothing to do with Windows, that was a graphic driver update, a certain outdated overlay mode was no longer supported. Different overlay mode, problem solved.

Keyboard not working I have never seen. When Alt tabbing random keys are pressed, but that's an old DosBox error. And don't forget that the DosBox version we have here is ancient, the code is a mess. Use DosBox Staging and be good.

Game crashes after update ... I heared that before. Funny that it never affects ALL players who installed that update, but only a hand full. People keep blaming Windows "after update", but usually it has nothing to do with it. Peopler don't even bother to read what the update was about but are quick to blame it for all their booboos. As long as game programmers follow Microsofts standards and don't hack the DLLs or use them in a way not intended, it's very very very rare that a Windows update can cause problem.
Telltale games crash, when you start them with Windows 10 and a XBox gamepad connected? Yes, they do, because DInput was changed, new functions were added and old stuff was removed. But why don't all games crash then? Because the other programmers adressed the DLL as they should and didn't call functions that had been marked as deprecated years ago.

And no one of the "but it worked 10 years ago!!!" guys ever tries the compatibility options. Yes, Windows changes, but these options are to have certain Windows functions like they did in older Windows versions.

Is it perfect? Heck no, but there is nothing else that comes even close to Windows when it comes to compatibility.

For me, the main weakness of xinput is that people stopped supporting dinput. I don't think a new standard is the solution.

https://xkcd.com/927/

It's also less flexible, supports less axes and buttons, no keyboard, no mouse. XInput was designed around the XBox 360 pad, additional buttons on a pad are not supported, also if we had a pad with a touchpad like the ps4 one it would not work. That it only supports 4 controllers should not be a problem, it's very rare that one has 4 controllers in the first place. I still have to look into what the next controller standard is about.

If they created what is essentially direct input 2.0 and made it properly backwards compatible with both direct input and xinput then I guess that would be great. Something that allows a large number of possible axes, plus support for the gyroscopes that modern controllers usually contain and things like touchpads.
Xinput-only controllers don't work properly with Dinput games as they misreport the trigger axes (summing the two triggers to a single axis, even though Dinput supports way more axes).
Dinput-only controllers aren't recognised by Xinput games, which is also a failing of Microsoft's (probably deliberate in order to try and sell 360 controllers).

As long as the new standard goes back to being as flexible as directinput, I have no problem with it.
It sounds like something other than your controller is set as "controller 1" and is interfering. I'd guess some kind of virtual gamepad software got installed alongside a game you installed (or perhaps Steam itself).