Code.exe

Application ProcessMicrosoft Corporation

Catalog search terms code, vs code, visual studio code

WindowsApplication

Visual Studio Code. Extra Code.exe rows na Electron helper, GPU, and extension hosts, no be extra copies of Visual Studio.

Wetin you need know

Dis na VS Code, an Electron editor. Visual Studio na devenv.exe.

Code.exe na Visual Studio Code. Electron dey start GPU and extension-host processes wit di same image name. devenv.exe na di full Visual Studio IDE and na different product.

E safe?: Check the running file path, signature, and publisher. Name alone no fit confirm say e safe.
Na Visual Studio?: No. devenv.exe na Visual Studio
High CPU?: A file watcher or extension fit contribute. Compare current activity before disabling extensions.

Feex tok say

If Code.exe dey busy after I open huge repo, I go check di file watcher and extensions. I no go uninstall Visual Studio, because dat one na different exe.

Wetin be Code.exe?

Code.exe na di Visual Studio Code desktop editor. Na Electron. Shared process names na Chromium-family habit, no be second install.

Wetin e dey do?

Di main process get windows. Extension Host dey run extensions. Language server fit be different exe entirely, like node or rust-analyzer binary.

Wetin make am dey run?

You open folder or remote window. Code.exe from portable zip inside Downloads still be VS Code if Microsoft sign am, but di path no go be Program Files.

Wetin make many copies dey?

Main, GPU, renderer, and extension host. Di Command Palette "Developer: Open Process Explorer" dey name dem.

Inspect the running instance

Inside Windows PowerShell, this read-only query show matching process IDs, creation times and executable paths on this PC. (pcm)

Get-CimInstance -ClassName Win32_Process | Where-Object { $_.Name -eq 'Code.exe' } | Select-Object ProcessId, ParentProcessId, CreationDate, Name, ExecutablePath | Format-List

No result or a path we no fit access is inconclusive. Protected processes fit restrict access, and process IDs fit be reused. Keep personal paths local. (pcm)

Use the file-identity guide to compare signatures and product metadata. A filename alone no fit establish safety. (pcm)

E dey safe?

Check dis running file

Microsoft-signed Code.exe under Microsoft VS Code na di editor. Code.exe inside random tools folder fit be rename.

Compare the recorded location with the actual file. A familiar folder alone no fit establish identity. (pcm)

C:\Users\<you>\AppData\Local\Programs\Microsoft VS Code\Code.exe

User install na di default path
System install dey use Program Files\Microsoft VS Code
No be devenv.exe

I fit end am?

E dey close di window and extensions

To end di main process dey close di editor. To end only di extension host dey restart extensions. Unsaved files dey live inside VS Code backup, no be inside Windows.

I fit comot am?

Uninstall VS Code

Use di VS Code uninstaller or Settings > Apps. To delete Code.exe dey leave di user data folder.

E suppose start with Windows?

VS Code fit open folders again during logon if Windows restore di window. Dat one na session restore, no be service.

Measure resource use

Measure the current process rather than assume a universal baseline
CPU and memory	Compare several observations for the same PID and workload. This entry get no independently measured universal baseline. (pcm)
Disk and network	Attribute activity to the actual process and current task; a filename alone no fit establish expected destinations or transfer volume. (pcm)

File information

Code.exe file information
Executable name	Code.exe
Recorded installation path	C:\Users\<you>\AppData\Local\Programs\Microsoft VS Code\Code.exe
Publisher	Microsoft Corporation
Signature check	Inspect the actual file; this entry no dey certify its certificate identity. (pcm)

Common wahala dem

Watcher file handle limits

Microsoft document watcher excludes. node_modules tree fit keep Code.exe busy without syntax error.

Confused wit Visual Studio

Help articles wey talk say "close Visual Studio" mean devenv.exe. Dis process na di lightweight editor.

How to troubleshoot

Diagnose before you change anything wey fit scatter things.

Run wit extensions disabled

code --disable-extensions na di documented test. If CPU drop, di extension list na di article, no be Windows.

Open Process Explorer inside VS Code

E dey label renderer versus extension host. Task Manager no fit.

Technical details

Code.exe technical details
Image name	Code.exe
Product	Visual Studio Code

Check the identity of running file

A filename alone no fit establish safety. Verify the actual path, signature and product identity. (pcm)

Sources and verification

Recorded source label: August 2026. Dis label no establish independent verification. How we dey do research.

Microsoft: VS Code process model · Extension host and GPU
Microsoft: VS Code system requirements · Official editor docs
Foxhole process map · First-party samples on top Windows PCs. No be lab benchmark.
Microsoft Sysinternals: Sigcheck · Dey explain how to check file signatures. Dis reference no establish the identity or safety of any particular running file.
Microsoft: Get-CimInstance · Read-only local process-query method. (pcm)
Microsoft: Win32_Process properties · Documents process IDs, executable paths, creation dates and parent-ID reuse. (pcm)

Dis article make sense to you?

Yes or no dey enough. Choose reason if you want, or add short note.