Jason Hood

Windows 10 1803 (10.0.17134.48 with Defender updated just now) didn't complain about 1.84.

It looks like you need to sign in to Trend Micro support to report a false positive. If you're on 10 [here's](http://ansicon.adoxa.vze.com/termon.exe) ([source](http://ansicon.adoxa.vze.com/termon.c)) an alternative program which enables terminal processing...

According to the crash address it's not the sequence causing the crash, but injecting into a DLL. [Here's](https://github.com/adoxa/ansicon/files/4424806/inaccessible.zip) a DLL that will catch and log it. Run the script with...

> The version of the DLL provided does not cause a crash Nor does it show anything as inaccessible. Strange. > however when I run the php script by passing...

[Here's](https://github.com/adoxa/ansicon/files/4432878/inaccessible.zip) an update that fixes scripts run directly by `cmd`. It also moves the crash test to log level 64 (undocumented). Try without logging and see if it still crashes...

Have you tried this, @rmroczk?

Okay, couple of other tweaks to make then I'll put out a new release.

Use the Run dialog to run `cmd /d`, then you can uninstall. Should it still not work, have a look at `HKCU\Software\Microsoft\Command Process\AutoRun`. Does `ansicon -p` work on the command...

That value is fine, so there's something going wrong with `-p`. Does just `ansicon` work? That should start a new instance of `cmd`, with sequences. What's your version of 10?

Okay, that's a bit more than I was expecting. I was really only after the build version, although Enterprise might have something to do with it. Just tried `ansicon -p`...