I ran into this problem recently. With Visual Studio 2019 installed, I had already installed Python as a workload. I went to CMD and typed python. Up came the Microsoft Store. After wasting too much time looking more into this, it was obvious to me Microsoft Visual Studio team and Python team were not on the same page.
What I eventually ended up with was going back into Visual Studio installer and unchecking the Python workload to uninstall. Then, going into Windows Apps and uninstalling Python and any Python related applications listed.
After noticing that Python was installed on my 1TB NVMe SSD boot drive in the users directory I cringed. The path name was not friendly at all. Not only that, but because I have limited space on that drive and with all the Microsoft Store apps piling up, I dread to think what happens when the drive goes full.
So I decided, this was not good and chose to go to the Python website and download the current version. Then, install in a non-boot drive with plenty of disk space into a friendlier file path (D:\Python). You'll see why this is important when you go pip down a bunch of packages and applications...
Also, if you run into environment space problems, at the end of the Python installer is a question if you want to increase environment space. Say yes. Looking at my environment PATH, D:\Python\Python38\Scripts and D:\Python\Python38 were pre-appended.