I've tested the all the launch actions on many systems and never had a problem (and no user has reported a problem before this) so unfortunately for you this problem is specific to your system, or to your macro. If you want to post the final command xml code that you are using I will look at it to be sure. As Kalle points out, maybe the problem is with keyboard emulation or something similar. If you are using Launch.Url you could try switching to Launch.RawParam, or vice versa to see if it makes a difference, or try another browser. The Launch actions are all managed code using standard .NET methods, so it should work fine and there is almost no chance that this is due to an error in the VC program itself.