Yes, I’m using Windows 10
If I run the Upgrade/Downgrade from Anki I still get the warning that the launcher could not determine the current Anki version and if I select “2) Choose a version” I still get the error from versions.py. This now happens whether I start Anki from the dock or by calling launcher from the command line. Before this version it did not happen when I started Anki from the command line.
Anki Launcher
Warning: Could not determine current Anki version
- Latest Anki (press Enter)
- Choose a version
- Revert to previous version (25.08b1)
- Allow betas: on
- Cache downloads: on
- Uninstall
> 2Please wait…
Error: Failed with code Some(1): /Applications/Anki.app/Contents/MacOS/uv run --no-project /Applications/Anki.app/Contents/Resources/versions.py
Press enter to close…
Please reproduce the error outside of Anki so it’s more clear: anki/qt/launcher/src/main.rs at e77cd791deb8d412d1ed9083f2697e389605823a · ankitects/anki · GitHub
I’m guessing we need to exclude VIRTUAL_ENV there too?
Yes, I believe I tested with add-ons disabled, though I’m not 100% sure.
In any case, I can no longer reproduce the issue since updating to 25.08b2. Everything seems to run smoothly, even after reinstalling 25.08b1 (using the old launcher) and testing with add-ons enabled.
By the way, if I update to 25.08b2 using the old launcher, then go to Tools > Upgrade/Downgrade and select “Yes”, nothing happens - it just restarts Anki.
(The new launcher seems to work fine, I haven’t encountered any issue for now)
I ended up uninstalling and reinstalling Anki and I don’t get the error from version.py anymore when choosing a version, either from running Anki on the doc or from the command line. I also have my virtual environment commented out in .zshrc, so no environment variable to worry about. I still get the Warning about not being able to determine the version, though, from both the dock and the command line.
Anki Launcher
Warning: Could not determine current Anki version
Latest Anki (press Enter)
Choose a version
Allow betas: on
Cache downloads: on
Uninstall
2
Please wait…
Latest releases: 25.08b2, 25.07.2, 25.06b7, 25.02.7, 25.05b2
Enter the version you want to install:
If I run the launcher from the command line I get the launcher menu above when I run Upgrade/Downgrade from Anki. I don’t know how to force the launcher into the menu without starting Anki.
Here’s what I get on the command line while doing all this:
/Applications/Anki.app/Contents/MacOS/launcher [NORMAL]
Starting Anki 25.08b2…
2025-07-15 14:48:29,540:INFO:aqt.mediasrv: Serving on http://127.0.0.1:57069
Starting main loop…
2025-07-15 14:48:40,086:WARNING:waitress: unhandled close event
(venv_m1_313) ➜ Downloads
I then put the venv back into my profile and ran Anki from the dock and the launcher and the menu behaved the same way.
Like Expertium mentioned, the “gear wheel” bug no longer happens. Presumably the downgrade back to Qt 6.8 is responsible.
Logged that issue on launcher: do we need different ANSI handling on Windows 10? · Issue #4209 · ankitects/anki · GitHub
I wonder if there are other env vars/paths set that is causing this? Any extra digging/info you can provide would be appreciated. The ‘uv run’ command is shown in the error message - running it manually doesn’t trigger the same problem?
Thanks for you kindly reply, it is fixed.
Maybe it is best to rollback to the standard version of Anki.
So far the lag problem seems to be fixed 
The issue persists in beta 2. Every UI element that is NOT rendered in a webview has this issue.
Edit: As per my testing with different versions of pyqt6-qt6 in pyproject.toml, this regression was introduced in v6.8.2. v6.8.1 has normal font while subsequent versions (upto 6.9.1) have the distorted font.
uv run appears to work fine. This looks more like a list of historical versions, though, rather than it telling me which version is active. Am I on the right track?
/Applications/Anki.app/Contents/MacOS/uv run --no-project /Applications/Anki.app/Contents/Resources/versions.py [NORMAL]
[“2.1.24”, “2.1.25”, “2.1.26”, “2.1.28”, “2.1.29”, “2.1.30”, “2.1.31”, “2.1.32”, “2.1.33”, “2.1.34”, “2.1.35”, “2.1.36”, “2.1.37rc1”, “2.1.37”, “2.1.38b1”, “2.1.38b2”, “2.1.38b3”, “2.1.38b4”, “2.1.38”, “2.1.39b1”, “2.1.39b2”, “2.1.39”, “2.1.40”, “2.1.41b1”, “2.1.41b2”, “2.1.41b3”, “2.1.41b4”, “2.1.41b5”, “2.1.41b6”, “2.1.41b7”, “2.1.41”, “2.1.42”, “2.1.43b1”, “2.1.43”, “2.1.44b1”, “2.1.44”, “2.1.45a1”, “2.1.45a2”, “2.1.45a3”, “2.1.45a4”, “2.1.45b1”, “2.1.45b2”, “2.1.45b3”, “2.1.45b4”, “2.1.45b5”, “2.1.45b6”, “2.1.45rc1”, “2.1.45rc2”, “2.1.45”, “2.1.46rc1”, “2.1.46”, “2.1.47rc1”, “2.1.47rc2”, “2.1.47”, “2.1.48rc1”, “2.1.48rc2”, “2.1.48”, “2.1.49”, “2.1.50b1”, “2.1.50b2”, “2.1.50b3”, “2.1.50b4”, “2.1.50b5”, “2.1.50b6”, “2.1.50b7”, “2.1.50b8”, “2.1.50b9”, “2.1.50rc1”, “2.1.50rc2”, “2.1.50rc3”, “2.1.50rc4”, “2.1.50”, “2.1.51rc1”, “2.1.51rc2”, “2.1.51”, “2.1.52rc1”, “2.1.52rc2”, “2.1.52rc3”, “2.1.52”, “2.1.53rc1”, “2.1.53rc2”, “2.1.53”, “2.1.54rc1”, “2.1.54rc2”, “2.1.54rc3”, “2.1.54”, “2.1.55b1”, “2.1.55b2”, “2.1.55b3”, “2.1.55b4”, “2.1.55b6”, “2.1.55b7”, “2.1.55rc1”, “2.1.55rc2”, “2.1.55”, “2.1.56rc1”, “2.1.56”, “2.1.57b1”, “2.1.57rc1”, “2.1.57”, “2.1.58”, “2.1.59”, “2.1.60”, “2.1.61b1”, “2.1.61b2”, “2.1.61”, “2.1.62b1”, “2.1.62rc1”, “2.1.62”, “2.1.63”, “2.1.64”, “2.1.65”, “2.1.66b1”, “2.1.66rc1”, “2.1.66”, “23.10b1”, “23.10b2”, “23.10b3”, “23.10b4”, “23.10b5”, “23.10b6”, “23.10rc1”, “23.10rc2”, “23.10rc3”, “23.10”, “23.10.1rc1”, “23.10.1rc2”, “23.10.1”, “23.12b1”, “23.12b2”, “23.12b3”, “23.12rc1”, “23.12”, “23.12.1”, “24.4rc1”, “24.4rc2”, “24.4”, “24.4.1”, “24.6”, “24.6.1”, “24.6.2”, “24.6.3”, “24.10b1”, “24.10b2”, “24.10b3”, “24.10b4”, “24.10rc1”, “24.10rc2”, “24.11rc1”, “24.11rc2”, “24.11”, “25.1b1”, “25.1rc1”, “25.2rc1”, “25.2”, “25.2.1”, “25.2.2”, “25.2.3”, “25.2.4”, “25.5b1”, “25.5b2”, “25.2.5”, “25.2.6”, “25.2.7”, “25.6b1”, “25.6b2”, “25.6b3”, “25.6b4”, “25.6b5”, “25.6b6”, “25.6b7”, “25.7”, “25.7.1”, “25.7.2”, “25.8b1”, “25.8b2”]
I think I know what it is. I looked at main.rs to see how the launcher gets the version and found it calls “pip show aqt”.
- I ran the command from the command line and it said the package wasn’t found.
- I ran which pip and saw it was the pip from my personal venv, which in in the first directory of my PATH environment variable.
- I took my venv out of the PATH and then zsh used /usr/local/bin/pip. It still didn’t find aqt, because Anki has it’s own venv.
- I activated the venv with ~/Library/Application\ Support/AnkiProgramFiles/.venv/bin/activate and then pip showed aqt:
$ pip show aqt
[NORMAL]
Name: aqt
Version: 25.8b2
Summary:
Home-page:
Author:
Author-email:
License-Expression: AGPL-3.0-or-later
Location: /Users/beirne/Library/Application Support/AnkiProgramFiles/.venv/lib/python3.13/site-packages
Requires: anki, anki-mac-helper, beautifulsoup4, flask, flask-cors, jsonschema, pip-system-certs, pyqt6, pyqt6-webengine, requests, send2trash, waitress
Required-by: anki-release
I then ran the launcher from the command line since I have a clean environment but it still does not show the current version. Now I wish I was on Linux and had a proc file system to show me what variables the launcher had.
25.07.3rc1 is now available to test:
If you’re not already using the 08b2 launcher or had troubles with it, please update the launcher first.
Thanks, that’s useful to know. Perhaps related to Loading.... It doesn’t seem to bother other people enough to justify reverting to an older version, and 6.9 fixes a prevalent crashing issue on macOS.
I’ve made a change that might help - does the latest launcher make any difference?
2 Likes
It’s a bit confusing that the naming reverted back to 25.7 after flirting with 25.8, because someone selecting “Choose a version” might automatically assume that 25.8b are the very latest betas.
They’re shown in release order in the launcher:
Latest releases: 25.07.3rc1, 25.08b2, 25.06b7, 25.02.7, 25.05b2
Enter the version you want to install:
I uninstalled what I had and then installed 25.07.3rc1 without any of my own venv in the environment or path. It worked find and I did not get errors about not finding the version.
I then uninstalled again and put my venv back into .zshrc and reinstalled. It then would crash when I would exit Anki or go to the Upgrade/Downgrade menu, until I decided to report it here. Now that I’m doing that I can’t reproduce it. 
I have the crash report, though, if you want it.
Even with my virtual environment set, the launcher now gets the version. This works if I start Anki from Alfred or from the command line, so things are looking better. I’ll have to see if I can reproduce the crashes, though.
I reinstalled and can’t reproduce the crashes, so I guess ignore those for now
Same in Windows 11 and the latest launcher (25.07.3rc1):
That’s strange, 25.07.3rc1 looks fine for me.
Btw, Dae, what is “Sync project changes?”
1 Like
While the handling of this particular rare case (25.8 being renamed to 25.7) looks correct, but this behaviour is problematic. Suppose, I am testing the beta releases of a new major version and a patch release of the stable version is released in the mean time. Then, the current behaviour means that my Anki will be downgraded to the patch release if I choose “Latest Anki” in the launcher because it was released later even though I am already on a newer major version.
Just to share my experience, I didn’t have this issue with any version of the launcher on Windows 11.
1 Like