Why doesn’t a Windows shortcut work if the executable is changed?

Damir Imamovic February 22, 2012

we have one executable file on a fileserver share where the shortcut is created on the user’s desktop. The Desktop and My Documents folders are redirected to another file share on file server.

If Offline Files is On and we change this executable file by replacing it with a new version, the shortcut doesn’t work anymore. This wasn’t a case before and we don’t know why this started to happen. We know that something is changed and for some reason this shortcut can’t open up the new executable file it is pointing to.

  1. Anonymous
    February 22, 2012 at 11:34 am

    perhaps  give permission back to users so the files will still work?

    When you redirect the Documents folder on a Windows Vista-based or Windows 7-based computer to a network share, the folder name unexpectedly changes back to Documents

    Implementing Folder Redirection with Group Policy

  2. Damir Imamovic
    February 22, 2012 at 10:47 am

    Bruce Epper: No
    @FIDELIS: :-). Nice, but what about other 299 desktops. We are doing changes like every 2-3 days adding new reports etc ...This was working for a years without issue and started happening on few sites we are running, but not connected to each other. 

  3. Bruce Epper
    February 22, 2012 at 8:46 am

    Have there been changes to Foldier Redirection with regard to the directory on the fileserver where your executable resides?

    February 22, 2012 at 2:22 am

    Hello, I would just create another folder in the share or another share.  In this new folder/share, save the new .exe file.  Once new .exe file is saved there, create a new shortcut.  Copy this new shortcut to users desktop.