in one case, farr tells windows to run the shortcut -- which windows should figure out how to decode and execute.
in the other case, farr reads the shortcut info inside it and executes the program itself.
i'm guessing that some firewalls are blocking one of these modes on people's machines where the problem is occurring, but it could be something else too i suppose..