Problem with Shortcut dialogue

Recently there have been a number of workstations in my company that are
displaying a "Missing Shortcut" box indicating that Windows is searching for
example.exe. After a few seconds to as long as about 30 seconds a "Problem
with Shortcut" box shows indicating that the "Nearest match..." was found and
asking to Fix It, Delete It, or Cancel.

The path that is shown in the "Problem with Shortcut" dialogue box is the
exact path to the executable that is already present when you review the
properties of the shortcut itself. The properties of the shortcut have not
been changed and the exe file has not moved or changed. If you click Fix It,
then everything is fine after that. Users only have read/execute access to
the shortcut so for them they must click Fix It everytime they use the
program until an admin logs in and clicks Fix It.

Does anyone have a clue as to what could be causing this issue and how this
can be resolved?

I have also seen this issue when I run an SMS Installer package I created
that creates a shortcut to an executable on a shared server folder. I know
the package is good because it was created before we started seeing this
issue and has worked fine on a number of other workstations.

Anyone have any ideas, thoughts, tips, pointer, anything about this problem?

"Greg" wrote:

> Recently there have been a number of workstations in my company that are
> displaying a "Missing Shortcut" box indicating that Windows is searching for
> example.exe. After a few seconds to as long as about 30 seconds a "Problem
> with Shortcut" box shows indicating that the "Nearest match..." was found and
> asking to Fix It, Delete It, or Cancel.
>
> The path that is shown in the "Problem with Shortcut" dialogue box is the
> exact path to the executable that is already present when you review the
> properties of the shortcut itself. The properties of the shortcut have not
> been changed and the exe file has not moved or changed. If you click Fix It,
> then everything is fine after that. Users only have read/execute access to
> the shortcut so for them they must click Fix It everytime they use the
> program until an admin logs in and clicks Fix It.
>
> Does anyone have a clue as to what could be causing this issue and how this
> can be resolved?
>
> I have also seen this issue when I run an SMS Installer package I created
> that creates a shortcut to an executable on a shared server folder. I know
> the package is good because it was created before we started seeing this
> issue and has worked fine on a number of other workstations.