Error code 0x00000005: Access is denied.

audiorouterdev / audio-router

Routes audio from programs to different audio devices.

GNU General Public License v3.0

3.51k stars 420 forks source link

Error code 0x00000005: Access is denied. #52

Open Youserhax opened 7 years ago

Youserhax commented 7 years ago

This is the first time this has popped up for me since I started using audio router. It doesn't seem to be a problem all across the board, but as of 6/30/2017 I keep getting this error message whenever I try to route the audio from google chrome.

andreluizgit commented 6 years ago

This error show for any app... In Windows 10 always show "acess is denied"

vctls commented 6 years ago

I get the same error when trying to route some programs. It also says «Router functionality not available.»

vernzimm commented 6 years ago

Same here... I'm guessing it's a Windows 10 update that broke something... Here is the only security update close to and earlier than OP's post that includes audio fixes....

https://support.microsoft.com/en-us/help/4020102

"Addressed issue where, after installing the Creators Update, audio output through external decoders no longer works."

"Addressed issue with high latency when using the Universal Windows Platform (UWP) MIDI API."

poochie89 commented 6 years ago

Any news on this? Having the same issue with all applications

IvnSoft commented 6 years ago

I got the same. However, i noted that you can still use it but in reverse :

Set default device to internal speakers (or whatever is your default)
Then route apps to the other non-default-devices.

This way it worked for me fine even in creators update.

mauriciabad commented 6 years ago

SOLVED:

Use a non Microsoft Store app (prevent 0x00000005 error)
Run "Audio Roter.exe" with compatibility mode for windows 7 (prevent duplication pending error)
Duplicate the audio from Default output to output A, then duplicate from output A to output B. (Don't check Soft routing)
(Follow the steps strictly or you will listen it in bad quality)

kyruzic commented 6 years ago

The suggested fix does not work. I still have this error when trying to route anything.