Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm trying to understand a problem I have encountered several times now (i have a workaround but it bugs the hell out of me).

Basic problem is that a given .exe file runs fine or not depending on how its started:

  • works if you do it graphically (click to folder, dubbelclick the .exe)

  • does not work if you do it from dos (cd to folder, execute the exe)

  • works from dos if you create a shortcut to the exe and execute the lnk file. When the program doesnt run it complains about not being able to find dll's.

  • works if you run it with the path to the exe from the runas dialog

I've seen this same problem before with different programs on windows-xp, but the one I currently ran into it with is 'smart response' downloaded from

Is anyone able to shed a light on the root cause of this?

share|improve this question

Does it work if you change into the applications directory on the command prompt before starting it?

The program probably tries to load some additional modules (DLLs) without specifying where to look for them. So they have to be somewhere windows can find them automatically: in the system PATH or in the current directory.

When you start by double clicking the exe (or starting a shortcut) the system usually sets the current directory to the folder the lives in...

share|improve this answer
No, changing the directory to the application folder, and then executing the .exe does not work. – cobaco May 2 '11 at 9:52

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.