Most machines don't have it System32 by default. Even if they're a dev machine with Visual Studio installed. I had to manually copy it for Symbol Server calls to be attempted. These calls can be observed by running MTuner under a debugger where they appear in the Output window.
Ahh I now see that you deploy symsrv.dll in the release. So it's really just a local build environment issue. So maybe close will not fix. Doesn't seem like very many people try to build MTuner from source.
A super obnoxious fact about Windows is that symbol server related calls will fail unless
symsrv.dll
is present in either the running application directory or inSystem32
. See remarks here: https://learn.microsoft.com/en-us/visualstudio/debugger/debug-interface-access/idiadatasource-loaddataforexe?view=vs-2022Most machines don't have it
System32
by default. Even if they're a dev machine with Visual Studio installed. I had to manually copy it for Symbol Server calls to be attempted. These calls can be observed by running MTuner under a debugger where they appear in the Output window.