I posted the other day about a similar problem, but in my company, we share AQTime licenses, and some developers can run from inside AQTime, and others have to attach to the running app they are instrumenting. Since we are supposed to all work eith the same tools and permissions, this is a conundrum. When AQTime fails to run the app from inside, the app appears in task manager, but is not running. The only correlation we have found so far between the working and not working AQTimes is that AQTime seems to work for the developeres who installed it ab out a year ago, and not for the recent installations, even though it is the same version for everybody. One significant thing that happened in between is that our company installed some "privilege management software", but it was installed for everybody and with the same privileges. So currently,we are at a loss to understand the difference.
We just tried with a barebone WIn32 application (the default project in VisualStudio 2015). When AQTime fails to run, it stops loading dlls after ntdll.dll (the first dll loaded after the executable file under scrutiny) . When it runs OK, it loads about 3 dozen dlls after ntdll.dll
