vscode: WinSCP: Code not working as external editor anymore

Issue Type: Bug

I just updated to the 1.31.0 release and now I’m not able to use Code as external editor within WinSCP anymore. (This worked just fine since the birth of VSCode)

Error: image (German for: The procedure entry point “??0TryCatch…” not found in DLL “C:\User…”)

WinSCP config: image The command is: "C:\Users\morgy\AppData\Local\Programs\Microsoft VS Code\Code.exe" !.! If I run this on CMD it works just fine, so I have no clue how to resolve this. Since it’s due to the 1.31.0 I tried it here first before blaming WinSCP. 😃

VS Code version: Code 1.31.0 (7c66f58312b48ed8ca4e387ebd9ffe9605332caa, 2019-02-05T22:35:56.624Z) OS version: Windows_NT x64 10.0.17763

System Info
Item Value
CPUs Intel® Core™ i7-8650U CPU @ 1.90GHz (8 x 2112)
GPU Status 2d_canvas: enabled
checker_imaging: disabled_off
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: disabled_software
rasterization: enabled
surface_synchronization: enabled_on
video_decode: enabled
webgl: enabled
webgl2: enabled
Memory (System) 15.93GB (10.10GB free)
Process Argv
Screen Reader no
VM 0%
Extensions (23)
Extension Author (truncated) Version
project-manager ale 10.3.2
vscode-multi-line-tricks big 0.0.3
htmltagwrap bra 0.0.7
vscode-toggle-quotes Bri 0.3.2
npm-intellisense chr 1.3.0
path-intellisense chr 1.4.2
bracket-pair-colorizer Coe 1.0.61
vscode-eslint dba 1.8.0
xml Dot 2.4.0
gitlens eam 9.5.0
prettier-vscode esb 1.8.1
php-debug fel 1.12.6
auto-rename-tag for 0.0.15
php-cs-fixer jun 0.1.95
debugger-for-chrome msj 4.11.1
indent-rainbow ode 7.2.4
vscode-versionlens pfl 0.22.0
nested-comments phi 2.2.6
vscode-fileutils sle 2.13.5
sensitive-replace vil 0.1.1
glean wix 4.5.0
change-case wma 1.0.0
markdown-all-in-one yzh 2.0.1

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Reactions: 1
  • Comments: 19 (8 by maintainers)

Most upvoted comments

I have one last idea to this. (Except asking the node team for the dll stuff) Recently I turned on the Windows Defender Ransomware Protection. Maybe that one broke the installation.

I’ll try a fresh installation without that protection.

@bpasero Let me quote:

If you need you may specify a command-line parameters for your editor. Use pattern !.! to specify where should WinSCP place name of the file to edit (quotes around filename containing spaces are added automatically). https://winscp.net/eng/docs/ui_editor_preferences#editor_type

So it’s basically the placeholder of the file to edit. Maybe something like "C:\Users\morgy\AppData\Local\Programs\Microsoft VS Code\Code.exe" C:\Users\morgy\AppData\Local\Temp\scp21773\var\www\vhosts\domain.com\index.php If I run this via cmd it opens up perfectly by the way.