Bug report

Bug description:

I recently did a fresh python installation, from python.org (https://www.python.org/ftp/python/3.12.2/python-3.12.2-amd64.exe)
I did installed it on an "uncommon" directory (D:\EDM115\Programmes\Python312\), but this had never caused any issue in the past.
The main issue is that theScripts folder was simply empty, meaning that no pip command worked. I verified that the pip checkbox was checked, tried to repair and later redo the install, only to face the same issues.
What fixed it was to runpy -m ensurepip --upgrade and later renameD:\EDM115\Programmes\Python312\Scripts\pip3.exe toD:\EDM115\Programmes\Python312\Scripts\pip.exe, but I believe that it should be done automatically

CPython versions tested on:

3.12

Operating systems tested on:

Windows

Linked PRs

• gh-117505: Run ensurepip in isolated env in Windows installer #118257
• [3.13] gh-117505: Run ensurepip in isolated env in Windows installer (GH-118257) #119421
• [3.12] gh-117505: Run ensurepip in isolated env in Windows installer (GH-118257) #119422