I’ve sent a report and apparently the issue is fixed in the 6000.1.0a2 and will be fixed in the next Unity release.
Link to the issue tracker : https://issuetracker.unity3d.com/issues/input-is-not-received-after-some-time-when-using-a-gamepad
Thank you for notifying. Btw I’m not use multiple controllers, only wireless switch pro controller. Hope it gets fixed… 
Hey everyone,
We have a possible fix for this, which will be included in a new Unity Editor patch version, Unity 6000.0.26f, to be more precise.
This version should be released between November 6 and 8. Please let us know if you’re still experiencing this problem once this release comes out!
Thanks! It’s like you read my mind. I was just thinking “I wonder what the timeframe for this update is looking like.”
Looking forward to it. Liking Unity 6 quite a bit otherwise.
Just wanted to mention we have a shipped Early Access game that some users are reporting this issue (gamepad stops responding), so glad to see a fix is on the way…
i tried this on a completely new project using the new input system with Unity 6000.0.25f:
when i close the built game, my game.exe process isnt closing in the task manager background processes. wonder if anyone else has this? if i use the old input system i dont have that.
also tried the 6000.1.0a2 and have the issue there too.
dont have it in 2022.3.51f.
For what it’s worth I still have the issue. It is locked showing me having an xbox controller plugged in. Never seems to recognize my keyboards and swap back over. I’m gonna try just starting a new project and see if it happens here too.
edit #2:
Ok I was an idiot on edit 1, I had it paused. SO!
It’s definitely registering my keyboard, but my character is not moving.
So here’s our editor settings, for lets just say W.
Unfortunately when we come over to our Player Input:
We can see it still thinks an xbox controller is connected. However there is none currently connected, all of my controllers are unconnected and turned off. None were on when Unity opened either.
So here is our move which we’d expect to see triggered by W (or ASD). However…
This never is hit by pressing those keys. But if I turn on a controller and move around the joystick it works.
So I know my input systems are all at least somewhat setup correctly. And they worked flawlessly in 2024.
I hope this helps…maybe give some ideas on what might be up?
(PS The 6000.1 also doesn’t work)
I’ve since moved the affected project I was working on to Rewired to get around the issue, but in Unity 6000.0.26f1 I tested the bugged project that I submitted using the Unity Input System. The bug I was encountering seems to be fixed 
Thanks for confirming Glad the nasty bug you had to face is now fixed!
@Oafkad that sounds like a different problem. Could you report it as bug in Help - Report A Bug, from the Editor? Let me know what’s the ID of the bug so I can track it with QA. Thanks!
Gotcha! CASE IN-88786.
Reported with all the details I could think of and a link back to this chat.
Part of my plan is to make a brand new project and see if I can just rebuild things. Bit annoying but I don’t really care to revert back to 2024 lol.
Edit: Worth noting, this does NOT happen with a new project. So its some lingering problem from the upgrade that isn’t eliminated with a library deletion. Peculiar!
Are there any new updates? This fix will be critical for my Unity game.