Cannot open Visual Studio Code as Administrator (error code 18) in version 1.121.0
@deepak1556 is already working on this.
Since May 27, 2026.
Assessment
This issue has not been assessed yet.
Description
Type: Bug
- Install VS Code (system installer), latest version (1.121.0 as of writing).
- Open VS Code as administrator
Result: The window terminated unexpectedly (reason: 'launch-failed', code: '18')
We are sorry for the inconvenience. You can open a new empty window to start again.
Expected result: VS Code should open.
Workaround: Start VS Code with flag --disable-chromium-sandbox
VS Code version: Code 1.121.0 (f6cfa2ea2403534de03f069bdf160d06451ed282, 2026-05-19T11:51:53+02:00)
OS version: Windows_NT x64 10.0.17763
Modes:
System Info
| Item | Value |
|---|---|
| CPUs | Intel(R) Xeon(R) Gold 6246 CPU @ 3.30GHz (4 x 3292) |
| GPU Status | 2d_canvas: unavailable_software GPU0: VENDOR= 0x1414, DEVICE=0x008c [Microsoft Basic Render Driver], DRIVER_VENDOR=Google, DRIVER_VERSION=10.0.17763.8641 GPU1: VENDOR= 0x1414, DEVICE=0x008c [Microsoft Basic Render Driver], DRIVER_VERSION=10.0.17763.8641 Machine model name: Machine model version: direct_rendering_display_compositor: disabled_off_ok gpu_compositing: disabled_software multiple_raster_threads: enabled_on opengl: disabled_off rasterization: disabled_software raw_draw: disabled_off_ok skia_graphite: disabled_off trees_in_viz: disabled_off video_decode: disabled_software video_encode: disabled_software webgl: unavailable_software webgl2: unavailable_software webgpu: unavailable_software webnn: unavailable_software |
| Load (avg) | undefined |
| Memory (System) | 10.00GB (6.68GB free) |
| Process Argv | --disable-chromium-sandbox --crash-reporter-id 20477c75-1cc9-47c9-9278-1d2b6970aac1 |
| Screen Reader | no |
| VM | 100% |
Extensions (1)
| Extension | Author (truncated) | Version |
|---|---|---|
| powershell | ms- | 2025.4.0 |
- Dominant language
- TypeScript
- Stars
- 193k
- Forks
- 42.9k
- PR merge metrics
- PR metrics pending
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/vscode
-
testplan-item
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
new release
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
testplan-item
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
testplan-item
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
All issues in microsoft/vscode
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
vercel/react-tweet#225 ·