Controller Firmware Update - Messed up my controller?!?

Yup, the newest update just knocked my controller out with same exact stuff... and its only 3 months old.... this last update got me angry because now I got a very expensive paper weight.... both system and controller...

Very unhappy they need to fix this.... because taking out batteries is worthless and helps only for a half a nano second....

I literally have the exact issues as you after updating my controller tonight. It was an update from November so I figured I should do it and now my controller is completely messed up. I bought a usb-c to usb wire to hard connect to console so I can try to revert back to the previous firmware. This is complete bs and Microsoft is doing nothing to fix it.

I did it, it appear a screen that says "Something went wrong

Your controller is already up to date"

And then I can only press the "cancel" button and the system bring me to the controller menu, without any chance to revert the firmware.

I've had this problem for a month now ever since I received that newest firmware update that I believe was given to people part of the insider program since I have some friends not part of the programs whose controllers never received an update and still work on their computers. I hate that the only solutions are just workarounds and not really a solution. I have the same problem that everyone else is having with inputs being completely ruined. I have friends that have controllers that will disconnect randomly and refuse to pair. The only way that I've been able to work around the messed-up inputs on the controller is to run games through steam and use their controller configs. I've tried rebinding all inputs using the windows control panel to even using the Xbox accessories app. Neither works, especially the accessories app since it can't even detect my controller even though it should. I just hope for a new firmware release that updates to the older version, since we can't roll back updates on controllers ourselves. I do enjoy being able to pair my controller really fast to windows with the new firmware update, but I'd rather have a working controller that I paid for.

I got my Series X in January, and never even took the included controller out of the box, because I own the Elite Series 2. When I dropped my Elite Series 2 (oof) recently, I sent it off for out-of-warranty repair, and pulled out the basic controller, still wrapped and taped in the foam bag in the box.

Stock controller worked fine for a few days, then there was a firmware update - recently, and I'm having intermittent disconnections all the time. It works fine when wired with a USB-A -> USB-C cable (I use the 9-foot one that comes with the Elite Series 2).

I decided, since I'd never had trouble with connectivity on the Elite Series 2, that I would buy a 2nd one, brand new of course. It 100% required me to update before proceeding.

Since I never had issues with the Series X and Elite Series 2, I wasn't aware of the known connectivity issues until the basic controller started intermittently dropping connection.. After searching, I saw that there were a ton of articles from way back in January, including Microsoft acknowledging the problem and releasing a firmware update in March...

Yet here I am with a freshly unwrapped Series X controller AND a brand new, (delivered Sept. 7th) SECOND $180 Elite Series 2 controller, and BOTH are cutting out intermittently..

-Sitting Less than 7 feet from my console

-I keep my batteries charged - both the Elite's internal, and the Enelooph Pro AA rechargeables that I use in the regular controller.

-As I mentioned, latest firmware on controller

-Of course, latest firmware/software on Series X console

-Both controllers work fine when wired.

-Already performed hard power cycle on the controller as well as the console.

-1st Elite (the one being repaired) never had issues until I dropped it - but it was never exposed to that new firmware)

-That's 8 months I used my 1st Elite Series 2 with the Series X and no problems.

It seems to me that the original intermittent connectivity issues were never resolved.