ContributionsMost RecentMost LikesSolutionsRe: Application does not start because of aqReporter.dllThat did the trick. I uninstalled AQTime. Rolled back the registry teaks. Installed again AQTime and now it works fine. Thanks for your help. rodolfoRe: Application does not start because of aqReporter.dllThat is correct. Long story short, when windows started using the "program files (x86)" folder for 32 bit apps it caused us some trouble in our developer's VMs so we tweaked the registry to make windows install all apps under the regular "program files" folder no matter if they are 32 or 64 bits. The only thing I have under the Program Files (x86) folder is what comes with windows out of the box. Btw, if you want to do a webex sometime to take a look at this problem just let me know. regards, rodolfoRe: Application does not start because of aqReporter.dllI installed it in another vm with the same configuration (Win2003 x64, etc) and I get the same error. rodolfoRe: Application does not start because of aqReporter.dllI had the 64bit version. Just to be sure I re-installed it and I still get the error. I'm installing aqtime650x64.exe rodolfoRe: Application does not start because of aqReporter.dllHi Allen, Isn't that right? I have a 64bit Windows. rodolfoRe: Application does not start because of aqReporter.dllHere are the files. I have everything installed under the program files folder. C:\Program Files\Automated QA\AQtime 6\Bin\aqReporter.dll --> 1.50.411.4 RodolfoRe: Application does not start because of aqReporter.dllHey Allen, I tried those steps and it didn't work. I still get the error as soon as I run the application. Let me know if you need more information to find the solution. Thanks, rodolfoApplication does not start because of aqReporter.dllWhen I run AQTime 6 I get the following error: This application has failed to start because aqReported.dll was not found. Re-installing the application may fix this problem. What I've tried so far is: 1. Check the windows path and the AQTime bin folder is there. 2. Copying the dll to the system32 and syswow64 folders. 3. Uninstalling and installing using the latest version. You can see in the attached screenshot that the file is several places in the hard drive as I also have installed Build Studio and DevTeam Client which both work with no problem. My configuration: Virtual Machine running on VMWare Esx 4 Windows Server 2003 R2 64 Bits Any ideas? Thanks, rodolfo