Problems detected for one device
A system-wide equalizer for Windows 7 / 8 / 8.1 / 10 / 11
Brought to you by:
jthedering
Hi, I have been trying to install equalizer apo correctly by watching a lot of videos but none of the tickets, people thinking or trying to find out what the problem i have might be cannot find out. I asked chatgpt i did resets i did everything possible and i still get the problems detected for one device and access denied when i select my playback device as well also i changed a lot of headsets and still same problem im not sure what to do and im lost pls help me (i contacted windows support and they said its not a windows security problem)
According to Gemini AI this can be one of 4 things:
A 5th isn't mentioned: An anti-malware/firewall/registry monitoring app locking the Windows registry. But this one is rarely the case accept for some overactive registry monitoring app.
All 5 aren't likely but I guess it's one of those.
Btw. Check if Equalizer APO is installed in c:\program files\equalizerapo. Installing it in another folder may cause issues.
Its none of these problems i already have voice mod and voice meter installed on my PC also i changed so many headsets so its not a software issue and eq apo causes problems when in device selector. the access is denied message only pops up when i choose my playback device but when i do my capture device it only says problems detected for one device i also checked my exclusive mode problem and its all where it needs to be and im adding to the fact that access is denied is also an issue
Unfortunately I don't know what else it could be. Btw. The developer isn't very active so we can't ask him, that is if he knows the problem in the first place.
So Equalizer APO is installed in c:\program files\equalizerapo?
What I don't get is that "Access denied" refers to a simple initialization (the failing of) of the audio device by Equalizer APO, just like any other (audio) app would do when play sounds. And I guess you're running the Device Selector in administrative mode (right click menu -> run as administrator) so it should have plenty of rights.
correct, i even checked my mic perms and it lets apps take control of it this does not make any sense to me while i also contacted windows and they said its not a windows problem, apo is installed in c:\program files\equalizerapo i changed it to that and it still has the problem, i tried the audio enchancment and exclusive mode but that also is not solving it. as well as deleting all apps mic related for example voice mod and steelseries etc and the problem still occurs, not really sure what to do. + i tried ALL versions and some problem besides 1.3 which then says i dont have QT plugin and i should reinstall. the only thing that is weird is that when i tried wiring my voice mod to my eq apo caputure devices it actually said no problems detected and went through but it wasnt selected in config editor so i had to go back to selector and when i did and id the fail error but turned out positive with no problems then again it still did not show up, when i tried to listen through my voice with voice mod for example discord test mic the voice mod mic was acting up and insane HEAVY loud sounds like its broken.
Concerning the Voicemod, this is a virtual audio device which others have reporting that Equalizer APO won't work on or is difficult to get going on. But I don't know why that is. But it's probably another issue then the "Access denied" one. And I don't know why it doesn't show up in the Configurator Editor. It should as it's the same as a normal device.
Btw. Good thing that you've tried other Equalizer APO versions. Specially 1.1.2 ans 1.2.1 may work in some cases. Also, sometimes after a few restarts Equalizer APO suddenly starts working.
When talking about SteelSeries mics after unchecking the exclusive mode checkboxes, forcing the mic in shared mode, and after setting the mic audio enhancement to "Device Default Effects" (a.k.a. allowing APO's) it should work if the test by the Device Selector is successful. But users have reported that SteelSeries devices are difficult to get Equalizer APO going.
Another issue can be a new Windows update when having the "Get latest updates as soon ..." enabled or worse the Windows Insider Programme enabled. But since Windows 11 is already matured this isn't often no longer the cause, well unless 26H2 presents an issue. I still need to install that one.
I did multiple restarts, multiple reinstallations and the problem persists. anytime the mic is connected in anyway to eq apo the problem will always be there
What a bummer. Sorry that I'm not much of an assistance.
No problem i will let you know if i find the fix
Last edit: Nathan Smith 5 days ago
Thanks Nathan. Good luck.
I found a fix for the headset issue when it said "access is denied" you have to press win + r and type mmsys.cpl and go on playback click on your headset and check exclusive mode but issue presists with the capture device
Hello peter, i fixed the device selector part but my apo stil does not proccess my mic
Last edit: Nathan Smith 5 days ago
Well, that's great that you have found a solution for this nasty "access denied" issue. It looks like that the Device Selector wants to have exclusive access to a device for testing it. But that makes no sense as any APO (audio processing object) is bypassed in this WASAPI exclusive mode. Or did you uncheck the exclusive mode check boxes?
Getting Equalizer APO going on a mic can sometime be pretty difficult. The usual suspects are:
Hello, I have offically found the fix here is the solutions for all people who dont know yet. if you get the problems detetced for one device you need to open device manager go on EQ and APOS and delete voice clarity or uninstall, if the playback device shows access is denied you need to enbale exclusive mode on the headphones you use. if APO is not proccessing through your mic on discord youneed to go on settings voice settings click custom and turn off every noise suppresion setting and open advanced voice settings and turn off automatic gain control. thats the full fix for everyone who has the problem, NP.
Thanks for Nathan for figuring this all out.