It's understood that, in the absence of the -c parameter, uncap.exe runs in the background, i.e. has no visible output. I can run it via "WIN-R uncap.exe" and it behaves as expected.

When invoked from the command line, however (i.e. an instance of CMD.exe already running) uncap.exe will not only run and close itself but the window from which it was called as well, meaning I have to rerun CMD.exe to continue working on the command line. Is that expected behavior?