>>This is an old thread but I wanted to update it. For a few customers where this phenomena is happening (requiring to select Applicatin.fxp when starting Application.exe), the temporary solution is to add the Application.fxp as a parameter to the Application.exe in the desktop shortcut property. Therefore the shortcut target says "Application.exe Application.fxp" (where Application is the name of the .EXE). But what is "strange" (at least to me) is that the application runs under the version of the Application.fxp. That is, if I update Application.exe to any new version, the run-time shows the version of Application.fxp (done when copying Application.exe to Application.fxp). Thus, I have to remember, whenever updating the application, to update (re-copy) the Application.fxp.
>
>In my experience, this likely means Windows Security Essentials or some other anti-virus program is blocking the Application.exe application. Unblock this to prevent this issue.
>
>Doug

I will ask the IT to check the WSE on the desktops that have this issue. Too bad I don't have Windows Security Essentials on my PC to simulate the situation.
Thank you for your suggestion.