# Code.exe

Application Process: Microsoft Corporation

Also called code, vs code, visual studio code

Windows, Application

Visual Studio Code. Extra Code.exe rows are Electron helper, GPU, and extension hosts, not extra copies of Visual Studio.

## What you need to know

This is VS Code, an Electron editor. Visual Studio is devenv.exe.

Code.exe is Visual Studio Code. Electron starts GPU and extension-host processes with the same image name. devenv.exe is the full Visual Studio IDE and is a different product.

- **Safe?**: Yes, from VS Code

  **Is it Visual Studio?**: No. devenv.exe is Visual Studio

  **High CPU?**: File watcher or an extension

Feex says

If Code.exe is busy after I opened a huge repo, I would check the file watcher and extensions. I would not uninstall Visual Studio, because that is a different exe.

## What is Code.exe?

Code.exe is the Visual Studio Code desktop editor. It is Electron. Shared process names are a Chromium-family habit, not a second install.

## What does it do?

The main process owns windows. Extension Host runs extensions. A language server may be a different exe entirely, such as a node or rust-analyzer binary.

## Why is it running?

You opened a folder or a remote window. A Code.exe from a portable zip in Downloads is still VS Code if it is signed Microsoft, but the path will not be Program Files.

## Why are there multiple copies?

Main, GPU, renderer, and extension host. The Command Palette "Developer: Open Process Explorer" names them.

## Is it safe?

Usually safe

A Microsoft-signed Code.exe under Microsoft VS Code is the editor. Code.exe in a random tools folder can be a rename.

A legitimate copy normally runs from:

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

- User install is the default path
- System install uses Program Files\Microsoft VS Code
- Not devenv.exe

## Can I end it?

Closes the window and extensions

Ending the main process closes the editor. Ending only the extension host restarts extensions. Unsaved files live in VS Code backup, not in Windows.

## Can I remove it?

Uninstall VS Code

Use the VS Code uninstaller or Settings > Apps. Deleting Code.exe leaves the user data folder.

## Should it start with Windows?

VS Code can reopen folders at logon if Windows restored the window. That is session restore, not a service.

## Normal resource behavior

These are contextual labels, not universal averages.

- **CPU**: File watchers on huge trees and TypeScript servers are the usual spike

  **Memory**: Extensions and language services dominate

  **Disk**: Search and git status on large repos

  **Network**: Settings sync and remote-ssh

## File information

| Executable name        | Code.exe                                                           |
| ---------------------- | ------------------------------------------------------------------ |
| Common legitimate path | C:\Users\\\<you>\AppData\Local\Programs\Microsoft VS Code\Code.exe |
| Publisher              | Microsoft Corporation                                              |
| Signature expectation  | Signed by Microsoft Windows                                        |

## Common problems

### Watcher file handle limits

Microsoft documents watcher excludes. A node_modules tree can keep Code.exe busy without a syntax error.

### Confused with Visual Studio

Help articles that say "close Visual Studio" mean devenv.exe. This process is the lightweight editor.

## Troubleshooting

Diagnose before you change anything destructive.

### Run with extensions disabled

code --disable-extensions is the documented test. If CPU falls, the extension list is the article, not Windows.

### Open Process Explorer inside VS Code

It labels renderer versus extension host. Task Manager cannot.

## Technical details

Technical details

| Image name | Code.exe           |
| ---------- | ------------------ |
| Product    | Visual Studio Code |

## Related

These entities connect to this article. Type is shown on every link.

[Visual Studio Code: Application](https://feex.it/wiki/software/visual-studio-code)[When high CPU is normal: Guide](https://feex.it/wiki/software/system/when-high-cpu-is-normal)

## Sources and verification

Reviewed by Feex editorial. Last verified August 2026 Status: Feex Reviewed. [How we research](https://feex.it/wiki/research).

- [Microsoft: VS Code process model ](https://code.visualstudio.com/docs/supporting/troubleshoot-render-performance)· Extension host and GPU
- [Microsoft: VS Code system requirements ](https://code.visualstudio.com/docs/supporting/requirements)· Official editor docs
- [Foxhole process map ](https://foxhole.feex.it/)· First-party samples on Windows PCs. Not a lab benchmark.

## Was this article useful?

A yes or no is enough. Pick a reason if you want, or add a short note.

Quick facts

The short identity of this page. Specs, sources, and the full story stay in the article.

- **Type**: Application Process

  **Publisher**: Microsoft Corporation

  **Executable**: Code.exe

  **Parent app**: [Visual Studio Code](https://feex.it/wiki/software/visual-studio-code)

  **Mapped by Feex**: Seen on Windows PCs in Foxhole

Feex Reviewed: Last verified August 2026

---

Source: [Canonical Feex Wiki page](https://feex.it/wiki/process/code.exe/)

[Developer guide](https://feex.it/wiki/developers/) | [API policy](https://feex.it/developers/api-policy/) | [Agent guidance](https://feex.it/wiki/llms.txt)