No, it's the lnk file (not winword.exe).
What this means is that you can open the lnk file as a resource and extract the name of the winword.exe to execute it.
Printable View
No, it's the lnk file (not winword.exe).
What this means is that you can open the lnk file as a resource and extract the name of the winword.exe to execute it.
Did you try calling MsiGetShortcutTarget() on that shortcut and then if it returns ERROR_SUCCESS, call MsiGetComponentPath() to retrieve the path?