Starting VSCode in the current directory fails if using PowerShell on a network share #53764
Description
Issue Type: Bug
When using Powershell on an unmapped network share, you cannot start VSCode using the command "code ."
You'll get the error:
CMD.EXE was started with the above path as the current directory.
UNC paths are not supported. Defaulting to Windows directory.
There are ways to work around, but it is less fast then being able to use "start powershell here" from explorer, and then typing "code .".
VS Code version: Code 1.25.0 (0f080e5, 2018-07-05T13:11:58.697Z)
OS version: Windows_NT x64 10.0.16299
System Info
| Item | Value |
|---|---|
| CPUs | Intel(R) Core(TM) i7-6600U CPU @ 2.60GHz (4 x 2808) |
| GPU Status | 2d_canvas: enabled 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: disabled_software video_decode: enabled video_encode: enabled vpx_decode: unavailable_software webgl: enabled webgl2: enabled |
| Memory (System) | 7.93GB (1.22GB free) |
| Process Argv | C:\Program Files\Microsoft VS Code\Code.exe . |
| Screen Reader | no |
| VM | 0% |
Extensions (9)
| Extension | Author (truncated) | Version |
|---|---|---|
| pascal | ale | 0.11.0 |
| matlab | Gim | 0.9.0 |
| innosetup | idl | 1.0.3 |
| restructuredtext | lex | 65.0.0 |
| python | ms- | 2018.6.0 |
| cpptools | ms- | 0.17.6 |
| csharp | ms- | 1.15.2 |
| PowerShell | ms- | 1.7.0 |
| vscode-docker | Pet | 0.0.27 |