Normally this kind of problem is something to do with the order of your PATH environment variable.
Some things include some other things, like visual studio ships with its own copy of some open source utils and if its higher up in the path list and it finds them there first then it will try to use these old versions instead of what you are expecting.
I don't have an exact answer but I would recommend going to your windows path env screen and looking at the order of the paths in there.
Bump ones related to your issue up closer to the start of the list / top of the list and retest.
Note that some things, like command consoles, cache the path variable so you will have to close and reopen things each time you make a change just to be safe.
To get to the path in Windows 10:
- Open the Start Search, type in “env”, and choose “Edit the system environment variables”
- Click the “Environment Variables…” button.
- Under the “System Variables” section (the lower half), find the row with “Path” in the first column, and click edit.
- The “Edit environment variable” UI will appear. From this screen you can also edit or reorder them.
- Dismiss all of the dialogs by choosing “OK”. Your changes are saved!
- You will probably need to restart apps for them to pick up the change. Restarting the machine would ensure all apps are run with the PATH change.
Source: https://www.architectryan.com/2018/03/17/add-to-the-path-on-windows-10/