Voice Proxy

Every time I log into the game I get an error for the WoWVoiceProxy.

This application has encountered a critial error:

ERROR #132 (0x85100084) Fatal exception!

Program C:
Program Files (x86)\World of Warcraft_retail_\Utils\WowVoiceProxy.exe
ProcessID: 20020
ThreadID: 19480
Exception: ACCESS_VIOLATION

The Instructions at “0x00007ffe2d801be0” referenced memory at “0x00007ffe2c506908”.
The memory could not be “written”.

The in-game chat says “lost connection to the voice chat service:(VoiceError: 17)”

Been going on for a few months now. It does it multiple times when logging into a new character. Does it with all addons disabled.

Reading through seems this was a major issue back in 2019 after 8.1 was launched. Ive yet to find a fix. No security software installed, fresh wow install, fresh bnet install, deleted my wtf folder, deleted my addons folder. Still have the same issue.

Hey there,

Definitely odd that WowVoiceProxy.exe would be crashing in that way. Could it be that WowVoiceProxy.exe is blocked by the Windows Firewall and potentially causing it to crash when loading up?

You might try defaulting the Windows Firewall settings and then test again.

If it’s still happening, perhaps try rebooting using Selective Startup to see if it happens with no extra processes or services running in the background. This might help identify if there’s something else on the system that’s conflicting with it somehow.

  1. Press Windows Key+R.
  2. Type msconfig and press Enter.
  3. Select Selective startup and uncheck Load startup items.
  4. Select the Services tab.
  5. Check Hide all Microsoft services.
    *Note: Skipping this step may prevent your computer from rebooting correctly.
  6. Click Disable all.
  7. Click Apply then click OK.
  8. Click Restart.

Sorry for the long delay. I did try the steps above and still get the issue. I have done this with the firewall totally disabled, as well. With all addons disabled. And a fresh install of battle.net and for WoW. It doesn’t do it every time I log in but about 90% of the time. And it will do it when each character logs in.

Hey again,

If it’s crashing even after a fresh install that makes me think there might be something else on the system that is conflicting with the voiceproxy, but hard to say exactly what since this isn’t a common problem we see happen.

I’d probably recommend submitting a ticket (use the Contact Us button) and a Technical Specialist can look over your DXDIAG and MSINFO files to see if anything else stands out as to what might be causing it.

you can disable it by going to where wow is installed - World of Warcraft - retail - UTILS - WowVoiceProxy.exe rename it to WowVoiceProxy.exe.bak… then use WoW.exe from the retail folder to bypass the Battle.net Launcher or it will put a new one in … you will get a error after login saying “Can’t connect to a voice chat server right now . please try again. (VoiceError: 14)” it’s safe to ignore the error because the game runs fine without WowVoiceProxy.exe running

1 Like

Ive sent a ticket in with my DXDIAG and MSinfo files and the description of whats going on. Hopefully I can get this issue resolved.

So I put out the ticket and put what I have done to try to fix the issue and I get a generic response with the first thing asking me to disable my addons… The first thing I listed when I said “this is what Ive tried” what disabling all addons and freshly installing WoW. Can I get an actual response or shall I go watch “Wall E” and see if I get a better response from that robot.

The bottom of the ticket response will have a link to re-open the ticket.

A GM answering a new ticket will almost always respond to a ticket initally with a canned response for suggested self-help actions and I understand these actually work often enough to save a great deal of time hand-holding a customer through self-help.

2 Likes

I got a real response today and it appears it was uxthemesignaturebypass.dll. Its a program that is used to heavily modify the windows theme by changing the windows 10 coding. No idea why that would conflict with the voiceproxy but it appears it does. This can be marked as resolved.

1 Like

Hey again Eon,

Thanks for following-up and I’m glad to hear that Support was able to identify what was causing the crash. Definitely an odd conflict since it was be crashing the WowVoiceProxy but not WoW itself.

I went ahead and marked the post as a solution for you. :slight_smile:

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.