Windows 7 64bit,
I've tried launch.openfile, launch.openbat and a few others. I can see the command being successfully interpreted and 'executed' but it never actually runs/opens the file.

I'm using the trial version, is there a limitation on running external executables that I am unaware of? I need to make sure this simple functionality is there before I buy it.

There is no such limitation.  It should work if your parameter is a proper full path to an executable or batch file.

edit: try this

action:  Launch
param:  notepad.exe

The path is correct, so I'm not really sure, I'm able to "open text files" and do other such things, juts not .bats, do you think it could be some kind of inherent windows safeguard? Maybe I have to "run as administrator for voxcommando? I'm at work now, I'll update with some more details when I get home, thanks for your reply.

it might depend on where your bat file is.  I just tested running a batch file with both Launch and Launch.bat and in both cases it worked fine.  If the bat file is in a system protected folder then running as admin might help.

Figured it out, It wasn't able to access my .bat for some reason so i just moved it to my documents, thanks for your help.

Ok good. 

I'm glad you brought this up though, I'm taking another look at my launch commands and adding some error feedback in the history window so it will be easier in the future to diagnose what is going on when it doesn't work.  It will tell you if it can't find the file, or if there is an access violation.  There are so many nook and crannies in this program...