InvokeAI
InvokeAI copied to clipboard
[bug]: I get an error when trying to open invoke.bat
Is there an existing issue for this?
- [X] I have searched the existing issues
OS
Linux
GPU
cuda
VRAM
8GB
What happened?
I reinstalled invokeAI and got this error when I open Invoke.bat
CommandNotFoundError: Your shell has not been properly configured to use 'conda activate'.
If using 'conda activate' from a batch script, change your
invocation to 'CALL conda.bat activate'.
To initialize your shell, run
$ conda init <SHELL_NAME>
Currently supported shells are:
- bash
- cmd.exe
- fish
- tcsh
- xonsh
- zsh
- powershell
See 'conda init --help' for more information and options.
IMPORTANT: You may need to close and restart your shell after running 'conda init'.
Do you want to generate images using the
1. command-line
2. browser-based UI
3. open the developer console
Please enter 1, 2 or 3:
when I try to open the webui or line command, the window closes.
Screenshots
No response
Additional context
No response
Contact Details
No response
I have the same issue. OS: Windows 11
Same issue on Windows 11
I'm trying this on windows 10 I have another error:
Traceback (most recent call last):
File "C:\Users\name\invokium\invokeAI\scripts\invoke.py", line 3, in <module>
import ldm.invoke.CLI
ModuleNotFoundError: No module named 'ldm'
does anyone have the same error?
I just reinstalled it with anaconda3, I guess it works now but only from conda. I now have a new problem, how do I open it up in one click? I have to open up an anaconda3 prompt and type in 'conda activate invokeai' and 'python scripts\invoke.py --web' in order for it to open the webui.
Had the same problem. It will start when you add this line to the invoke.bat file prior to the "call conda activate invokeai" line:
call C:\Users\YourUserName\anaconda3\Scripts\activate.bat C:\Users\YourUserName\anaconda3 call conda activate invokeai
Replace YourUserName with your Windows Login name. It should point to your Anaconda location.
I had this problem too and it was a simple solution for me... Just restarted windows and bam, it now works