> Also, just one question: how could python -m pip work but not pip? What are the differences in them?

To answer this, "pip" on its own is essentially like writing the full path to a specific python.exe and passing "-m pip". If that Python install has been removed or (more likely in this case) is broken, then you'll get the error you're seeing.

Fixing your PATH as suggested should do it.