WoW Voice Proxy Problems

[Flumpumpel]

Did someone else experienced problems with multiple Voice Proxy Tasks during Classic Stress Test ?

I had sometimes up to 10 of those Tasks open and each of them was using about 9% cpu load.
In one case i was 15min afk, WoW and Bnet were closed before going afk. As i went back on my PC i realized a pretty high cpu load for an idle situation and looked into Task Manager where i found this
https://www.bilder-upload.eu/bild-edb510-1565515577.jpg.htmlhttps://www.dual-boxing.com/attachment.php?attachmentid=2198&stc=1

[nodoze]

My WoW clients are still open (just DCed) and I checked my task manager and don't see Voice Proxy tasks anywhere.

Right now they just say 'World of Warcraft' & I don't remember seeing 'World of Warcraft Voice Proxy' anywhere.

When having 5 clients open in the stress test this weekend I don't remember seeing any Voice Proxy tasks anywhere but I never had any CPU load issues so I really never had a need to look (I run a 16core i7-6900K with 128GB of RAM so maybe that is why).

Maybe the Voice Proxy can be turned off somewhere. If I can remember to check once I get what names reserved I will try to circle back after and let you know what I see.

[JohnGabriel]

Are you loading WoW from the launcher?

In the retail version, you can safely delete WoWVoiceProxy.exe and BlizzardBrowser.exe from your /retail/utils/ folder. Many people have been doing that for privacy reasons as it completely disables voice chat.

I would assume you can do the same for Classic version.

[Flumpumpel]

Thx for your replies.


Maybe the Voice Proxy can be turned off somewhere.
a few days ago i disabled the voice chat in the Bnet Parental Controls, which worked fine for wow retail. I no longer have any options to join a voice chat. In Task Manager the Voice Proxy still gets loaded but did not use any resources so far.


you can safely delete WoWVoiceProxy.exe and BlizzardBrowser.exe from your /retail/utils/ folder
This worked well, until i started the Launcher and everything got reinstalled. I guess thats why you asked this in first place :) . Usually i do not use the Launcher , just for updates and playing Diablo 3.

Can Addons in Classic use the Voice Proxy Interface and could cause these problems?

[Drakhoun]

Hi all,

i had the same issue. It caused major slow downs after some time.

I managed to fix it by deleting the voice proxy files in the game folder. Then as isboxer launches the team, i just kept killing the Blizzard Update Agent. It stopped the voice proxies from restarting.

[Quiding]

I had exact same problem, was especially annoying when I tried setting up UI and quitting/reopening the game a bunch of times and forgetting about it, would lock up the computer for a time.

[JohnGabriel]

I don't think the battle.net updater should launch every time you open a window through isBoxer.

It feels like you have the battle.net launcher open while your team is loading. Could that cause it? Maybe its just being minimized to the system tray, which is its default behavior.

[xHaplo]

Came across this issue myself while 5 boxing,
None of the suggested solutions worked for me, so ended up writing a small app that basically checks running processes every 10 secs and closes any Wow Voice Proxy processes it finds.



Source code and release available:
https://github.com/David-c0degeek/WowVoiceProxyKiller
(https://github.com/David-c0degeek/WowVoiceProxyKiller)
I kept it as simple as possible, really just a quick 1 min fix for it.
Feedback is more than welcome.

[nodoze]

Came across this issue myself while 5 boxing,
None of the suggested solutions worked for me, so ended up writing a small app that basically checks running processes every 10 secs and closes any Wow Voice Proxy processes it finds.



Source code and release available:
https://github.com/David-c0degeek/WowVoiceProxyKiller
(https://github.com/David-c0degeek/WowVoiceProxyKiller)
I kept it as simple as possible, really just a quick 1 min fix for it.
Feedback is more than welcome.The following is how I manage it via firewall:

https://www.dual-boxing.com/threads/56245-Addressing-WowVoiceProxy-exe-issues

[xHaplo]

The following is how I manage it via firewall:

https://www.dual-boxing.com/threads/56245-Addressing-WowVoiceProxy-exe-issues

Yup, this works but depends on the firewall solution / software and sometimes fails (I still get rogue WowVoiceProxy instances running even with the firewall rule)
That's why I made the small simple app, but ofc, if the firewall you use does the job, its a better solution :)

[Moorea]

WowOpenBox in 3.5 now auto kills the voice proxy for you
https://wowopenbox.org/


edit: it is only able to kill left over ones from previous runs, not ones attached to currently running wow... working on a fix

edit2: fixed in v3.5.3!