Visual Studio Code powershell terminal display is broken #833

HyundongHwang · 2017-06-06T14:52:00Z

System Details

windows version :
windows 10 (Microsoft Windows NT 10.0.15063.0)
VS Code version :
version 1.12.2
commit 19222cdc84ce72202478ba1cec5cb557b71163de
date 2017-05-10T13:20:36.315Z
vscode-powershell version :
1.2.1

PS C:\WINDOWS\system32> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      5.1.15063.296
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.15063.296
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

PS C:\Users\hhd20> code -v
1.12.2
19222cdc84ce72202478ba1cec5cb557b71163de
PS C:\Users\hhd20> code --list-extensions --show-versions
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
PS C:\Users\hhd20>

Issue Description

I have the following problem.

I am using VisualStudioCode with powershell, and the line breaks as shown below.

Do you have any idea why?

VisualStudioCode Version:

My settings file:

{
    "editor.fontFamily": "D2Coding",
    "editor.fontSize": 14,
    "editor.wordWrap": "on",
    "editor.mouseWheelZoom": true,
    "window.reopenFolders": "none",
    "workbench.colorTheme": "Visual Studio Dark",
    "workbench.welcome.enabled": false,
    "window.zoomLevel": 0,
    "editor.cursorStyle": "line-thin",
    "terminal.integrated.shell.windows": "C:\\Windows\\SysWOW64\\WindowsPowerShell\\v1.0\\powershell.exe"
}

Attached Logs

The logs directory did not exist.

The text was updated successfully, but these errors were encountered:

daviwil · 2017-06-06T14:57:28Z

Hey @HyundongHwang, have you tried the Visual Studio Code Insiders release? I think I saw a fix for this issue being worked on there. If it doesn't work with that build, let me know and I'll investigate.

HyundongHwang · 2017-06-06T15:06:30Z

@daviwil
I installed vscode insider as you said.
But the problem is continuing in a different way.

daviwil · 2017-06-06T15:11:32Z

Hey @Tyriar, do you know if there's a solution to the integrated terminal rendering issue shown in the screenshot @HyundongHwang posted here?

@HyundongHwang can you give us the output when you run this command in the terminal:

chcp

HyundongHwang · 2017-06-06T15:18:52Z

@daviwil, @Tyriar

I do not know very well, but codepage seems to be a clue.

Copyright (C) 2016 Microsoft Corporation. All rights reserved.

PS C:\Users\hhd20> chcp
활C:\U성 코드 페이지: 949                                                           PS C:\U

활C:\U성 코드 페이지 is activated code page in english.

daviwil · 2017-06-06T15:21:47Z

Thanks! Does the output improve after you enter this command?

chcp 65001

If so, you might consider making it part of your PowerShell profile so that it gets loaded when you start up PowerShell.

HyundongHwang · 2017-06-06T16:24:07Z

@daviwil, @Tyriar

Changing the codepage does not solve the problem.
First, I'll show you the problem screen shot below.
(I think the screen shot is better than the text capture because it is a UI problem)

There is an additional problem.
In the powershell environment of vscode, profile.ps1 is not loaded.
Because of this, adding the chcp 65001 syntax to profile.ps1 is no longer useful.
(But it loads well in the outside powershell environment.)
I am looking at profile.ps1 in the system32 directory for the sake of understanding the phenomenon. Surprisingly, the results from vscode and outside are different!
Query results in the vscode environment show that profile.ps1 does not exist. Is vscode capable of caching the environment?

vscode's powershell

Windows PowerShell
Copyright (C) 2016 Microsoft Corporation. All rights reserved.

PS C:\Users\hhd20> $pshome
C:\Windows\System32\WindowsPowerShell\v1.0
PS C:\Users\hhd20> ls C:\Windows\System32\WindowsPowerShell\v1.0 | select fullname

FullName
--------
C:\Windows\System32\WindowsPowerShell\v1.0\en
C:\Windows\System32\WindowsPowerShell\v1.0\en-US
C:\Windows\System32\WindowsPowerShell\v1.0\Examples
C:\Windows\System32\WindowsPowerShell\v1.0\ko
C:\Windows\System32\WindowsPowerShell\v1.0\ko-KR
C:\Windows\System32\WindowsPowerShell\v1.0\Modules
C:\Windows\System32\WindowsPowerShell\v1.0\Schemas
C:\Windows\System32\WindowsPowerShell\v1.0\SessionConfig
C:\Windows\System32\WindowsPowerShell\v1.0\Certificate.format.ps1xml
C:\Windows\System32\WindowsPowerShell\v1.0\Diagnostics.Format.ps1xml
C:\Windows\System32\WindowsPowerShell\v1.0\DotNetTypes.format.ps1xml
C:\Windows\System32\WindowsPowerShell\v1.0\Event.Format.ps1xml
C:\Windows\System32\WindowsPowerShell\v1.0\FileSystem.format.ps1xml
C:\Windows\System32\WindowsPowerShell\v1.0\getevent.types.ps1xml
C:\Windows\System32\WindowsPowerShell\v1.0\Help.format.ps1xml
C:\Windows\System32\WindowsPowerShell\v1.0\HelpV3.format.ps1xml
C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
C:\Windows\System32\WindowsPowerShell\v1.0\PowerShellCore.format.ps1xml
C:\Windows\System32\WindowsPowerShell\v1.0\PowerShellTrace.format.ps1xml
C:\Windows\System32\WindowsPowerShell\v1.0\powershell_ise.exe
C:\Windows\System32\WindowsPowerShell\v1.0\powershell_ise.exe.config
C:\Windows\System32\WindowsPowerShell\v1.0\profile.ps1_old
C:\Windows\System32\WindowsPowerShell\v1.0\PSEvents.dll
C:\Windows\System32\WindowsPowerShell\v1.0\pspluginwkr.dll
C:\Windows\System32\WindowsPowerShell\v1.0\pwrshmsg.dll
C:\Windows\System32\WindowsPowerShell\v1.0\pwrshsip.dll
C:\Windows\System32\WindowsPowerShell\v1.0\Registry.format.ps1xml
C:\Windows\System32\WindowsPowerShell\v1.0\types.ps1xml
C:\Windows\System32\WindowsPowerShell\v1.0\typesv3.ps1xml
C:\Windows\System32\WindowsPowerShell\v1.0\WSMan.Format.ps1xml

outside powershell

Active code page: 65001
개인 및 시스템 프로필을 로드하는 데 1809ms가 걸렸습니다.
PS C:\WINDOWS\system32> $pshome
C:\Windows\SysWOW64\WindowsPowerShell\v1.0
PS C:\WINDOWS\system32> ls C:\Windows\System32\WindowsPowerShell\v1.0 | select
 fullname

FullName
--------
C:\Windows\System32\WindowsPowerShell\v1.0\en
C:\Windows\System32\WindowsPowerShell\v1.0\en-US
C:\Windows\System32\WindowsPowerShell\v1.0\Examples
C:\Windows\System32\WindowsPowerShell\v1.0\ko
C:\Windows\System32\WindowsPowerShell\v1.0\ko-KR
C:\Windows\System32\WindowsPowerShell\v1.0\Modules
C:\Windows\System32\WindowsPowerShell\v1.0\Schemas
C:\Windows\System32\WindowsPowerShell\v1.0\SessionConfig
C:\Windows\System32\WindowsPowerShell\v1.0\Certificate.format.ps1xml
C:\Windows\System32\WindowsPowerShell\v1.0\Diagnostics.Format.ps1xml
C:\Windows\System32\WindowsPowerShell\v1.0\DotNetTypes.format.ps1xml
C:\Windows\System32\WindowsPowerShell\v1.0\Event.Format.ps1xml
C:\Windows\System32\WindowsPowerShell\v1.0\FileSystem.format.ps1xml
C:\Windows\System32\WindowsPowerShell\v1.0\getevent.types.ps1xml
C:\Windows\System32\WindowsPowerShell\v1.0\Help.format.ps1xml
C:\Windows\System32\WindowsPowerShell\v1.0\HelpV3.format.ps1xml
C:\Windows\System32\WindowsPowerShell\v1.0\Microsoft.PowerShell.Core_00000...
C:\Windows\System32\WindowsPowerShell\v1.0\Microsoft.PowerShell.Diagnostic...
C:\Windows\System32\WindowsPowerShell\v1.0\Microsoft.PowerShell.Host_56d66...
C:\Windows\System32\WindowsPowerShell\v1.0\Microsoft.PowerShell.Management...
C:\Windows\System32\WindowsPowerShell\v1.0\Microsoft.PowerShell.Security_a...
C:\Windows\System32\WindowsPowerShell\v1.0\Microsoft.PowerShell.Utility_1d...
C:\Windows\System32\WindowsPowerShell\v1.0\Microsoft.WSMan.Management_7662...
C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
C:\Windows\System32\WindowsPowerShell\v1.0\PowerShellCore.format.ps1xml
C:\Windows\System32\WindowsPowerShell\v1.0\PowerShellTrace.format.ps1xml
C:\Windows\System32\WindowsPowerShell\v1.0\powershell_ise.exe
C:\Windows\System32\WindowsPowerShell\v1.0\powershell_ise.exe.config
C:\Windows\System32\WindowsPowerShell\v1.0\profile.ps1
C:\Windows\System32\WindowsPowerShell\v1.0\PSEvents.dll
C:\Windows\System32\WindowsPowerShell\v1.0\pspluginwkr.dll
C:\Windows\System32\WindowsPowerShell\v1.0\pwrshmsg.dll
C:\Windows\System32\WindowsPowerShell\v1.0\pwrshsip.dll
C:\Windows\System32\WindowsPowerShell\v1.0\Registry.format.ps1xml
C:\Windows\System32\WindowsPowerShell\v1.0\types.ps1xml

Tyriar · 2017-06-06T17:46:34Z

This is a duplicate of microsoft/vscode#19665, it's due to Windows Creators Update, make sure you update your Windows when it's available to fix it.

HyundongHwang · 2017-06-08T06:16:40Z

@Tyriar @daviwil
Surprisingly, the terminal at android studio has the same symptoms.

Tyriar · 2017-06-08T19:48:02Z

@HyundongHwang it's a problem with Windows so has a very wide impact and affects many applications. As I understand t the fix is rolling out to stable builds of Windows now.

daviwil · 2017-06-13T14:51:47Z

Closing this since it's a Windows issue that's affecting everyone, not just VS Code.

daviwil closed this as completed Jun 13, 2017

daviwil added the Resolution-External label Jun 13, 2017

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Visual Studio Code powershell terminal display is broken #833

Visual Studio Code powershell terminal display is broken #833

HyundongHwang commented Jun 6, 2017 •

edited

Loading

daviwil commented Jun 6, 2017

HyundongHwang commented Jun 6, 2017

daviwil commented Jun 6, 2017

HyundongHwang commented Jun 6, 2017

daviwil commented Jun 6, 2017

HyundongHwang commented Jun 6, 2017

Tyriar commented Jun 6, 2017

HyundongHwang commented Jun 8, 2017

Tyriar commented Jun 8, 2017

daviwil commented Jun 13, 2017

Visual Studio Code powershell terminal display is broken #833

Visual Studio Code powershell terminal display is broken #833

Comments

HyundongHwang commented Jun 6, 2017 • edited Loading

System Details

Issue Description

Attached Logs

daviwil commented Jun 6, 2017

HyundongHwang commented Jun 6, 2017

daviwil commented Jun 6, 2017

HyundongHwang commented Jun 6, 2017

daviwil commented Jun 6, 2017

HyundongHwang commented Jun 6, 2017

Tyriar commented Jun 6, 2017

HyundongHwang commented Jun 8, 2017

Tyriar commented Jun 8, 2017

daviwil commented Jun 13, 2017

HyundongHwang commented Jun 6, 2017 •

edited

Loading