-
-
Notifications
You must be signed in to change notification settings - Fork 344
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uninstalling and reinstalling Miniforge breaks all shells #164
Comments
Try running "conda init" again. |
Was this a bug with an older version of miniforge? This seems like a missing if statement in the ps hook. |
@hmaarrfk Sorry for the late reply, I was away. No I used the latest version available from this github page under Miniforge3 Installers, the one that ships with Python 3.9. By the way, I was able to restore functionality of the windows command prompt following this stackoverflow question: https://stackoverflow.com/questions/66335300/cmd-crashes-with-exit-code-1-after-uninstalling-anaconda However, I am still having lots of issues working with miniforge (see this issue); after many days having my development blocked from this I have to switch to something else, most likely a clean, standalone python install. |
This still can be reproduced by me. Steps to reproduce:
And fix it by
|
Part of the problem might be that according to my observations Uninstall-Miniforge3.exe is deleting content even after exe returned. |
Issue:
After transitioning from Anaconda to Miniforge, I had a few issues with VSCode and imports were broken. I decided to start from scratch again, and uninstalled both VSCode and Miniforge, cleaned up all files, and installed Miniforge again.
After installing I noticed a "Miniforge Prompt" in the start menu; i tried launching it, but nothing happened.
I would have expected a command prompt to open and have the base environment activated.
After that, I noticed that it seems ALL shells have been broken.
Windows Command Prompt has the same problem as Miniforge Prompt, namely it does not open at all.
Windows PowerShell opens, but throws an error at me saying "running scripts is disabled on this system".
I am at loss.
The text was updated successfully, but these errors were encountered: