When I use the
start command in a batch script to launch a program, I expect that program to be launched asynchronously; this happens exactly as I'd expect it would if the program that I'm launching exists.
However, if I try to
start a program that doesn't exist, Windows displays a popup telling me that it cannot find the file, locking up the execution of the batch script until I manually close the popup. This is annoying. Because of some remote filesystem shenanigans, I have no way to reliably guarantee that the binary will exist before I run it, and I have no way to lock the binary. In my scenario, if the binary doesn't exist, it's not a critical error, and my script should just proceed.
Is there a way to prevent these popups from being created in the first place, or alternatively a batch/cmd one-liner that can be used to asynchronously execute applications that won't block the script from continuing if it fails (something I can just as easily use from a CLI as a batch script)?