When controller disconnects, FFXIV does not re-activate and prioritize it on return

On PC, most current version with all updates installed. I have a Xbox Elite 2 wireless controller connected by Bluetooth called "Bluetooth LE XINPUT" which is designated in Windows as the "preferred" game controller device in Control Panel. There is a second wired usb "game controller" called Footswitch which is only used to control the mute status of the microphone and has no other functionality related to game play.

The wireless controller is designated as the controller I wish FFXIV to use in the FFXIV System Configuration in the Gamepad Menu. The wireless controller is recognized and it works correctly immediately when I boot up FFXIV without any further intervention.

Whenever the controller disconnects (usually for power save / idle reasons), FFXIV defaults to Footswitch for some reason. When I turn the wireless controller back on, FFXIV sees that the preferred controller is back, but it does not use it, and does not change the FFXIV System Configuration default back to the preferred game controller device; FFXIV just leaves it as "Footswitch" until I manually go back into FFXIV Settings and re-select "Bluetooth LE XINPUT".

The desired behavior would be that when the wireless controller re-appears and is detected by FFXIV, that the Windows system designated Preferred Controller is re-activated as the FFXIV preferred primary controller without having to manually go into FFXIV Configuration Settings panels. This is how the FFXIV system responds when there is no other "controller" attached to the system. The difference in this use case is that a non-preferred wired "controller" is not being de-selected.

I'm happy to provide screenshots or video of the steps to reproduce if required.

Thank you.

I may have solved the issue! And more!

Windows 11 = Device Manager (MICROSOFT DEVICE ASSOCIATION ROOT ENUMERATOR) = DISABLED

Update: After some more searching and trial and error, I may have found the solution. It was discovered about 8 years ago so I can't take credit, but apparently It's due to an incompatibility with the game's USB Enumerator Code and Microsoft's. I was able to get the device to finally stop having to be re-calibrated every time a USB device was interrupted, or every time the system "Hiccups", however, I still have the "Hiccups" that occur that cuts the sound and input. See Update 3!

Still no idea why it "Hiccups" with XIV (And only XIV), maybe it's still a sound device issue (This has basically happened for me for over two years now with DS5 Controllers). Back in patch 6.4 the audio would cut out completely when this happened but at least that was updated. I'll try troubleshooting this further as I was never expecting to even find a solution to this issue in the first place. This was fixed See Update 3 \o/

Update 2: I have tested this with multiple controllers plugged in at once, The DS5 Controller (Ps5) as well as a Logitech G29 Driving Wheel. Before, the behaviour would be that the controller would disconnect, and the G29 would become the default controller if plugged in, or, if the only controller, the Ds5 Controller would need to be Re-Calibrated in order for the back button (Share button) to function as the back button (it would change to the touchpad on the device every-time and would act as if the device was new or lost) The Controller remapping issue is confirmed resolved \o/

Update 3: So! It appears as though the issue with the audio cutting out was in fact a USB Device "Issue" as well, however, this was my bad, It appears that if USB selective suspend is active in the advanced battery settings, it causes the cut out of the game's device input / audio every-time the system suspends a USB device (Like a wireless mouse or a system background USB device being suspended). It is possible that this was the culprit the entire time, however, since I've never had to re-calibrate the controller I assume that All is good now.

So far all my device issues with the game appears to be resolved, Right before Dawntrail! I hope this helps someone, I created my own thread so that way people don't require searching through deep Necro Threads. ô7