vscode: Shell integration is being activated on Windows where conpty doesn't exist

Type: Bug

Hi, after recent VSCode update now when I open the terminal via workspace (clicking “Open in integrated terminal”) - it shows some weird line like “←]633;P;IsWindows=←]633;A←]633;P;Cwd=C:\x5cUsers\x5cserge\x5cDesktop\x5cProjects\x5cProjectsName\x5cProjectsName\x5cfrontendPS C:\Users\serge\Desktop\Projects\ProjectsName\ProjectsName\frontend> ←]633;” and then computer makes two sounds of the error.

It have never happened before and everything was working fine - VSCode would open a terminal with the correct path without errors.

I am pretty sure your wonderful team will fix this little bug. Thank you for making such an amazing product!

VS Code version: Code 1.75.0 (e2816fe719a4026ffa1ee0189dc89bdfdbafb164, 2023-02-01T15:23:45.584Z) OS version: Windows_NT x64 6.3.9600 Modes: Sandboxed: No

System Info
Item Value
CPUs AMD Ryzen 5 4500U with Radeon Graphics (6 x 2371)
GPU Status 2d_canvas: unavailable_software
canvas_oop_rasterization: disabled_off
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_renderer: enabled_on
video_decode: disabled_software
video_encode: disabled_software
vulkan: disabled_off
webgl: unavailable_software
webgl2: unavailable_software
webgpu: disabled_off
Load (avg) undefined
Memory (System) 7.42GB (3.50GB free)
Process Argv –crash-reporter-id 0e3365a3-6e74-4fc7-8263-fcd53ca490e7
Screen Reader no
VM 0%
Extensions (14)
Extension Author (truncated) Version
formatter-pug ale 0.0.1
es7-react-js-snippets dsz 4.4.3
prettier-vscode esb 9.10.4
auto-rename-tag for 0.1.10
code-beautifier mic 2.3.3
vetur oct 0.36.1
webgl-glsl-editor rac 1.3.3
vscode-xml red 0.24.0
LiveServer rit 5.7.9
markdown-preview-enhanced shd 0.6.7
vscode-scss-formatter sib 2.4.4
shader sle 1.1.5
autoimport ste 1.5.4
volar Vue 1.0.24
A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492:30256859
vstes627:30244334
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263cf:30335440
vscorecescf:30445987
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593cf:30376535
pythonvs932:30410667
cppdebug:30492333
vsclangdf:30486550
c4g48928:30535728
dsvsc012:30540252
azure-dev_surveyone:30548225
vscccc:30610679
pyindex848cf:30577861
nodejswelcome1cf:30587006
2e4cg342:30602488
f6dab269:30613381
pythonsymbol12:30657548

About this issue

  • Original URL
  • State: closed
  • Created a year ago
  • Comments: 17 (5 by maintainers)

Commits related to this issue

Most upvoted comments

←]633;P;IsWindows=←]633;A←]633;P;Cwd=C:\x5c Getting the same error after upgrade…? Help. Windows 8.1 (yeah I know I need to upgrade,… We’ve got computers 7, 8, 10 & 11 here)

… OK after looking into this a little more I believe my issue was my need to upgrade this terminal - I just don’t want the down time at the moment…

Anyways ConPTY requires Windows 10 (build 18309+) therefor fishing around in my terminal settings I set it to false.

settings.json “terminal.integrated.windowsEnableConpty”: false

Hope this helps somebody, cheers.