The program wowvoiceproxy.exe in the UTILS folder eats up too much CPU power. I don’t even use the voice program, but this thing loads everytime I start up Classic. It eats up more CPU power in the background than the WoW Classic client does itself.
Why does this have to load up when it isn’t being used? Why does it use up so much CPU processing constantly when it doesn’t in the WoW retail client? Please fix this or disable it, preferrably have it not even load if the player isn’t even using the voice service.
EDIT: The only way to fix this right now is to delete the wowvoiceproxy.exe file before loading the game, so it won’t load in the background.
4 Likes
Yeah as a 10 boxer it eating up 62% of my cpu is real cool blizzard.
1 Like
This is still happening. I have to rename the file / avoid using battlenet desktop app to mitigate this bug. Please give us the option to toggle the feature, or remove it from the classic client.
1 Like
You can exit bnet after you launch; then you can shut it off.
it doesn’t work like that, there is no “shutting it off”, you have to rename the file as Velium stated to sort of stop it from running, in fact any activiation of bnet will restore the file, even if you exit afterwards from it
on a stand alone instance of Wow, it’s not a big deal, but man it is a huge CPU hog once you start running multiple instances, what’s even more annoying is you might go to the extent of turning on Parental Controls to try and stop WoW Voice in any capacity but it won’t matter the game still runs this .exe in the background
this thread doesn’t really belong in the bug section though
Meh, I just shut it off and delete the file. I don’t use B.net more than once a month just for updates.
Yeah… this is actually so infuriating. Please fix your game and make this an easy option to turn off. No one using your crapping voice chat anyway.
1 Like
Renaming the file was the only way i could fix this. Bless.
How did you delete it? I wouldnt let me I had to rename the file as Velium suggested. That worked for us.
You can’t delete a file if it’s in memory, so you have to shut off the application (i.e., close battle.net). Then close WoW and delete the voiceproxy.exe file.
delete the file and make a directory called ‘WowVoiceProxy.exe’ in the utils subdirectory. voila banned file
2 Likes
followup. i noticed they changed bnet to literally check this file attributes and file type and remove any existing match that doesn’t have the intended target attributes (executable file, etc). it makes sense from a deployment perspective.
i’ve had to strip permissions on the entire directory and make it owned by another account to lock blizzard out of being able to update it (e.g. immutable). it’s becoming pretty stupid to the point I may make an AV ruleset to prevent bnet touching the file.
You can exit bnet and wow and just delete the file. Re-create your wowvoiceproxy.exe folder. Bnet will only delete this on update.
wow that’s why i have been lagging…!!
hilarious, these idiots restore WowVoiceProxy.exe by forcing an update whenever you start battlenet/try to launch wow.
-.-
Blitzkreig wtf
I know this a very late response, but you might try setting the file DACL to deny execute permissions instead of renaming.
This should have the benefit allowing agent to read & verify the file is present and in working order, but prevent actually starting it…even if it is replaced or updated.
This works on my system, but I haven’t verified whether the DACL is ever overwritten by update/integrity checks:
icacls WowVoiceProxy.exe /save "%userprofile%\WowVoiceProxyAclNormal.acl"
icacls WowVoiceProxy.exe /deny "%userdomain%\%username%":(x)
icacls WowVoiceProxy.exe /save "%userprofile%\WowVoiceProxyAclDeny.acl"
This first part stores the original DACL, sets deny execute (x), then stores that DACL.
I saved the files in %userprofile% as I know agent will periodically do some housecleaning and wipe out unrecognized files (syncthing settings, for example)
Once they’re saved, the permissions on file can be restored, back & forth like so:
icacls . /restore "%userprofile%\WowVoiceProxyAclNormal.acl"
icacls . /restore "%userprofile%\WowVoiceProxyAclDeny.acl"
Note you’ll need to be in the same folder as WowVoiceProxy.exe for the commands to work as listed, though I’m sure it would all work with absolute paths too.
…the /restore switch only takes a directory specifier as an argument…in this case, “.” represents the current directory.
4 Likes