[issue45789] Python execution broken after update via Windows Store

2022-02-09 Thread firewave
firewave added the comment: Actually "Process Explorer" finds the handle as well. No idea why it didn't come up in my last search. -- ___ Python tracker ___ _

[issue45789] Python execution broken after update via Windows Store

2022-02-09 Thread firewave
firewave added the comment: I figured it out. I tried to delete the files using PowerShell and I got the following: Remove-Item : Cannot remove item C:\Users\Username\AppData\Local\Microsoft\WindowsApps\python.exe: The process cannot access the file 'C:\Users\Username\AppData\Local\Microsof

[issue45789] Python execution broken after update via Windows Store

2022-02-09 Thread Steve Dower
Steve Dower added the comment: It still unfortunately sounds like a Windows issue. All we do is specify that there should be a file there, we have nothing to do with creating or removing them. I'm not sure there's anything else we can do to help. You could try reporting the issue using the W

[issue45789] Python execution broken after update via Windows Store

2022-02-09 Thread firewave
firewave added the comment: A few weeks ago I was able to re-install Python 3.9 and 3.10 after manually removing the %LocalAppData%\Microsoft\WindowsApps\PythonSoftwareFoundation.Python.3.* and disabling/enabling the applinks manually and uninstalling/installing a few times to get rid of al

[issue45789] Python execution broken after update via Windows Store

2021-11-16 Thread firewave
firewave added the comment: Today 3.9.2544.0 was automatically installed on my system. Interestingly it did not update the broken "python3.9.exe" appexec links. The timestamp is still from the last update and the links still point to 3.9.2032.0. All other links were updated. -- ___

[issue45789] Python execution broken after update via Windows Store

2021-11-12 Thread Eryk Sun
Eryk Sun added the comment: > Also all those files are 0 bytes - even the working ones. The files should have no data, just appexec links. It's just an empty file if there's no link set. > Since I cannot even run the actual executable there seems to be > an issue with the executables on top

[issue45789] Python execution broken after update via Windows Store

2021-11-12 Thread Steve Dower
Steve Dower added the comment: You're right. You probably need to uninstall and reinstall for the subdirectories of WindowsApps. -- ___ Python tracker ___ ___

[issue45789] Python execution broken after update via Windows Store

2021-11-12 Thread firewave
firewave added the comment: That didn't work. The link is wrong on the disk and that setting just controls the usage of it not the creation. -- ___ Python tracker ___ ___

[issue45789] Python execution broken after update via Windows Store

2021-11-12 Thread Steve Dower
Steve Dower added the comment: > Could it be possible that it might not be able to replace that link when it > is currently in use? That (or something like that) would be my suspicion. It's happened before, though as Eryk Sun says the link itself does not remain in use very long at all. I

[issue45789] Python execution broken after update via Windows Store

2021-11-12 Thread firewave
firewave added the comment: The "python3.9.exe" link is that one also points to the earlier version. All other links are fine. Also all those files are 0 bytes - even the working ones. Since I cannot even run the actual executable there seems to be an issue with the executables on top of th

[issue45789] Python execution broken after update via Windows Store

2021-11-12 Thread Eryk Sun
Eryk Sun added the comment: > The python3.9.exe file in the WindowsApps folder looks like > a real executable and not a link. As requested, and as shown in the output, you tested the file in Python 3.9's subdirectory of "WindowsApps", not in "WindowsApps" itself. If the size in the `dir` ou

[issue45789] Python execution broken after update via Windows Store

2021-11-12 Thread firewave
firewave added the comment: The python3.9.exe file in the WindowsApps folder looks like a real executable and not a link. The script also backs that python3 read_appexec.py "c:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.2288.0_x64__qbz5n2kfra8p0\python3.9.exe" Tracebac

[issue45789] Python execution broken after update via Windows Store

2021-11-12 Thread Eryk Sun
Eryk Sun added the comment: > Could it be possible that it might not be able to replace that > link when it is currently in use? Appexec links are only used briefly to find the real executable and create the access token that allows executing it. I don't know how your local profile director

[issue45789] Python execution broken after update via Windows Store

2021-11-12 Thread Eryk Sun
Change by Eryk Sun : Removed file: https://bugs.python.org/file50434/read_appexec.py ___ Python tracker ___ ___ Python-bugs-list mailing lis

[issue45789] Python execution broken after update via Windows Store

2021-11-12 Thread firewave
firewave added the comment: Thanks a lot for all the details. I used the script to check all the 3.9 appexec links and only the "python3.9" one points to the wrong executable. Version: 3 Package ID: PythonSoftwareFoundation.Python.3.9_qbz5n2kfra8p0 Entry Point: PythonSoftwareFoundation.Pytho

[issue45789] Python execution broken after update via Windows Store

2021-11-11 Thread Eryk Sun
Eryk Sun added the comment: > It fails with "The system cannot find the file > C:\Users\\AppData\Local\Microsoft\WindowsApps\python3.9.exe." The shell's CreateProcessW() call failed with ERROR_FILE_NOT_FOUND (2). The file exists, but it's probably a broken appexec link. I'm attaching a scr

[issue45789] Python execution broken after update via Windows Store

2021-11-11 Thread Steve Dower
Steve Dower added the comment: Can you look in your %LocalAppData%\Microsoft\WindowsApps folder and see if the python*.exe files are there? You should be able to double-click them to launch them. That folder should be on your PATH so that they work everywhere, and it should reflect what you

[issue45789] Python execution broken after update via Windows Store

2021-11-11 Thread firewave
firewave added the comment: I checked them and they look fine. I have Python 3.10 installed as well so the non-suffix and "3" suffix-only executable refer to that. All the "3.9" suffix ones point to the "Python 3.9" entries and are enabled. -- ___

[issue45789] Python execution broken after update via Windows Store

2021-11-11 Thread Steve Dower
Steve Dower added the comment: If you open "Manage app execution aliases", do you see the entries for Python? I've heard that they sometimes switch themselves off during updates, but nobody seems to know why. Even if not, disabling and re-enabling them may help. The executable in Program Fil

[issue45789] Python execution broken after update via Windows Store

2021-11-11 Thread firewave
New submission from firewave : I have Python 3.9 installed from the Windows Store and use it in CMake scripts. After the recent update to 3.92288.0 Python executions suddenly started failing with "Access is denied". I assumed I was using a wrong or cached path but that didn't turn out to be t