Has anyone found such behavior when Command Processor (cmd.exe) closes immediately after calling it?
I’ve run McAfee AV and Windows System File Check (sfc.exe) and nothing wron
Answering in case anyone else still runs into this problem. I have recently experienced same issue, and the reason for that was a bitcoin mining malware. I used Malwarebytes to scan the computer and remove the malware, which immediately resolved the problem.