DualShock 4 and DualSense battery both plummet on PC via Bluetooth

[CaseyDog]

Despite being fine wirelessly on my PS5, both my DS4 and DualSense die after about an hour of bluetooth connection to Windows 10, with DS4Windows showing them as draining and then dead accordingly. Is this normal? They're supposed to last like eight hours, right? I even have their lightbars disabled.

 

[tabzer]

It's not normal. You say that they coincidently stop working. Do you mean that both of them stop working at the same time? If so, then it's probably not the battery charge that is the issue. More likely a communication fault.

 

[CaseyDog]

Sorry, I worded that poorly. I meant either controller (not connected at the same time as each other) disconnects from Windows and needs to be recharged in accordance to DS4Windows displaying them as dead,

 

[tabzer]

Sorry, I worded that poorly. I meant either controller (not connected at the same time as each other) disconnects from Windows and needs to be recharged in accordance to DS4Windows displaying them as dead,

Okay. What version of DS4Windows do you have? I'd recommend trying a fresh reinstall with new drivers and updated software to see if that fixes things. Newest version is 3.0.18

 

[CaseyDog]

Drivers for what exactly?

 

[tabzer]

Drivers for what exactly?

https://ds4-windows.com/drivers/

What version of ds4windows do you have installed?

 

[CaseyDog]

I updated them all and that seems to've fixed it, thanks a tonne!

 

[tabzer]

I updated them all and that seems to've fixed it, thanks a tonne!

Thanks for the update! Feel free to post if anything changes. Glad it seems to be working now.

 

[Alesh_Silva]

I updated them all and that seems to've fixed it, thanks a tonne!

Is the battery normal right now? What exactly did you update aside from DS4WINDOWS?

 

[KKordeth]

Is the battery normal right now? What exactly did you update aside from DS4WINDOWS?

Yeah, I am seeing some poor battery life from my PS5 controller when using it to bluetooth to the PC.
I can't pinpoint when it was better, but v3.3.3 seems to be harsh.