New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v5.0.0beta: Not working: Missing Python Runtime (search): despite manually setting the Python path (per "Allow users to specify Python executable path #19644"), Python cannot be found by qBittorrent #20737
Comments
You need to put the full path to python.exe in the "Python executable path" option. For example: |
Thank you for catching that one. Entering the full path, including the python.exe executable, DID NOT fix the problem. qBT 4 and 5 still ask to install Python themselves, but after doing so it will still not find python.exe. Even worse, v5 is now constantly freezing and not responding at all (despite having qBittorrent.exe excluded from Sticky Password in its program settings) Thank you! https://snipboard.io/ls8uST.jpg https://snipboard.io/GplZoh.jpg `C:\Users\Gebruiker>python --version C:\Users\Gebruiker>where python From the LOG: |
It indicates one thing: qbt couldn't access the executable for unknown reasons. Could be insufficient permission or something is blocking the access. For the record, I couldn't reproduce the issue, it works for me. |
What reasons could there be? Running qBT as an admin makes no change. Disabling Avast AV makes no difference either. The OS finds it just fine, so does the installer used by qBT. But once it's installed, somehow qBT just can't see it. What else to look at? :( |
Try downloading a the "Embeddable package" from Python's website @realdevnullius . Extract it to like to your Documents folder (something writable, accessible) and give that .exe path to qB. |
Downloaded and extracted the embedded zip file to: I entered that path statement in qB ("D:\python-3.12.3-embed-amd64\python.exe"). I restarted qB and clicked View... Again, an installer prompt appears telling me that Python is not installed. Like, how!!? :( I just can't figure this out. Someone even built a custom qB 4 wallet with more log notifications but even that didn't teach us anything new. It just won't work on this specific PC :( The installation prompt will run each time and the installer itself will recognize Python already installed and is done rather quickly (nothing to do!). |
I also did this: #20392 (comment) (including 2 PC reboots and an uninstall with IObit Uninstaller). As expected: qB keeps behaving the same: Python is not found. It's maddening I tell ya! |
@realdevnullius Are you running Windows 11 via parallels desktop on mac or any other VM?
|
@xavier2k6 thanks for the question: no, just regular Windows 11 on a regular Intel PC. |
@realdevnullius Under "Manage App Execution Aliases" Are When installing did you select "Add Python 3.x to PATH"? |
Author did set it in qBittorrent |
Edited #20737 (comment) to add images via github in case those links go down. |
PATH:
|
qBittorrent & operating system versions
qBittorrent: 5.0.0 beta 1, LT20, x64
Operating system: Windows 11
Qt: 6
What is the problem?
This issue is hunting me on 1 PC for the longest time...
In regards to version 4: https://forum.qbittorrent.org/viewtopic.php?t=11055
In regards to version 5: https://forum.qbittorrent.org/viewtopic.php?t=11409
No matter what we tried, qBittorrent just won't find ANY Python installed, ever. And yes, I think I tried it all and that's why I went to v5 beta in the hopes that manually setting the Python path (finally!) would fix my issue.
It did not. So I made a bug report. Screenshots, steps taken, etc. are all in the forum threads.
Steps to reproduce
No steps, it always fails no matter what I try.
Additional context
See forum links please
Log(s) & preferences file(s)
I have no settings file I can upload. All I found were:
qbittorrent.ini
qbittorrent-data.ini
(empty) watched_folders.json
categories.json and an RSS folder.
I doubt there's anything of interest in it.
I have not been able to find a log file, though I posted console logs to the forum threads.
The text was updated successfully, but these errors were encountered: