[bug]: Install script doesn't work
Is there an existing issue for this?
- [X] I have searched the existing issues
OS
Windows
GPU
cuda
VRAM
8GB
What happened?
When I tried to run install.bat, I got this error. I also get 4 "This app can't run on your pc" errors.
edit: I also tried to run this as an administrator and with disabled av
"InvokeAI source installer..."
""
"Some of the installation steps take a long time to run. Please be patient."
"If the script appears to hang for more than 10 minutes, please interrupt with control-C and retry."
"<Press any key to start the install process>"
Press any key to continue . . .
""
"Downloading micromamba from https://github.com/cmdr2/stable-diffusion-ui/releases/download/v1.1/micromamba.exe to C:\image_generation\InvokeAI\installer_files\mamba\micromamba.exe"
A subdirectory or file C:\image_generation\InvokeAI\installer_files\mamba already exists.
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (56) Failure when receiving data from the peer
Micromamba version:
Access is denied.
Access is denied.
"Packages to install: conda"
Access is denied.
"There was a problem while installing conda using micromamba. Cannot continue."
Press any key to continue . . .
Screenshots

Additional context
No response
Contact Details
No response
i have exactly the same error
I had this error, too. but somehow it installed after a few tries.
To fix edit the install.bat file. locate the line: call curl -L "%MICROMAMBA_DOWNLOAD_URL%" > "%MAMBA_ROOT_PREFIX%\micromamba.exe" change it to: call curl --ssl-no-revoke -L "%MICROMAMBA_DOWNLOAD_URL%" > "%MAMBA_ROOT_PREFIX%\micromamba.exe" save and run. it should now work.
Yep, it seems to fix the issue, but why it's working and why it's not implemented in InvokeAI?
I tried this, but now have another error: "There was a problem while installing conda git using micromamba. Cannot continue."
I'm using Windows 11
There has been no activity in this issue for 14 days. If this issue is still being experienced, please reply with an updated confirmation that the issue is still being experienced with the latest release.