#208 Equalizer APO Configurator and Editor won't launch

[Nicholas Decker]

I've had Equalizer APO installed for a while and it worked fine. I recently upgraded my CPU/mobo and had to reinstall all my drivers. After this, Configurator and Editor won't launch. When I attempt to open the programs, nothing even pops up. If I try to open Configurator through Peace, a window flashes for a split second and disappears.

I've tried reinstalling Equalizer APO and Peace multiple times, checked all my audio devices to make sure nothing is interfering, deleted all registry entries between reinstalls and none of it seems to work.

Is there anything short of a fresh install of Windows 10 that I can try to fix this?

[Peter Verbeek]

Commonly some firewall/antivirus software is blocking the startup. Usually caused by the fact that the Configurator and Configuration Editor try to access the Windows registry. So at least the Configurator needs to have the highest rights (administrator rights) to run. Btw. usually Peace doesn't need that much rights but it may be needed in your case.

Just to be sure: Is Equalizer APO installed in the proper folder, c:\program files\equalizerapo? Some firewall/antivirus app may also block this entire folder. So you could check this too.

[Alesk Nand]

I'm banging mi head a lot over this, the same issue mentioned over and over around the page.
Configurator.exe and Editor.exe both crash on launch after an unfortunate uninstall->reinstall.

Faulting application name: Configurator.exe, version: 0.0.0.0, time stamp: 0x5cfe3d2a
Faulting module name: Configurator.exe, version: 0.0.0.0, time stamp: 0x5cfe3d2a
Exception code: 0xc0000005
Fault offset: 0x00000000000126d4
Faulting process ID: 0x23fc
Faulting application start time: 0x01d857010f79d14c
Faulting application path: C:\Program Files\EqualizerAPO\Configurator.exe
Faulting module path: C:\Program Files\EqualizerAPO\Configurator.exe
Report ID: ac04c299-0632-4d81-9701-d493ec94c92d
Faulting package full name: 
Faulting package-relative application ID: 

Edition Windows 10 Pro
Version 21H2
Installed on    ‎25/‎02/‎2022
OS build    19044.1645
Experience  Windows Feature Experience Pack 120.2212.4170.0

Things I tried:

Deleting leftover files in the disk

1. C:\Program Files\EqualizerAPO
2. Everything mentioning EqualizerAPO in C:\\ (Revo Uninstaller)

Deleting registry keys(and subkeys) after EqualizerAPO uninstall

1. Computer\HKEY_LOCAL_MACHINE\SOFTWARE\EqualizerAPO
2. Computer\HKEY_CURRENT_USER\SOFTWARE\EqualizerAPO
3. Everything mentioning EqualizerAPO in the registry (Revo Uninstaller + manual search)

No antimalware interference detected

I'm using only Windows Security, it has been disabled for precaution.

Uninstalling-reinstalling realtek audio drivers, other audio devices, vendor audio software

The only audio peripheral I've ever used EqualizerAPO on are my bluetooth headphones (AutoEQ). They can easily be removed from the Windows Settings or Device Manager.
For precaution, I've also removed them from the driver store with Driver Store Explorer.

Inspecting log (also with trace enabled)

Docs say it's written in C:\Windows\ServiceProfiles\LocalService\AppData\Local\Temp\EqualizerAPO.log. Configurator.exe crashes too soon for anything to be written. Crash is reported in the Windows Event Viewer tho.

Running Configurator.exe with windbg

Nothing caught my attention, I'm a programmer but I've never programmed under windows or reversed.

Attempt to debug Configurator.exe from source (?)

Developer docs say Visual Studio 2013 is required to open the project. I can't afford to install such an old version on my machine.

Deleting Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\MMDevices\Audio\Render

Developer docs explain how it uses the FxProperties key to register the APO. Original values are backed up in HKEY_LOCAL_MACHINE\SOFTWARE\EqualizerAPO\Child APOs. In a desperate attempt I deleted the entire key (with backup). Windows recreated it on reboot, Configurator.exe is still crashing.

Running installer and/or Configurator.exe as TrustedInstaller/System/Current User with all privileges with NSudo

To rule out potential permission issues, I've tried running executables as more powerful users.

Many, many combinations of all of the above, in different orders, with one or more system reboot between each steep

I also have Windows' fast startup disabled.

Configurator.exe works in another PC of mine, and also inside a sandbox

I've compared before and after registry states with RegistryChangesView. They all run Windows Security with the same settings (managed by a tool, for consistency).

I don't understand what's wrong with it, I tried ¯_(ツ)_/¯

I consider my Windows installation quite young and well kept (no ..exotic customizations?). I can't afford a full reinstall. I'd suggest a better error handling system, the page is littered with the same crash issue and no information available except guesses.
AutoEQ really improved my listening experience while it lasted!

[Alesk Nand]

I took advantage of the migration to a more humane toolchain (VS2019) to finally see with my own eyes what the hell was going on here.
After some major hiccups, I've found that the codebase references the startup folder and assumes it to exist. Being a syscall, someone better versed in Windows and debugging might've caught that easily, without sources.

So, recreating the startup folder in the start menu fixed the issue for me.

[Peter Verbeek]

Exception code 0xc0000005 seems to suggest it has to do with having not enough rights. That could be a few things, I guess:

1. Not enough rights to change the "protected audio" state of Windows (which must done in the registry to get reroute the audio stream from audio devices through the Equalizer APO engine).
2. Not enough rights to access the Windows registry.
3. Not enough rights to run the Editor.exe and Configurator.exe.

Mostly this is because of an antivirus/firewall app preventing the access to the registry or Equalizer APO folder. It's a bit weird that Equalizer APO doesn't have enough access to its own folder but it does happen, especially on the 'config.txt' file. A security app may sandbox quite a lot.

And somehow the same happens with some particular Windows 10 updates.

Also some users have issues with Equalizer APO 1.2.1 so they revert to 1.1.2.

One thing needs to be done very often: restarting. After Equalizer APO is uninstalled the computer must be restarted. After changing something in the registry the computer must be restarted. After installing Equalizer APO the computer must be restarted. So when in doubt, restart. Some issues were resolved simply by restarting a lot after some change is made. It's weird of course. So not easy to pinpoint the why and how.

[Alesk Nand]

I've updated my post with additional info I had forgotten, specifically regarding permission issues and antimalware observations.

[Peter Verbeek]

I can imagine it's annoying that you can't find an easy fix.

I also saw some post here on this forum saying that an empty having or adding HKEY_LOCAL_MACHINE\SOFTWARE\EqualizerAPO\Child APOs key did the trick. I don't know why but it is suggested by the developer at least once. I only know that this key is used to back up the audio device routings before the Configurator reroutes the audio streams.

[Alesk Nand]

I read that too in some of the dozes pages I've read (and also in the dev docs, as you mentioned). I tried that also, forgot to mention. 🤣

I can imagine it's annoying that you can't find an easy fix.

Yeah, you can definitely say I'm annoyed with the tool, but above all I'm thankful the dev spent his personal time to create this, for free!
I'm documenting it in the best detail I can mostly for future reference/debugging

[Peter Verbeek]

Yes, documenting is good way to go.

Unfortunately the dev isn't very active any longer. But his work is amazing. If Equalizer APO didn't exist the Peace equalizer didn't. And I wasn't giving the support for both projects :)