• Options
• Login
• Register
• Desktop Style
• Accelerated Mobile Pages Theme

Adding a shortcut file (.lnk) with arguments

• Index

  • Jean Lalonde Support Forum
  • QUICK ACCESS POPUP FORUM
  • QAP SUPPORT
  • Adding a shortcut file (.lnk) with arguments
• Adding a shortcut file (.lnk) with arguments

• Adding a shortcut file (.lnk) with arguments

  LaurentHaas > 2025-05-06 05:54

  Hi Jean et al.
  
  I have a shortcut whose target is a vbs script with arguments :
  
  C:\Windows\System32\wscript.exe ".\invisible.vbs" ".\openWindowsUpdate.bat"
  
  and the start directory is empty = it is the directory where the shortcut is stored.
  
  For the record, this shortcut opens directly the Windows Update window without displaying any command line (or Windows terminal) window. I use this trick (taken from https://superuser.com/questions/62525/ru...hidden-way - See James comment on Aug 14, 2018 at 20:37) for several other batches.
  
  How can I add this shortcut (.lnk) to QAP ? If I add the shortcut as an Application, QAP truncates the target command and opens wscript.exe only (the arguments are removed/ignored).
  
  Thanks !

• RE: Adding a shortcut file (.lnk) with arguments

  Jean Lalonde > 2025-05-06 06:48

  Hi Laurent,
  
  Right click on the shortcut file and, in the context menu, select "Import shortcut to Quick Access Popup menu".

• RE: Adding a shortcut file (.lnk) with arguments

  LaurentHaas > 2025-05-06 07:17

  Thanks Jean for your prompt reply
  
  I can see now where the arguments are stored (advanced settings), but, with an empty starting directory set in the shortcut, QAP seems to start from the target .exe directory instead (C:\Windows\System32 in this very case). And wscript can't obviously find the vbs script, and the other argument, as they are stored in the shortcut directory. And I can't find a placeholder for the shortcut directory (I guess you "convert" the shortcut and discard its original location). I'm afraid I have to set an absolute path myself in the QAP advanced settings. Not a big deal.

• RE: Adding a shortcut file (.lnk) with arguments

  Jean Lalonde > 2025-05-06 09:28

  > with an empty starting directory set in the shortcut, QAP seems to start from the target .exe directory
  
  I think it is what Windows is doing without "Start In" directory. Not a QAP specific behavior.
  
  > I'm afraid I have to set an absolute path myself in the QAP advanced settings. Not a big deal.
  
  That was the suggestion I was going to make :-)
  
  I'm not sure what is your exact need but maybe one of the QAP location placeholders could help. See:
  https://www.quickaccesspopup.com/can-i-i...ceholders/

• RE: Adding a shortcut file (.lnk) with arguments

  LaurentHaas > 2025-05-06 11:24

  > I think it is what Windows is doing without "Start In" directory. Not a QAP specific behavior.
  
  This is not the case for the original shortcut. If the field empty, it considers the Starting directory to be where the shortcut (lnk file) is, not where the target exe is. You can test it by yourself by creating a shortcut to cmd.exe on the desktop and modify the starting directory with an empty field in the properties. When double-clicked, the command prompt will display the desktop directory path, not the cmd.exe path.
  
  > I'm not sure what is your exact need but maybe one of the QAP location placeholders could help. See: https://www.quickaccesspopup.com/can-i-i...ceholders/
  
  Once the shortcut is imported in QAP, there is no more reference to the shortcut itself, and so there is no way for QAP to know where is was located. I think the import process should take of this by replacing the empty start directory (and only in this case) by the original shortcut directory. Anyway, as said before, not a big deal.
  
  Thanks again

• RE: Adding a shortcut file (.lnk) with arguments

  Jean Lalonde > 2025-05-06 14:07

  > I think the import process should take of this by replacing the empty start directory (and only in this case) by the original shortcut directory.
  
  Noted. It can be changed in the next release. Thanks for reporting this.
• Next Oldest Next Newest