>This issue has been resolved and I wanted to share with you how (in case anybody come across a similar situation). The folder where the application was installed was corrupted (general term as we don't know exactly how). I could not get into the Share properties of the folder, neither could the customer IT admin person. So last night he shutdown the share of this folder. Then I created a new folder and copied all files from the old/corrupted folder. He then set the share of the newly created folder under that same name as was the old share. And everything works without user being prompted for .FXP file and without the need for having the .FXP file as a parameter in the desktop shortcut properties.

If that's any consolation, I've seen a case how such a condition may arise.

I wanted to apply rights to a certain user to a folder (namely the NT Service, so my SQL could read backups from the places where I keep them, not in the unreadable structure where it wants to keep them), but then nobody told the filesystem that inheritance was invented. So it went about applying these rights to every file under that branch of the directory tree, and would take very long time (no progress indicator) and would eventually confess that it doesn't know how to finish. Then I'd cancel the process (because it wouldn't continue anyway), and it would warn me that the policy records (or whatever) were left in an inconsistent state bla bla.

Solution was even more drastic: killed W10 and reinstalled W7, forbid updates.