Replies: 8 comments 5 replies
-
same problem... |
Beta Was this translation helpful? Give feedback.
-
I am having the same issue. Vs Code was working fine for me, and then started throwing this error about 2 hours into my coding session. I did not install any packages, and I didn't even use the terminal. I was just using the debug code button to run my code, but then something changed and now it has stopped working. Pip is also having trouble installing packages now as well. I think it has something to do with the C:\Users\{username}\Documents\WindowsPowerShell\profile.ps1 profile that is managed by conda. But I wasn't changing anything in conda at the time, so I am completely clueless. I'm not even using localGPT (though I am doing stuff with local llms), but googling only lead me here, so here I am. |
Beta Was this translation helpful? Give feedback.
-
Same issue here, right after I installed the Github autocode thing |
Beta Was this translation helpful? Give feedback.
-
Temporary fix:As VS Code is first loading the terminal of your project, the error will show up almost immediately. But after a few moments, it will disappear for like three seconds. During the time where it is not present, type "pip" and press enter. For me, this prevents the error and returns my terminal to working order until I open a new terminal or reopen VS Code. As far as permanent fixes go, I suspected it was GitLens, since I had been fiddling with it around the time that the error showed up. But removing every non-required plugin still resulted in the error: |
Beta Was this translation helpful? Give feedback.
-
If you guys have cloned the repos into folders that have a hyphen in them, try removing hyphen from folder name. |
Beta Was this translation helpful? Give feedback.
-
Executing any command using PowerShell on VSCode now returns this error for me. Interestingly, when I use PowerShell on desktop or any other terminal on VSCode, it works fine. Any suggestions as to what the issue is? |
Beta Was this translation helpful? Give feedback.
-
try to choose default terminal -> enter the folder path of powershell in you pc and check if it works or not |
Beta Was this translation helpful? Give feedback.
-
Problem is likely with the Python extension and how it plays with environments (maybe conda specifically) - it was for me. Fix described here: TL;DR: switch the python extension to pre-release version and see if that helps. |
Beta Was this translation helpful? Give feedback.
-
Do you guys know how to fix this error?
Cannot find drive. A drive with the name '.C' does not exist.
At C:\Users\baek\OneDrive - HP Inc\Documents\WindowsPowerShell\profile.ps1:4 char:5
Beta Was this translation helpful? Give feedback.
All reactions