[BUG] Can't open a shortcut for editing if the target file has been moved or deleted

[BenthamSoftwareServices]

Can't open a shortcut for editing if the target file has been moved or deleted, which is exactly what I want to do to reactivate an orphaned shortcut.

[ElektroStudios]

Hi.

Are you asking if it's possible to implement a new functionality that allows to recreate the shortcut file when selecting it from the recent file list, when the shortcut file it's no longer found on disk?.

Something like this? (functionality actually not available):

If that is not what you are asking, then please describe the steps to reproduce the error you've mentioned. For "target" do you mean the "Target" field in the editor?, this field?:

I've tried moving the target file that the shortcut file points to, then reopening the shortcut file, but can't reproduce the error you've mentioned. Please describe exactly the steps to reproduce, to avoid misinterpretations on my side.

Thanks for your report!

[BenthamSoftwareServices]

OK suppose I make a short-cut to a file (e.g. Word doc) or a folder and then I move that file or folder to a new location the short-cut fails to work and asks me if I want to remove it. I would like to be able to edit the short-cut a: to make it work again or b: just to be able to see the previous target path so I know where the target was originally located. But it seems that if the target of a short-cut has been moved, not only can't I view it's properties as the original target path is not displayed, but apps like your's, and others, won't open the short-cut for editing and just display an error message. The only way I have found to view the details of a target-less short-cut is to use a hex editor. I can then see the original target path Regards Steve Bennett Bentham Software Services Formerly trading as PCs, TBSU Ltd & Settle Computer Shop 07790 735822 Mobile & WhatsApp To request copies of your personal information held by Bentham IT Services and to request modification or restriction of its use please contact us. This e-mail and any attachments transmitted with it, including replies and forwarded copies subsequently transmitted, contains information which may be confidential and which may also be legally privileged. The content of this e-mail is for the exclusive use of the individual(s) or entity named above, if you are not the intended recipient, please note that any form of distribution, copying or use of this e-mail or the information in it is strictly prohibited and may be unlawful. If you have received this e-mail in error please reply to the sender at Bentham IT Services and then delete the e-mail immediately. Any views or opinions presented are solely those of the author, and may not necessarily represent those of Bentham IT Services.

…

------ Original Message ------ From "Elektro" ***@***.***> To "ElektroStudios/Easy-Link-File-Viewer" ***@***.***> Cc "Steven Bennett" ***@***.***>; "Author" ***@***.***> Date 26/03/2025 14:52:55 Subject Re: [ElektroStudios/Easy-Link-File-Viewer] [BUG] Can't open a shortcut for editing if the target file has been moved or deleted (Issue #15)

Hi. Are you asking if it's possible to recreate the shortcut file when selecting it from the recent file list, when the shortcut file it's no longer found on disk? Something like this?: fdsfsd.gif (view on web) <https://github.com/user-attachments/assets/e15ec9b0-9942-4b07-bb53-1ac97dcb194b> If that is not what you are asking, then please describe the steps to reproduce the error you've mentioned. For "target" do you mean the "Target" field in the editor?, this field?: WinSnap.02.jpg (view on web) <https://github.com/user-attachments/assets/fcc7b367-0c93-4acf-9604-91fc8197dd1c> I've tried moving the target file that the shortcut file points to, then reopening the shortcut file, but can't reproduce the error you've mentioned. Please describe exactly the steps to reproduce, to avoid misinterpretations on my side. Thanks for your report! — Reply to this email directly, view it on GitHub <#15 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BHE6XAGLBTI2NPJQVHF5C4L2WKWLPAVCNFSM6AAAAABZZ5RUVWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONJUG4YTINZQG4>. You are receiving this because you authored the thread.Message ID: ***@***.***> ElektroStudios ElektroStudios left a comment (ElektroStudios/Easy-Link-File-Viewer#15) <#15 (comment)> Hi. Are you asking if it's possible to recreate the shortcut file when selecting it from the recent file list, when the shortcut file it's no longer found on disk? Something like this?: fdsfsd.gif (view on web) <https://github.com/user-attachments/assets/e15ec9b0-9942-4b07-bb53-1ac97dcb194b> If that is not what you are asking, then please describe the steps to reproduce the error you've mentioned. For "target" do you mean the "Target" field in the editor?, this field?: WinSnap.02.jpg (view on web) <https://github.com/user-attachments/assets/fcc7b367-0c93-4acf-9604-91fc8197dd1c> I've tried moving the target file that the shortcut file points to, then reopening the shortcut file, but can't reproduce the error you've mentioned. Please describe exactly the steps to reproduce, to avoid misinterpretations on my side. Thanks for your report! — Reply to this email directly, view it on GitHub <#15 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BHE6XAGLBTI2NPJQVHF5C4L2WKWLPAVCNFSM6AAAAABZZ5RUVWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONJUG4YTINZQG4>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[ElektroStudios]

Apologies for the delay. Let me clarify that the program is designed to read shortcuts regardless of whether their target path currently exists.

In your case, however, it seems we’re dealing not with a standard shortcut, but with an Advertised Shortcut. These are linked to a specific ProductCode, which is hardcoded into the Windows Registry as part of an MSI (Microsoft Windows Installer) package installed on your system. That’s why the Target field appears greyed out and cannot be edited through the shortcut’s properties window in Windows Explorer.

Easy Link File Viewer, unlike many other tools, includes built-in—though limited—support for these special types of shortcuts.

It informs the end-user when this kind of shortcut is detected:

Easy-Link-File-Viewer/Source/UI/Form1.vb

Lines 1195 to 1199 in 1af6bff

	If Me.currentShortcut.IsWindowsInstallerShortcut Then
	MessageBox.Show(Me, "This shortcut points to a Windows Installer product." & Environment.NewLine & Environment.NewLine &
	"Support to read/write this shortcut is experimental and saving changes to this file may corrupt the file. Please save any changes to a NEW shortcut file.",
	My.Application.Info.Title, MessageBoxButtons.OK, MessageBoxIcon.Exclamation)
	End If

Then it leverages Windows API functions to extract the properties of Advertised Shortcuts by resolving them through their associated ProductCode from the MSI installer:

Easy-Link-File-Viewer/Source/DevCase/ShortcutFileInfo.vb

Lines 1251 to 1291 in 1af6bff

	Dim msiProductCode As New StringBuilder(39)
	Dim msiFeatureId As New StringBuilder(39)
	Dim msiComponentCode As New StringBuilder(39)
	Dim isMsiShortcut As Boolean = (NativeMethods.MsiGetShortcutTargetW(Me.FullPath, msiProductCode, msiFeatureId, msiComponentCode) = 0)
	Me.isWindowsInstallerShortcut_ = isMsiShortcut
	If isMsiShortcut Then
	Dim path As New StringBuilder(capacity:=1024)
	Dim size As Integer = path.Capacity
	Dim result As Integer = NativeMethods.MsiGetComponentPathW(msiProductCode.ToString(), msiComponentCode.ToString(), path, size)
	If result <= 0 Then
	' Values in "msi.h" header file:
	'
	' INSTALLSTATE_NOTUSED = -7, // component disabled
	' INSTALLSTATE_BADCONFIG = -6, // configuration data corrupt
	' INSTALLSTATE_INCOMPLETE = -5, // installation suspended or in progress
	' INSTALLSTATE_SOURCEABSENT = -4, // run from source, source is unavailable
	' INSTALLSTATE_MOREDATA = -3, // return buffer overflow
	' INSTALLSTATE_INVALIDARG = -2, // invalid function argument
	' INSTALLSTATE_UNKNOWN = -1, // unrecognized product or feature
	' INSTALLSTATE_BROKEN = 0, // broken
	' INSTALLSTATE_ADVERTISED = 1, // advertised feature
	' INSTALLSTATE_REMOVED = 1, // component being removed (action state, not settable)
	' INSTALLSTATE_ABSENT = 2, // uninstalled (or action state absent but clients remain)
	' INSTALLSTATE_LOCAL = 3, // installed on local drive
	' INSTALLSTATE_SOURCE = 4, // run from source, CD or net
	' INSTALLSTATE_DEFAULT = 5, // use default, local or source
	Throw New Exception($"Cannot parse target of Windows Installer link. MSI Error Code: {result}")
	End If
	target = path
	Else
	' SHGetNameFromIDList() can retrieve common file system paths, and CLSIDs/virtual folders.
	If (idlist = IntPtr.Zero) OrElse NativeMethods.SHGetNameFromIDList(idlist, ShellItemGetDisplayName.DesktopAbsoluteParsing, target) <> HResult.S_OK Then
	target?.Clear()
	' IShellLinkW.GetPath() only can retrieve common file system paths.
	shellLink.GetPath(target, target.Capacity, Nothing, IShellLinkGetPathFlags.RawPath)
	End If
	End If

However, please note that if the corresponding product has been uninstalled or is otherwise no longer present, the results may be incomplete or incorrect, and unfortunately, that’s something I can’t guarantee against.