Prevent VMAware from closing/terminating?

[RazviOverflow]

I'm testing VMAware on several sandboxes (commercial SaaS) and it's hard to see the results on the first run because as soon as checks are performed and conclusion is printed the program exits.

Other detection tools usually do a getchar() (or anything that halts the execution waiting for some sort of input) right before terminating, so the user has time to see the results.

Is there anything similar for VMAware? I've been inspecting the code and didn't find it. I know there is a system.pause() call in case parent PID is explorer.exe, but that is not always the case since some sandboxes actually tamper this to avoid detection.

[kernelwernel]

Hi! Sorry for the long reply.

We actually already do this in the experimental release candidate for the 2.4.2 version. I assume you used the current 2.4.1 version.

Please compile the main branch and the cli should pause as you described. If you already did that but it doesn’t pause, please let us know.

@RazviOverflow

[RazviOverflow]

Hi! Sorry for the long reply.

We actually already do this in the experimental release candidate for the 2.4.2 version. I assume you used the current 2.4.1 version.

Please compile the main branch and the cli should pause as you described. If you already did that but it doesn’t pause, please let us know.

@RazviOverflow

Hi there! No worries :)

Yes, when I first tested the program, I used your released 2.4.1 binaries. I’ve since reviewed your latest commits and noticed that you implemented the same modifications I made in my fork RazviOverflow@257cc5d.

I will compile your code (and also try for Win 7 as was mentioned in #480) and retry my experiments :)

Thank you @kernelwernel