# ORCA input unavailable after 1.102.1 update **URL:** \ **Category:** Support\ **Created:** [October 28, 2025, 4:15am UTC](https://discuss.avogadro.cc/t/orca-input-unavailable-after-1-102-1-update/7200 "2025-10-28T04:15:52Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![andy\_huang](https://discuss.avogadro.cc/letter_avatar_proxy/v4/letter/a/5f9b8f/32.png) [@andy\_huang](https://discuss.avogadro.cc/u/andy_huang)\ **Post date:** [October 28, 2025, 4:15am UTC](https://discuss.avogadro.cc/t/orca-input-unavailable-after-1-102-1-update/7200/1 "2025-10-28T04:15:52Z")
Please consider submitting issues to [GitHub](https://github.com/OpenChemistry/avogadrolibs/issues) which will enable tracking bug reports and suggestions. These will be closed and updated automatically when they are fixed – including notifications. I believe this to be a bug with Avogadro: After the 1.102.1 update, I no longer have the option to create an ORCA input via Input \> ORCA. Under Python settings, the path is still listed, however. ## Environment Information Avogadro version: 1.102.1 Operating system and version: Windows 11 version 24H2 ## Expected Behavior Option to create an ORCA input should appear. ## Actual Behavior Available options only include APBS, CP2K, GAMESS, LAMMPS, or OpenMM Script. ## Steps to Reproduce ![image](https://discuss.avogadro.cc/uploads/default/original/2X/4/4d6ff815e5b6b7f275946a3510972d3cb0ad807c.png) ---
**Author:** ![ghutchis](https://discuss.avogadro.cc/user_avatar/discuss.avogadro.cc/ghutchis/32/456_2.png) [@ghutchis](https://discuss.avogadro.cc/u/ghutchis)\ **Post date:** [October 28, 2025, 10:35am UTC](https://discuss.avogadro.cc/t/orca-input-unavailable-after-1-102-1-update/7200/2 "2025-10-28T10:35:53Z")
What version were you using before? And did you install Python via 1.102 or did you already have Python installed? Thanks Oh, and there should be an Avogadro2.log file in your Documents directory. If you can post that, it would also be really helpful. Thanks. ---
**Author:** ![ghutchis](https://discuss.avogadro.cc/user_avatar/discuss.avogadro.cc/ghutchis/32/456_2.png) [@ghutchis](https://discuss.avogadro.cc/u/ghutchis)\ **Post date:** [October 28, 2025, 7:46pm UTC](https://discuss.avogadro.cc/t/orca-input-unavailable-after-1-102-1-update/7200/3 "2025-10-28T19:46:43Z")
Okay, I think this matches a bug report on GitHub: > > > \*\*Avogadro version: (please complete the following information from the About bo…x):\*\* > - Avogadrolibs: 1.102.1 > - Qt: 6.9.3 > > \*\*Desktop version: (please complete the following information):\*\* > - OS: Linux Gentoo > - Compiler gcc-16 > > \*\*Describe the bug\*\* > Since 1.102.1, a fresh install with pixi installed (no files in .cache or .local related to Avogadro or pixi) doesn't show scripts from inputGenerators in the plugin list. Pixi-env needs to be setup with any new plugin installed from the download manager. This is annoying with package from distrib that provides this plugin by default. > Without pixi installed, all scripts from input Generators are shown in a fresh install. There are two related bugs: - It should ask if you want to use `pixi` to run plugins and if so, create the default pixi environment. - If the default pixi environment doesn’t exist, it should just fall back to `python` by default I should be able to spin up a build tonight to handle this case and I’ll post a link here for the Windows installer. ---
**Author:** ![ghutchis](https://discuss.avogadro.cc/user_avatar/discuss.avogadro.cc/ghutchis/32/456_2.png) [@ghutchis](https://discuss.avogadro.cc/u/ghutchis)\ **Post date:** [October 29, 2025, 12:31am UTC](https://discuss.avogadro.cc/t/orca-input-unavailable-after-1-102-1-update/7200/4 "2025-10-29T00:31:16Z")
Okay, here’s the patch: > > > Fixes #2352 > > Developer Certificate of Origin > Version 1.1 > > Copyright (C) 200…4, 2006 The Linux Foundation and its contributors. > 1 Letterman Drive > Suite D4700 > San Francisco, CA, 94129 > > Everyone is permitted to copy and distribute verbatim copies of this > license document, but changing it is not allowed. > > > Developer's Certificate of Origin 1.1 > > By making a contribution to this project, I certify that: > > (a) The contribution was created in whole or in part by me and I > have the right to submit it under the open source license > indicated in the file; or > > (b) The contribution is based upon previous work that, to the best > of my knowledge, is covered under an appropriate open source > license and I have the right under that license to submit that > work with modifications, whether created in whole or in part > by me, under the same open source license (unless I am > permitted to submit under a different license), as indicated > in the file; or > > (c) The contribution was provided directly to me by some other > person who certified (a), (b) or (c) and I have not modified > it. > > (d) I understand and agree that this project and the contribution > are public and that a record of the contribution (including all > personal information I submit with it, including my sign-off) is > maintained indefinitely and may be redistributed consistent with > this project or the open source license(s) involved. I’ll post a link to the Windows installer once it finishes the build ~1 hour from now. ---
**Author:** ![ghutchis](https://discuss.avogadro.cc/user_avatar/discuss.avogadro.cc/ghutchis/32/456_2.png) [@ghutchis](https://discuss.avogadro.cc/u/ghutchis)\ **Post date:** [October 29, 2025, 1:30am UTC](https://discuss.avogadro.cc/t/orca-input-unavailable-after-1-102-1-update/7200/5 "2025-10-29T01:30:39Z")
Okay, here’s a link to that Windows build (which I think should be the new “nightly build” soon). Should solve your problem. [https://github.com/OpenChemistry/avogadrolibs/actions/runs/18893182107/artifacts/4400721911](https://github.com/OpenChemistry/avogadrolibs/actions/runs/18893182107/artifacts/4400721911)