[Aaron Lara]

winpty being blocked

We have received reports of the Terminal+ failing to start the shell on some Windows systems. Turns out the issue is caused by some antivirus software blocking winpty from running cleanly. Specifically it causes the process to run twice breaking the needed pipes. So far we have detected McAfee and Avast antivirus doing this. See here for the initial report.

WORKAROUND
Right now we are actively working on a solution! If you are being affected by this issue please try the following:

• A workaround to this issue is to add the following directory to the anti virus whitelists:
  (user.home)\.codemix\engine\resources\app\node_modules\node-pty\build\Release\

Shellcode Injection

Comodo’s shellcode detection is known to cause odd issues with Terminal+ behavior. We’ve seen it result in the Terminal+ incorrectly report missing directories or throw odd internal errors. While we haven’t had reports to this effect, it is possible that shellcode detection in other A/V software could cause similar issues as well.

If you’re experiencing issues with basic functionality in Terminal+, consider excluding CodeMix binaries from shellcode detection. You will need to exclude folders in your CodeMix store, which can typically be found at [user_home]/.codemix-store, or check the Preferences > CodeMix > Miscellaneous > Storage page for the CodeMix Terminal+ Area.

• This topic was modified 6 years, 2 months ago by Aaron Lara.
• This topic was modified 6 years, 2 months ago by Aaron Lara.
• This topic was modified 6 years, 2 months ago by Aaron Lara.
• This topic was modified 6 years, 2 months ago by timwebb.
• This topic was modified 6 years, 2 months ago by Aaron Lara.
• This topic was modified 6 years, 2 months ago by Aaron Lara.
• This topic was modified 5 years, 2 months ago by Brian Fernandes.

[Author]

Posts