You found a Microsoft Windows 10 bug. This appears to occur with any application you install on Windows 10. Guess Microsoft missed this problem.
Your PATH was updated. Go to your environment settings and check and you'll see that your PATH has been updated. However, when you start a command shell, it will not have the correct new PATH. You'll either need to reboot or edit your PATH environment variable and hit all the OK buttons as if you modified your PATH (that's what I did and the next command shell I opened had the right PATH).