Jason Hood

Use Run (Win+R) to run `cmd /d` - that will start a new command prompt without ANSICON. Then use `reg delete "HKCU\Software\Microsoft\Command Processor" /v AutoRun` to do it permanently.

I've released v1.65, deleting the files on SkyDrive.

Console2 is a GUI process, so ANSICON will not hook it and thus nothing Console2 starts will be hooked (except `CMD.EXE` if you use `-i`). You can start Console2 directly...

Just to make sure we're still talking about the same thing, can you try this in a new Command Prompt (since it's not working, I'm assuming it's not already installed):...

Could you try the steps in the December comment with the preliminary [1.70](https://onedrive.live.com/redir?resid=D18DE9C2F9D17ED!127&authkey=!ADZkdErqDeWb2cg&ithint=file%2c.zip)?

The binaries (all that's in the x86/x64 directories) are under [releases](https://github.com/adoxa/ansicon/releases) here or on my [site](http://ansicon.adoxa.vze.com/). On 7, it seems to be `mscorwks.dll` that controls Powershell output (at least excluding...

I'm going to need more information, as it seems to work fine with 8.1 and 10 (using 32-bit `cmd.exe` and VS2010 `signtool`).

I've used Python 3 (3.4.2) with success (Win7 x64). ``` C:\Language\Python34>ver Microsoft Windows [Version 6.1.7601] C:\Language\Python34>ansicon --version ANSICON (64-bit) version 1.83 (16 February, 2018). C:\Language\Python34>python --version Python 3.4.2 C:\Language\Python34>type test.py...

Just tried with both the 32- and 64-bit versions of 3.6.5 without incident. Can you provide more details? I'd like to resolve this before releasing 1.84.

Currently you'd have to go through the console Properties and the Colors tab, but I should be able to add the sequences to define the palette.