Home » Tools » ExeLauncher » ExeLauncher

ExeLauncher

Posted on by

Occasionally when I’m sequencing App-V 5 applications I find that some of the files that I have included inside the virtual file system cannot be read at run time, even though they exist in the virtual file system!

One example that exhibited this behaviour was when the main shortcut pointed to an executable on a remote share –  when the shortcut was launched, it couldn’t ‘see’ the files that were captured in the virtual file system.

Another example was when the shortcut pointed to a .hta file (The resultant shortcut created a local instance of mshta.exe and as such any calls made couldn’t see ‘inside’ the virtual file system)!

An easy way to circumvent these issues is to use my ExeLauncher.  It does exactly what it says on the tin – it launches executables!  But crucially you will include ExeLauncher.exe inside your App-V 5 package!

You can run it like so:

ExeLauncher.exe "[Path To Executable]" "[Arg 1]" "[Arg 2]" "[Arg x]"...

It will accept an unlimited number of arguments – remember to enclose the path to the executable and any arguments inside quotes, just in case they contain spaces.

To continue on from my examples above, to fix my App-V 5 issues instead of capturing a shortcut to:

\\[remoteshare]\alkane.exe

I placed a copy of ExeLauncher.exe inside my virtual package and then created a shortcut to:

C:\[PathToExeLauncher]\ExeLauncher.exe "\\[remoteshare]\alkane.exe"

and instead of capturing a shortcut to:

c:\[pathToHta]\alkane.hta

I placed a copy of ExeLauncher.exe inside my virtual package and then created a shortcut to:

C:\[PathToExeLauncher]\ExeLauncher.exe "c:\windows\system32\mshta.exe" "c:\[pathToHta]\alkane.hta"

Then give your shortcut whatever icon and name you want, and voila! Since you’re targetting an executable that resides inside the virtual file system, any process it calls will now be able to see ‘inside’ the virtual file system and your App-V applications will now work correctly!

Comments have now been disabled. If you have a question to ask about this post please ask the community!