This is something I’ve never seen before in the decade or more that I’ve had battle.net installed. Today the Battle.net update agent keeps randomly popping up the Windows UAC dialog because it wants to make changes to my computer. It’s happened on (I think) four occasions and each time it asks (and I refuse) twice.
I have auto-updates off, and I haven’t tried starting a game or doing anything with the Launcher (it’s just sitting there in the background).
I’ve seen it ask for permissions when I’m actually doing something like an update on install, but never just randomly out of the blue like this. So any idea why it’s decided today is the day to randomly start trying to do updates that require UAC permissions?
The only thing that comes to mind for me, is that I ran SeaTools yesterday and it changed the security state on a few of my drives. However, BNet is not installed on one of those drives.
The reason I refused is like I said. I didn’t choose to do something. It randomly popped up the UAC messages with zero interaction. It’s never done that for me in a decade. They’ve always been related to me actually triggering something in the past. So I was unwilling to click them.
Okay. Well, the app does auto update itself without requiring your intervention. Usually it has a tell-tale green logo notifying you of an update in the upper left corner of the menu.
But it can also trigger this “allow” request if it happens to check a game for an update. Now, mine are set to not auto-update, I do them manually, but its the same process. The app however does not have that option, it will check and apply updates automatically regardless of the game settings.
Some things it updates require permission. Its perfectly normal is my point. But you can do whatever you feel you need to do.
Like I said , in the ten plus years of using BNet it’s never popped up the UAC dialog unexpectedly. That’s the whole reason I have concerns. There were no bnet updates (at least no “green arrow” ones) or game updates. So I find it weird.
Thanks for that. I had a bit of a read and it sounds useful. Some of it doesn’t apply (I’m still on Windows 10) but I’m bookmarking it in case the problem persists.