Check for updates works today - installed correctly with 28.02.15.

I reported two problems, apparently. One was that the update didn't appear to be downloading the update - it just fails. The second was that the downloaded full install seems to be 28.01.14. It could be that I have a caching problem. However, my first try to update was from the original 28...

Take Command 28.01.14, using Check for updates (either through Take Command or TCC) to update to 28.02.15 ends with the error message: "Error: The downloaded update size does not match the size specified in updates configuration file." This happens almost instantly (it doesn't seem like enough...

I've been attempting to email [email protected] (by clicking the mailto: link in the announcement email) to report that I have not received my v28 keys. I get a non-delivery message: Your message did not reach some or all of the intended recipients. Subject: License key for TCMD 28...

I tried disabling Malwarebytes and Kaspersky Pure , one a a time and both at the same time, with no change. This is Windows 7. My laptop, running Windows 10, updated with no problems. I can't upgrade the desktop to Windows 10 - the install always fails with an unknown error. I've installed lots...

I'm now trying to install 19, and getting the same result (so it's installing to a new directory). I tried both the exe and the msi.

Basically the same result.

I'm running 18.00.29 64-bit. All updates since then have failed. Attached is the latest log. Windows 7.

Primarily because I hate the limitations of cmd.exe and don't like working within it. The other answer is that I'm a beta tester at heart and can't help raising compatibility issues whenever I encounter them. And this sounds like an oversight on Rex's part - he overlooked a feature of the...

This agrees with my observation and with their stated intention (from some notes somewhere that I can't find anymore) to strip quotes from variables. Why they don't use CR/LF <cr><lf> in native Windows files I don't know. I see this a lot from people who are basically Unix users porting their...

Just for the record, this didn't do it. Here's an example of a statement within one of the .cmd files that causes an error in TakeCommand but not in CMD.exe: </[email protected]>

Boy, that's ambitious. :) Here's the "Getting Started Guide" for an example cli: http://awsdocs.s3.amazonaws.com/IAM/latest/iam-gsg.pdf It calls for downloading this zip file: http://aws.amazon.com/developertools/AWS-Identity-and-Access-Management/4143 You can't do anything useful with it...

I've been trying to use the command line interface to AWS supplied by Amazon, with little success. It is provided as a library of .cmd files (and other files used by the .cmd scripts). These scripts almost universally produce error messages with TakeCommand (and TCC) but work fine with the...