Hi, thanks for sharing this issue.

Looking at the path of the command window, this seems to be sourced from a .EXE located inside your NCrunch workspace.

NCrunch doesn't invoke .EXEs inside the workspace - but it does run your test code, which might be responsible for doing this.

v2.20 introduced a change in which the task runners are no longer run as console applications (they are now standard windows applications). It's possible that this change has had some kind of knock-on effect on the behaviour of your test code, but at this stage I have no idea how such a change could cause this problem.

Have you tried running your tests selectively to isolate the one causing the window to pop up?

I recommend the 'binary search' method, in which you run 50% of your tests, then wait to see if it happens.

Based on your result, you can choose whether to run the other 50% of your tests, or split the original 50% in two, and run half of them. Usually you can narrow it down to a single test within a few short runs.

NCrunch itself doesn't support Javascript, so I assume that these tests are being run through some intermediate adapter in your own code.

I suggest looking into how this adapter is implemented. If it's spawning a new process, suppressing the command window may be as simple as just adjusting the parameters to the method spawning the process.