Avogadro version: Avogadro 2. 1.100
Operating system and version:
Windows 11 Pro Version 21H2
After installing Avogadro2 1.100, the program does not start. Log judge, the program complains that there is no correct path to the Python interpreter. At the same time, I installed both the Current Release and the Nightly Build, and still no one works. I also recently reinstalled python, but it also doesn’t help. Attach logs to the post
I have same problem with Win 10, I also tried both classic and Nightly version.
First time it showed message like if I donť mind installing Python, so I agreed, but nothing happened neither after installing Python 3.13 fom MS store and reinstalling avogadro2.log (7.3 KB)
So if I understand correctly, it popped up a dialog about installing Python, you did that, but you never see an actual editor window? Even when it had the message about installing Python?
The challenge has been figuring out what part of the code is causing problems. So it helps to know at least what parts of the code work before it evidently crashes.
As I mentioned in another thread, I’m pretty busy this week, but will try to get another debug / test build to see if we can fix the issue. Not all Windows users seem to be affected (e.g., it works for students in my research group fine)
I had the same thing as @LordGnarlord. During the first launch, I was offered, like, to install Python, I agreed, after which this window just closed, and Avogadro 2 appears in the task manager, but almost immediately it finishes working.
In my case, it doesn’t open at all. In the task manager, it just shuts down, and if it had turned on again later, that would have happened, since I was still working on the computer. Of course, if it turns on after 10 hours, but then there is a question of convenience)
I had major problems tracking down why Avogaro2 crashed on startup in Windows 10 - even the older versions wouldn’t start.
Eventually I found a registry entry titled OpenChemistry under HKEY_USERS that wasn’t removed during an uninstall. Uninstalling, deleting that key and finally reinstalling version 1.100 works perfectly. I should have twigged earlier as the window always appeared on my second monitor after every reinstallation
Interesting. Sounds like resetting the settings worked for you. Let me think about how to detect a crashed startup and offer to reset settings on the next launch…