Hello Giobatcodo,
We've replied this also in the case you logged, this is indeed the result when a deployment is run as Currently Logged on User, or with Scanning Credential. On a computer that is logged on as the scanning credential. If you run the deployment as a system account or scanning credentials in all other scenarios, no CMD window will pop up.
We went ahead and created a product improvement for it. At this moment, we can't guarantee when and if this will be picked up for a future release.