![]() It was still possible for me to run bash scripts directly via a git bash installation: & "C:\Program Files\Git\bin\bash.exe". \npm -v didn't print anything (also no error). I reinstalled node.js and the PATH variable was configured correctly.īut opening a Powershell window in the directory C:\Program Files\nodejs and running. Typing node -v in PowerShell answered the node version, but npm -v didn't print anything (also no error). I hade the exact same problem as the question asker and noticed it first because npm was not working anymore after uninstalling Anaconda. I am just leaving this answer with some additional hints, phrases, and error messages (for SEO) so that others can find this answer via Google: Because Anaconda was already uninstalled, the script doesn't exist anymore and fails while crashing the CMD. The AutoRun value would probably run a custom command or script related to Anaconda. Open the registry key Computer\HKEY_CURRENT_USER\Software\Microsoft\Command Processor and delete the value AutoRun. As per Mike Nunan's comment, you can also edit the values rather than deleting the AutoRun if you still have Anaconda installed - just make sure to know where your Anaconda is installed.įor instance: the data of the Autorun value with string type could be if exist "C:\Anaconda3\condabin\conda_hook.bat" or if exist "C:\ProgramData\anaconda3\condabin\conda_hook.bat" etc. Restart computer to take registry modification in effect. Repeat for all Command Processor keys associated to all different users (the random numbers). ![]() In HKEY_USERS, something like HKEY_USERS/**RANDOM NUMBERS**/SOFTWARE/Microsoft/Command Processor will show up, delete ‘AutoRun’ entry. if ‘cmd /d’ opens normally, then fix I used is below.įix: With admin privilege in Registry Editor, search (CTRL+F) for ‘Command Processor’ keys. This should abnormally open and close immediately. My Error: command prompt opens and closes immediately following improper anaconda uninstall (uninstall throwed errors)ĭiagnostic: press WIN+R, type ‘cmd’. If you are in a corporate environment, the AutoRun of the active user will likely NOT be in HKCU\Software\Microsoft\Command Processor but in HKEY_USERS. Adding as an Answer to make it obvious to other people, who may miss Mike's comment. Actual requestĬan anyone help me with this issue please? I tried to look online for a week but with no luck,Ĭomment by Mike Nunan was key for me.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |