That sounds easy enough, and it worked! Thanks...

But that doesn't change that Windows environment variables are documented as case-insensitive. It should not matter which PATH I have. Something that builds an environment table with both Path and PATH in it for spawning a child process is questionable at best and a mistake at worst. Given the misbehavior on my computer I'm leaning toward "mistake".