Every 48 hours I'm prompted to re-enter my BN password

Is this supposed to be happening? I’ve got BN set to remember my login and keep me logged in. And yet just about every other day I get a message when I wake my system that there was an error logging me in or it can’t connect to BN or something else and prompts me for my password again. I enter it again and the spinny thing just spins until I close the window, and that’s when BN finally logs me in. I’ve let that thing spin for several minutes and it’s never timed out or anything. Now I just close it as soon as it starts.

What’s the point of the “Keep me logged in” option if I’m having to do this every other day after I wake my system? I only have BN on one system and there’s no record of any other systems using my account.

1 Like

Are you running Bnet on Windows? Do you have security apps or a VPN?

It’s running on Windows 11. No security apps other than Windows Defender and no VPN.

And now since I’ve posted this topic it’s doing it every single time after the system wakes. Doesn’t even wait the 48 hours anymore.

This started happening to me last night as well. Same thing only windows defender and no VPN. Please help fix this. Hate putting in a PW everytime

I recommend submitting this as a Desktop App Bug Report

Not able to recreate it myself.

Hello - I am having this same problem. I have tried uninstalling and reinstalling battle.net and that did not fix it. I have also tried using the ‘allow multiple instances of battlenet’ setting. It is very frustrating to have to re-enter my password every day - I’m about to look for a scripted solution. :frowning:

It’s been two weeks since I originally posted this. And I don’t know if BN did something on the backend or pushed out a patch, but, I kid you not, the problem stopped within 24 hours of my last post. So, about 12 days ago. I haven’t had to put in my password a single time since then. BN’s automatically logged me in just like I would expect it to. But then again, I’ve barely actually played any BN games in that timeframe as well, so who knows.

If Blizzard did something to fix this, then bravo on them. If not, then I’m really super-curious as to why this just stopped being a problem after like months upon months of it doing it consistently every few days.