Windows 10: Command not recognized on prompt despite being in PATH

Hi, my issue is similar to Commands on command prompt are showing up as "not recognized" - Microsoft Community, but the suggestion there didn't help me and that thread is locked. I did restart the PC after adding those paths to the list. See screenshot here direct image upload keeps failing . Any ideas how to make the command work without writing full path every time, please? Thanks,Ondrej

:)

 

command prompt will not open in safe mode with command prompt

Would I just follow the same steps within safe mode after hooking up to the other system?

 

Installation media boots to command prompt

I've just booted from known working install media to see exactly what it does when booting. The sequence of events is...

1. Windows logo on a black screen
2. circling dots appear beneath the logo
3. light blue 'Please wait' screen with circling dots
4. a command prompt window (very briefly)
5. the initial Setup page appears

Do you see steps 1-3? If so, it appears you have stopped at step 4, suggesting that something on the disc cannot be read.

Does the disc boot properly in another machine? If so, try cleaning the laptop's drive lens then try booting from the disc again.

If not, make new install media with Microsoft's Media Creation Tool, either as a bootable USB, on an ISO that you can burn to another disc. At Step 8 in Option One of this tutorial you can choose between making a USB or an ISO.

Download Windows 10 ISO File

 

Win10 Advanced System Settings shows different path than Command Prompt PATH

The changes to User Variables I made in System Properties (aka Advanced System Settings) Environment Variables do NOT appear in Command Prompt's PATH, despite a reboot. Several items in Environment Variables are not in the PATH.

Why not, but more importantly, how can I fix it?

I can't get PyCharm and Python to work properly, without them being in the PATH.

NOTES: I solved this issue for myself by using System Restore, but it's disturbing.

I made copies of the Command Prompt PATH in a Notepad text file, before and after making changes. So I KNOW 100% that there's a disconnect between Advanced System Settings' Environment Variables and the actual PATH used by Windows apps / Command Prompt.

I'm shocked! What?!

Apparently, Environment Variables is just a copy of the PATH, but not the PATH. Any change to it *ought* to directly change the PATH, but my experience proves that it doesn't (always).