Thanks, got it fixed but not the way I predicted. I do understand how firmware works I just frustratingly typed the wrong thing. Got the throttle fixed but this was unconventional after speaking with Thrustmaster tech support.
First thing I did was uninstall the drivers and reinstall the drivers. I also performed the bootloader process to ensure a clean install of the firmware, which I thought was faulty, it was not.
I read on a post on the interwebs somewhere that one individual was having problems with the mb settings using USB 3.0 vs 2.0 and an enabled BIOS setting called xHCI. I turned it off and rebooted and then plugged my devices into the 2.0 USB slots. No joy. I then plugged them into the 3.0 slots and experienced the same thing, no joy. I then returned to BIOS and enabled xHCI and plugged devices into the 3.0 slots. It worked. I have no idea why. I also removed all the power management features for all the USB devices under device manager.
To summarize this is a Win 10 and new motherboard problem, not a Thrustmaster Warthog HOTAS problem. I tried calling the computer manufacturer yesterday but got no answer while on hold, figured they were answering thousands of calls from families who had never bought a computer before.
Alas, I will update as I discover more if anything from the mb manufacturer and the computer manufacturer as I suspect future problems for folks buying more advanced machines.
Now that I have the HOTAS throttle working, (joystick always worked...) I am still having issues with the coolie hat essentially operating in repeat mode whereas I cannot long press coolie hat to establish SOI. The slew button behaves like its an inverse x and y and also has no stops, it just keeps on drifting as soon as I engage it. Can anyone give me some advice on how to make that work/behave better, perhaps a thoroughly fleshed out throttle profile?