PowerShell Preview Does Not Load Integrated Terminal

[ghost]

Issue Type: Bug

PowerShell extension is disabled. But it doesn't matter because get the same result whether it is installed and disabled or uninstalled.

After installing PowerShell Preview v2.0.0-preview.1, select PowerShell Command Explorer.

Nothing loads.

And get the following message:

"There is no data provider registered that can provide view data."

Extension version: 2.0.0
VS Code version: Code 1.32.3 (a3db5be9b5c6ba46bb7555ec5d60178ecc2eaae4, 2019-03-14T23:43:35.476Z)
OS version: Windows_NT x64 10.0.17763

System Info

Item	Value
CPUs	Intel(R) Core(TM) i7-4720HQ CPU @ 2.60GHz (8 x 2594)
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)	11.92GB (6.83GB free)
Process Argv
Screen Reader	no
VM	0%

[TylerLeonhardt]

Did you open an empty workspace or a folder when you opened vscode?

There's currently a bug in Preview that is fixed and pending a deployment that will fix this issue.

[Cazs03]

Same here

[SydneyhSmith]

@HJLBX @Cazs03 we have released the update, would you mind updating if ou havent already and letting us know if you hit the issue still?

[tmknight]

I experience PowerShell Integrated not fully loading. It requires, placing focus on the terminal and hitting ENTER x2 to completely load.

For what it's worth, this is the same behavior for native PS terminal; though that only requires ENTER x1 to completely load.

Version: 1.32.3 (user setup)
Commit: a3db5be9b5c6ba46bb7555ec5d60178ecc2eaae4
Date: 2019-03-14T23:43:35.476Z
Electron: 3.1.6
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Windows_NT x64 10.0.17763

[tmknight]

Additional info: If you kill the PS Integrated Terminal and reload it, it will completely load without issue.

[rjmholt]

@tmknight Thanks for that info. I believe this is a Windows bug that VSCode itself has been trying to fix. The fact that it occurs outside of the extension means I don't think we can do much about it on our side.

@HJLBX, @Cazs03 can you let us know if you're seeing similar behaviour to this? If so, the fix will lie with Windows Update and the next VSCode release.

[SydneyhSmith]

VSCode 1.35 should mean that this issue is fixed so I am going to go ahead and close it --please let us know if you are still hitting this issue and we will reopen/investigate further