The terminal has an abnormality and the related information fails to appear normally.

[czfadmin]

Issue Type: Bug
In the latest version, when the VSCode terminal is opened, the phenomenon in the following GIF will appear. When the Enter key is entered, the terminal will display relevant information. When the window is reloaded, create a new terminal or reopen VSCode. At the time, this phenomenon will still occur.

The problem still occurs after all extensions are disabled:

VS Code version: Code - Insiders 1.28.0-insider (85d970a, 2018-10-02T22:27:52.997Z)
OS version: Windows_NT x64 10.0.17763

System Info

Item	Value
CPUs	Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz (8 x 1800)
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 video_decode: enabled video_encode: enabled webgl: enabled webgl2: enabled
Memory (System)	7.88GB (3.76GB free)
Process Argv
Screen Reader	no
VM	0%

Extensions (32)

Extension	Author (truncated)	Version
ng-template	Ang	0.1.10
dart-code	Dar	2.19.0
flutter	Dar	2.19.0
tslint	eg2	1.0.39
code-runner	for	0.9.4
Angular2	joh	6.1.5
Kotlin	mat	1.6.0
Angular-BeastCode	Mik	6.2.30
vscode-cosmosdb	ms-	0.8.0
vscode-language-pack-zh-hans	MS-	1.28.1
anaconda-extension-pack	ms-	1.0.0
python	ms-	2018.8.0
azure-account	ms-	0.4.3
cpptools	ms-	0.19.0
csharp	ms-	1.16.1
Go	ms-	0.6.89
js-atom-grammar	ms-	0.1.14
mono-debug	ms-	0.15.8
PowerShell	ms-	1.9.0
typescript-javascript-grammar	ms-	0.0.45
debugger-for-chrome	msj	4.10.2
vetur	oct	0.12.7
platformio-ide	pla	1.3.1
java	red	0.32.0
vscode-yaml	red	0.0.17
rust	rus	0.4.10
vscode-arduino	vsc	0.2.20
vscode-java-debug	vsc	0.13.0
vscode-java-pack	vsc	0.4.0
vscode-java-test	vsc	0.9.0
vscode-maven	vsc	0.11.0
JavaScriptSnippets	xab	1.7.0

(1 theme extensions excluded)

[christopherwolf1]

I can confirm; will skip posting the Animated GIF, but it looks to be the same issue. One additional note of detail, however; it appears it only does this when Code Insiders boots and the 1: Powershell terminal, or whatever you have as the first terminal, renders. Adding new terminals afterwards manually with the '+' new terminal button do not exhibit this behavior.

Version: 1.28.0-insider (user setup)
Commit: 85d970a
Date: 2018-10-02T22:27:52.997Z
Electron: 2.0.9
Chrome: 61.0.3163.100
Node.js: 8.9.3
V8: 6.1.534.41
Architecture: x64

[500InternalError]

I also have this problem, and I it seems that it's the windows 1809 update's problem, because the problem appeared after I upgraded to 1809.BTW another terminal emulator called hyper also has this problem

Version: 1.27.2 (system setup)
Commit: f46c4c4
Date: 2018-09-12T16:17:45.060Z
Electron: 2.0.7
Chrome: 61.0.3163.100
Node.js: 8.9.3
V8: 6.1.534.41
Architecture: x64
OS Version: Windows 10 1809 (x64)

[czfadmin]

@christopherwolf1 Thank you.This behavior will still occur after manually adding a new terminal using the "+" new terminal button.
I agree with @500InternalError, this problem should be caused by the window1809 update.Because I did not have this problem with a stable version of VSCode before I updated it to the system, but this problem occurred after updating the system.
@500InternalError, your avatar is really cool.

[500InternalError]

Ohh thank you for your praise @czfadmin

[christopherwolf1]

@czfadmin

See GIF below; the bug behavior, at least on my system, is similar to that observed in the OP, until a new terminal is created. At which point, normal behavior resumes

[czfadmin]

@christopherwolf1
Ok, but there will be such a problem on my computer. In both versions, this problem will occur. At the same time I try to use your method and it does not solve the problem.

[christopherwolf1]

It's not really to solve the problem, just a little bit more detail; it could also be a closely related bug. Either way, the information could help to resolve it faster and/or discriminate between two closely related bugs.

[Tyriar]

#57803