Vscode: Visual studio code stopped working after latest update. Tried uninstall and reinstall still not working

[vsawant1608]

[vsawant1608]

OS :- Windows 7
VS code setup file used :- VSCodeUserSetup-x64-1.26.1

[n8harmon]

I uninstalled the latest update and reverted back to 1.25: https://code.visualstudio.com/updates/v1_25 and I'm back up and running.

[joaomoreno]

@vsawant1608 What happens when you try running it?

[n8harmon]

@joaomoreno I can't speak for @vsawant1608, but I can tell you the steps that triggered the problem for me as well as the steps I took to troubleshoot it.

1. I installed the 1.26.1 update suggested when I opened up VS Code
2. I waited for the application to open back up after the installation completed, but it did not auto-restart
3. I attempted to start the application by running code from the command line.
4. I attempted to manually start the application by clicking on the code.exe file, and even tried starting it with elevated permissions

Each time I attempted to start the application, nothing happened, so I began further troubleshooting:

1. I searched the application logs for errors, but could not find anything out of the ordinary, so
2. I rebooted my system just to ensure a restart didn't resolve the problem
3. I downloaded the latest Windows installer from here: https://code.visualstudio.com/download (VSCodeUserSetup-x64-1.26.1.exe)
4. I uninstalled VS Code and reinstalled using the above installer, and I continued to experience the same problems, so
5. I uninstalled VS Code again and then downloaded and installed 1.25 from the installer found here: https://code.visualstudio.com/updates/v1_25

I'm currently running on version 1.25 without any issues. Now that I'm looking closer at the latest download page I wonder if this has anything to do with the User installer vs the System installer. I don't have time at the moment to test out whether the same problem occurs with the System installer, but if I'm able to before you find a resolution to this problem, I'll report back my findings.

[vsawant1608]

@joaomoreno I faced the exact issue as described by @n8harmon . I just took latest update as suggested by vs code update notification. It did nots tart the visual code automatically. So I went and manually tried to start the vs code. however nothing happened.

I then restarted the system and tried opening vscode again. nothing happend.

I installed previous version and it worked. For that previous version also I tried taking the update and ended up with same situation.

[archturtle]

I'm on v1.27 on Insiders and i am having the problem where intellisense doesn't even show up

Edit: I have disabled all my extensions and tried it, still seems like it doesn't want to work.

[joaomoreno]

I uninstalled VS Code and reinstalled using the above installer, and I continued to experience the same problems, so

@n8harmon This is interesting. Can you try this, but this time run it in a command line with code --verbose?

[n8harmon]

@joaomoreno I ran code --verbose prior to running the update again and received the following output:

[main 5:04:13 PM] Sending env to running instance...
[main 5:04:13 PM] Sending some foreground love to the running instance: 6280
[main 5:04:13 PM] Sent env to running instance. Terminating...
[main 5:04:13 PM] Lifecycle#kill()

I then ran the 1.26.1 update and executed the code --verbose command again. The application did not start nor was there any output on the command line. I went ahead and uninstalled and reinstalled with the system installer and received the same results. I've reverted back to 1.25.1 again and everything is back to normal now.

[joaomoreno]

received the same results

These results are what Code returns if there's already a Code instance running. Can you restart your system, to be sure there's no Code running?

[SKKOVVURI]

Same results like everybody mentioned above.. No output for code --verbose with vscode x64 1.26.1.
No other instance of code.exe running on my Win7. Also restarted the system but didn't help.

PS C:\Users\skovvuri> code --verbose
PS C:\Users\skovvuri>

[joaomoreno]

@SKKOVVURI Can you completely reinstall VS Code and try again?

@n8harmon Still waiting on a reply.

[darekkay]

I did exactly the same as n8harmon described (except that I did not downgraded, yet).
Latest VS Code version won't start, both "regular" and "user" versions. code --verbose does not print anything. I did a clean install/reboot and confirmed that no (other) code instance is running.

Maybe this helps debugging the issue: I'm having exactly the same problem with Slack Desktop app version 3.1.0 and up. Nothing happens when the app is started. Slack 3.0.5 is the last working version. I'm only mentioning it, as both VSCode and Slack use Electron under the hood, so this might be connected.
Additionally, the issue occurs only on Windows 7 (but for everyone on my team using this OS). I've had no issues on Windows 10 so far.

[joaomoreno]

cc @bpasero Seems strange...

[bpasero]

@darekkay any difference if you directly execute code.exe instead of our link?

[darekkay]

@bpasero There is no difference using:

• Visual Studio Code.lnk on the desktop
• Code.exe in the app folder
• Code.exe --verbose in command line
• Code.exe --verbose in command line with admin rights
• Code.exe --verbose in PowerShell
• Code.exe --verbose in Git Bash

I sometimes see Code.exe appear in the Windows Task Manager for a split of a second, but mostly not even that.

[bpasero]

I wonder if this is a crash in native code. Can you please follow the steps in https://github.com/Microsoft/vscode/wiki/Native-Crash-Issues to get at more details around the crash and attach the result here? Thanks!

[darekkay]

There you go:

vscode-crash-log.txt

[bpasero]

@darekkay great, any chance there is a stacktrace or more logs to look at?

[darekkay]

Unfortunately, that's all I've got in my Logs\Crash... folder. I followed the linked guide, but instead of selecting the Code.exe process I just typed it into the input field (as the process never runs to select it from the list). But this rule still creates to attached log files.

[bpasero]

@darekkay how about running VSCode from a zip archive directly: download

[darekkay]

Sorry, no difference here (both 32 and 64 bit) :disappointed:

However, after trying to start Code.exe a few more times, I got twice a Crash Log including an exception (this was not connected to a specific version):

vscode-crash-log-with-exception.txt

[bpasero]

@darekkay thanks, I just searched for that exception and some forum suggests to uninstall a software called EasyConnect, do you happen to have that installed?

[darekkay]

No, I don't have it installed.
However, this is a corporate laptop and assuming this issue is not reproducable for most people, it might be some pre-installed software interfering here.

[bpasero]

Ok was worth a try ;)

[aeciolevy]

So far on Mac OS X subtleBrackets is broken with 1.26.1 version.

[SKKOVVURI]

@joaomoreno I completely uninstalled and reinstalled .. Didn't help.. But once I installed old version it works fine.

[darekkay]

I decided to downgrade to 1.25.1, too, with no issues so far.
I hope this issue gets resolved, but I can understand how hard it is, when the maintainers cannot reproduce the problem and we can't offer anything more than "it does nothing" :disappointed:

[bpasero]

We are building exploration builds that use a much newer version of Electron (our UI framework). I wonder if this issue reproduces with one of these builds, could you try? Download:

• Windows: Download
• macOS: Download
• Linux: Download

[darekkay]

The issue still exists in this version

[SebastianMCarreira]

I was just running with1.27 and found a very similar issue.

Reinstalled VS because I wanted to have the context menu options I forgot to tick when I installed it in my PC some days ago. After the reinstalling, the issue started.

The window did open but in some ocassions the nonly the gray background was loaded, other times, alse the bottom purple line and the left lighter bar loaded too but nothing else. The process also spiked my CPU usage for 25% (I7-7700) without doing anything else. Tried running code --disable-extensions but still the same. Running code --verbose showed a lot of errors of the program trying to read non existant files in the logs directory. Tried deleting the whole code directory in roaming but didn't help. Also tried code --verbose --disable-extensions and had the exact same output @n8harmon had. All this was done in Win 10 with the cmd with administrator privileges.

I have just installed 1.25 and it works just fine. Hope the issue gets fixed soon.

[keeborg]

I've got the same issue as SebastianMCarreira above. Uninstalled 1.27.0 version and installed 1.25. Hope the issue will be fixed.

[bpasero]

I wonder if this is the same as https://github.com/Microsoft/vscode/issues/47883. Do people have non-ASCII characters in their username?

[darekkay]

@bpasero I have only letters and _ in my user name. But the reported issue is slightly different from the last comments anyway (we get no output at all for code --verbose).

[bpasero]

Yeah true story.

[ndite]

Same issue here. It doesn't start, regardless of shortcut, executable or "code --verbose" with no output. (Win 7 Pro)

It happened with 1.26.1 as well tried now 1.27.1. I'm back to 1.25 for now...

[tigerscar]

True for me, too. There are different instances of Code running in Windows Task Manager (Win 7 Pro). But no VS Code is currently visible in Windows. Each execution starts another process which different sizes. This behaviour started with 1.26.1, where I followed the instruction to use the new installer instead to update. Then I manually installed the 1.27.2 installer but ending up in the same error.

I have to restart my machine now, to start it once. But every invocation from the Windows Explorer context menu is failing shortly after closing it. Maybe it starts up one code instance per installed Extension to check for updates?

I am able to kill all processes without one. One is remaining and can't be killed.

[tigerscar]

Now there is the same problem with the 1.25.1 version of Visual Studio Code. The same Code.exe zombies in the Windows Task Manager as before. Any news about this topic?

Also my Powershell Plugin is no more working in 1.25.1!

[enisdenjo]

What happened to me is:

1. cmd + Q to shutdown VSCode
2. Immediately after VSCode closed, mac abruptly logged out (logout crash?)
3. Logged back in, VSCode crashes on start... No logs with --verbose or any other flag (--disable-extensions, --disable-gpu, etc.)

Visual Studio Code - Exploration starts without problems, however no extensions, presets, configs, nothing...

EDIT 1:

Opened Activity Monitor; saw Electron running (wasn't cogging up resources, averagely idling); Force Quit that baby; kernel panic, macOS crashes completely, reboot...

Bam, VSCode works again, everything back to normal.

Crash dump:

Anonymous UUID:       C8747503-14C0-AEC0-BE62-5ED21D9FE862

Tue Oct  2 19:47:30 2018

*** Panic Report ***
panic(cpu 2 caller 0xffffff7fa63f6a0f): "GPU Panic: mux-regs 4 3 7f 0 0 0 severity 3 WS-ready 1 switch-state 0 IG FBs 1 EG FBs 0:0 power-state 3 3D busy HDA idle : AGC GPU REGISTER RESTORE FAILED : rdar://7254528, VendorID invalid\n"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleGraphicsControl/AppleGraphicsControl-3.18.52/src/AppleMuxControl/kext/GPUPanic.cpp:162
Backtrace (CPU 2), Frame : Return Address
0xffffff921259ba90 : 0xffffff8024e6d166 
0xffffff921259bae0 : 0xffffff8024f95824 
0xffffff921259bb20 : 0xffffff8024f87b10 
0xffffff921259bba0 : 0xffffff8024e1f180 
0xffffff921259bbc0 : 0xffffff8024e6cbdc 
0xffffff921259bcf0 : 0xffffff8024e6c99c 
0xffffff921259bd50 : 0xffffff7fa63f6a0f 
0xffffff921259bdb0 : 0xffffff7fa63f320e 
0xffffff921259bdf0 : 0xffffff7fa63f6483 
0xffffff921259be30 : 0xffffff802549ef0c 
0xffffff921259bea0 : 0xffffff802549ee36 
0xffffff921259bed0 : 0xffffff8024ea67e4 
0xffffff921259bf40 : 0xffffff8024ea6345 
0xffffff921259bfa0 : 0xffffff8024e1e4f7 
      Kernel Extensions in backtrace:
         com.apple.driver.AppleMuxControl(3.18.52)[971DAA01-FE8B-39AD-BCFE-9BB81DCA55CD]@0xffffff7fa63e8000->0xffffff7fa63fafff
            dependency: com.apple.driver.AppleGraphicsControl(3.18.52)[6A280175-7E90-3F8B-BFE2-3C181C222BD9]@0xffffff7fa63a8000
            dependency: com.apple.iokit.IOACPIFamily(1.4)[95DA39BB-7C39-3742-A2E5-86C555E21D67]@0xffffff7fa5756000
            dependency: com.apple.iokit.IOPCIFamily(2.9)[1057F053-73DE-33E4-B5BE-09DA28715DB4]@0xffffff7fa5694000
            dependency: com.apple.iokit.IOGraphicsFamily(519.19)[0B3857C5-9040-3A0C-BFB4-C45E56DB01C6]@0xffffff7fa6001000
            dependency: com.apple.AppleGraphicsDeviceControl(3.18.52)[FC5E4CD4-7730-3A55-9CC5-338A64F50E42]@0xffffff7fa6399000

BSD process name corresponding to current thread: kernel_task

Mac OS version:
17F77

Kernel version:
Darwin Kernel Version 17.6.0: Tue May  8 15:22:16 PDT 2018; root:xnu-4570.61.1~1/RELEASE_X86_64
Kernel UUID: CC1699EE-71B5-3AF1-AAA3-6DBD16222B92
Kernel slide:     0x0000000024c00000
Kernel text base: 0xffffff8024e00000
__HIB  text base: 0xffffff8024d00000
System model name: MacBookPro8,3 (Mac-942459F5819B171B)

System uptime in nanoseconds: 118736563735385
last loaded kext at 104493578356423: com.apple.macos.driver.AppleUSBEthernetHost    8.1.1 (addr 0xffffff7fa8fca000, size 49152)
last unloaded kext at 113336261301216: com.apple.macos.driver.AppleUSBEthernetHost  8.1.1 (addr 0xffffff7fa8fca000, size 24576)

EOF
Model: MacBookPro8,3, BootROM MBP81.0050.B00, 4 processors, Intel Core i7, 2.2 GHz, 16 GB, SMC 1.70f6
Graphics: Intel HD Graphics 3000, Intel HD Graphics 3000, Built-In
Graphics: AMD Radeon HD 6750M, AMD Radeon HD 6750M, PCIe
Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x0198, 0x393955353432382D3031382E4130304C4620
Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x0198, 0x393955353432382D3031382E4130304C4620
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xD6), Broadcom BCM43xx 1.0 (5.106.98.102.30)
Bluetooth: Version 6.0.6f2, 3 services, 18 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en1
Serial ATA Device: Samsung SSD 840 EVO 500GB, 500.11 GB
Serial ATA Device: MATSHITADVD-R   UJ-898
USB Device: USB 2.0 Bus
USB Device: FaceTime HD Camera (Built-in)
USB Device: Hub
USB Device: BRCM2070 Hub
USB Device: Bluetooth USB Host Controller
USB Device: Apple Internal Keyboard / Trackpad
USB Device: USB 2.0 Bus
USB Device: Hub
USB Device: IR Receiver
Thunderbolt Bus: MacBook Pro, Apple Inc., 22.1

EDIT 2:
VSCode version v1.27.2

[tigerscar]

This problem could be an issue of our corporate endpoint security. This morning an Firefox update also ended in an non-killable process after applying an update. Have to research more.

[atticusmiles]

Ran into this problem since 1.26.0, problem still exists in 1.28.
code --verbose shows no message
back to 1.25.1..

[tigerscar]

Our IT department informed me about a folder, which is excluded from the scan functionality of the endpoint security. I installed 1.28.2 in there. Currently without any problem. This seems to fix this issue for me.

[hossmf]

I have the same issue with v1.28.2

[LiEyWe]

I experience the same issue after updating to 1.29.1
Going back to an older version doesn't fix the issue.

[MA-Norouzifar]

same issue and can't fix it

https://github.com/Microsoft/vscode/issues/64064

i very very bad and no one answer me or tell me how can i fixed it

[hossmf]

I have the same issue with v1.28.2

The last problem is fixed with 1.29 but now it doesn't open when there is no internet connection. 😂

[jonathan-zageno]

I don't know which version I had installed, but this morning I couldn't start code on OSX any longer. So I went back to version 1.25.1 and it works fine.

Confirming that the issue is with 1.29.1

[manztihagi]

Seems has a problem on me also, I use 1.29.1 and sometimes all plugins off even intellisense not working also. need to restart then back to normal.

but this is very disturbing for me when do coding then all function was stopped.
I think have to revert to old version 1.25.1

OS: MacOS Mojave

[jonathan-zageno]

For me 1.28.2 works.

[manztihagi]

@bpasero : I've been trying for vs code exploration for mac, unfortunately the problem still persist with regular vscode ... all plugins suddenly off including intellisense.

@jonathan-zageno where i can get that version ?

[bpasero]

If anyone has Cylance Antivirus running on macOS, crashes can be explained (see https://github.com/Microsoft/vscode/issues/62628)

[jonathan-zageno]

@manztihagi if you type code --version in the command line you'll get the version.

[MA-Norouzifar]

I think we should install version 1.25 . This version work perfectly.. and we should wait for new year to get new stable of visual studio code with electron version 3

I don't know why visual studio code teams don't solved this problem ...!!?

[GbolahanA]

I have the same issue with 1.30.1 but apparently it opens as long as there's an Internet connection otherwise it doesn't. All this after uninstalling and then reinstalling only to find out that it needed an Internet connection as @hossmf said

[TheKamakaZi]

I recently started running into a similar problem, but do have some output from code --version:

[main 7:00:12 PM] Error: [UriError]: If a URI contains an authority component, then the path component must either be empty or begin with a slash ("/") character at C:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\code\electron-main\main.js:74:478 at t.e (C:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\code\electron-main\main.js:74:792) at new t (C:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\code\electron-main\main.js:76:307) at t.e.with (C:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\code\electron-main\main.js:75:521) at Object.t.normalizePath (C:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\code\electron-main\main.js:88:339) at e.parseUri (C:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\code\electron-main\main.js:462:72) at e.doGetWindowsFromLastSession (C:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\code\electron-main\main.js:461:243) at e.getPathsToOpen (C:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\code\electron-main\main.js:459:410) at e.open (C:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\code\electron-main\main.js:453:185) at t.openFirstWindow (C:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\code\electron-main\main.js:499:565) at C:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\code\electron-main\main.js:495:66 at t.e.invokeFunction (C:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\code\electron-main\main.js:220:247) at C:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\code\electron-main\main.js:495:30 at n.Class.define.cancel.then (C:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\code\electron-main\main.js:108:201) at C:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\code\electron-main\main.js:494:959 at n.Class.define.cancel.then (C:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\code\electron-main\main.js:108:201) at t.startup (C:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\code\electron-main\main.js:494:385) at C:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\code\electron-main\main.js:506:508 at Object.v [as _notify] (C:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\code\electron-main\main.js:101:572) at Object.enter (C:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\code\electron-main\main.js:104:924) at n.Class.derive._creator._run (C:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\code\electron-main\main.js:106:790) at n.Class.derive._creator._completed (C:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\code\electron-main\main.js:106:231) at <anonymous> at process._tickCallback (internal/process/next_tick.js:188:7) [main 7:00:12 PM] Lifecycle#kill() [main 7:00:12 PM] telemetry/optInStatus { optIn: true } [main 7:00:12 PM] telemetry/update:win32SetupTarget { target: 'system' }

Version info:
>code --version 1.29.1 bc24f98b5f70467bc689abf41cc5550ca637088e ia32

[jryannel]

For me it seems an old instance was running. On Mac use activity monitor (or htop) to search for processes named "code". You should see a bunch of code helper processes. Kill them one by one. I used htop for this *F4 Filter" and then "F9 Kill".

Afterwards vscode opens again. For me at least:-)

$ code --version
1.30.1
dea8705087adb1b5e5ae1d9123278e178656186a
x64

[ebukab]

hey this helped me . Go to the extensions tab , click on an extension (preferably one of less importance ) , disable the extension , then press the reload button to reload vscode again . This worked for me

[bpasero]

I am closing this issue as there is no actionable change for VSCode.