CODEWITHSUNDEEP
reactjstypescriptvisual-studio-code
Uroš Milosavljević
Uroš Milosavljević

Reputation: 205

Visual Studio Code extensions stopped working suddenly

I'm having problem with my Visual Studio Code. Yesterday I had my pc shut down with VS Code open, and when I turned pc on again, all VS Code extensions stopped working. I'm using React and Typescript in my project and I really need those extensions. My eslint and prettier configurations also stopped working. If somebody had the same problem please answer.

Upvotes: 19

Views: 73388

Answers (8)

Marie Hekel
Marie Hekel

Reputation: 69

i too had a similar issue, and found (thru trial and error and multiple stackoverflow searches)

fix

  • toggle Developer Tools once you have vs code open
  • select the console tab
  • scroll thru the log, paying close attention to the red errors/ - if it's extension errors, open file explorer and go $drive:\Users\Yourname.vscode\extensions
  • delete any problem extensions
  • Restart VSCode and all should be well (at least for me it was)

cheers and happy coding :)

Upvotes: 6

Nicolas Corthorn
Nicolas Corthorn

Reputation: 1

In my case, my tests loaded again once I added the following line to .vscode/settings.json:

"python.experiments.enabled": false

For example, my settings.json files looks like this:

{
    "python.testing.pytestArgs": [
        "tests"
    ],
    "python.testing.pytestEnabled": true,
    "python.testing.unittestEnabled": false,
    "python.experiments.enabled": false
}

Upvotes: 0

Yuyo
Yuyo

Reputation: 61

This happened to me in the portable version (1.73.3). I deleted the extensions folder {vscode root}/data/extensions. Re-installing all extensions afterwards worked for me

Upvotes: 0

MarioG8
MarioG8

Reputation: 5931

I had this problem too. You can fix with the following:

  1. Open the command palette (Ctrl + Shift + P)
  2. Run Disable All Installed Extensions
  3. Then run Enable All Extensions.
  4. Restart Visual Studio Code

You can make sure again that the extensions are enabled.

Upvotes: 44

arda
arda

Reputation: 81

in my case removing "Todo Tree" plugin which is one of the VS Code plugins solved the problem,

https://marketplace.visualstudio.com/items?itemName=Gruntfuggly.todo-tree

if it is installed uninstall it and the problem will be solved

Upvotes: 3

Murungi Muhumuza
Murungi Muhumuza

Reputation: 121

Please check if you are able to turn on your settings sync. I had an issue like this and I couldn't even access the account option on vs code (the second last icon on the right horizontal panel.

If not (it's a long shot) try uninstalling vs code and reinstalling VS Code completely. I used these commands to do so (works for mac)

Upvotes: 0

dujiabao
dujiabao

Reputation: 1

It's weird. when I use WSL2 terminal opening Visual Studio Code, an exception occurs, expressing that wslCode.sh: 69.

But when I open Visual Studio Code in Windows, then type code . in WSL2 terminal, it works without an exception.

Upvotes: 0

Raul Pujol
Raul Pujol

Reputation: 17

I had that problem on WSL (Windows Subsystem for Linux). The error was like this:

/mnt/c/Users/Admin/.vscode/extensions/ms-vscode-remote.remote-wsl-0.63.13/scripts/wslCode.sh: 69: /home/raul/.vscode-server-server/bin/5554b12acf27056905806867f251c859323ff7e9/bin/code: not found

The solution was to go to Windows PowerShell and open Visual Studio Code, then go to the extensions and restart the Remote - WSL extension, and go back to WSL. It then started working immediately.

Upvotes: 2

Related Questions