Sorry to hear. Wish you all the best! ❤️

Just wondering, because it is now 250 days since Take Command 28.02.18 was released. Hope all is well. Best regards Ernst Mikkelsen

I think I get your point, and then again I don't. Dont' use WSL: Well, to me this have been one of the greatest enhancements to Windows for many years. So this is not an option. Don't use native console for WSL: Please elaborate. How do I launch bash without using native console? Tried several...

Okay - "Use legacy console" seems to be a global option and not only an option for the shortcut being changed. As Ubuntu Bash does not run with this option set, the workaround mentioned above does not solve my issue. As Rex does not see this as a problem with TCC, I would appreciate any...

Just found a "workaround". On the Options tab on the shortcut properties, there's a "Use legacy console" option (see screenshot below). When I check that option, I can now paste strings with $ signs in it. Unchecking "Filter clipboard contents on paste" didn't do it. This option is not...

Easily reproducible here. Take the EN_US 1803 image (MLF_X21-79647.ISO) and create a virtual vanilla Windows from it. Select Danish for Time, Currency and Keyboard. Then Windows 10 Enterprise. And finally Denmark as region and keyboard once more. Install VMware Tools (or whatever is needed for...

After updating/upgrading to Windows 10 1803, I am no longer able to paste e.g. UNC paths containing dollar signs into TCC (the tcc.exe console app). TCC just inserts a NULL character at positions where a $ sign should be placed. The issue does not hit TakeCommand or CMD.

However, IsLicense50.dll is not and I have no doubt, that that is what is causing the problem.

I was about to report the exact same thing. A signed peace of code needs to be timestamped, otherwise Windows refuses to load it (if the certificate is expired, that is).

Thank you very much for that hint, Charles. I've just tried APing, and with some rewriting of my script I might be able to use it. If I fail to make it work, at least you reminded me of the plugin feature in TCC, so maybe I'll just write my own ping6 plugin :smile:

It seems, to my big surprise, that the ping function does not support IPv6 addresses. More than 10 years ago, ISPs started yelling about IPv4 exhaustion, but still we find software not capable of understanding IPv6 addresses. Regards Ernst Mikkelsen

Just installed Build 24 and happily confirms, that the issue is solved! Thanks. Ernst Mikkelsen

It seems that the view command is somehow broken in version 21.0 build 22 as it cannot be launched from tcc anymore. If you type view filename.txt nothing happens at all. If you launch it from tc, it still works as expected. After having installed build 22 and downgrading to build 16, view is...

Fix confirmed! And a happy new year to you, Rex!

The "TCC History popups too small" problem on Windows 8 systems I reported back in August 2013 seems to be solved in the TCC 16.0 beta. Thank you very much!