A change in VScode makes it confusing for a user to switch the to a different PowerShell environment in the Integrated Terminal.

Issue Type: Bug

Steps to Reproduce:

1. Open vs code with PowerShell extension
2. Try to change to a different Integrated Terminal via the status tray.

I have been informed that this is due to a change in the way VS code works, which has had a knock-on effect on how the VScode PowerShell team have had to implement a new option to select PS versions within the Integrated . Personally, I simply could not figure this out without some guidance and lost a bunch of time trying to understand what was wrong and why I could no longer change PS versions in the Integrated Terminal.

Old way - very obvious: what PS version you were using: You simply clicked on 5.1, and could swithch to another version

New way - completely unobvious on how to change PS versions: Now, you need to hover over the { } icon next to the word PowerShell (and NOT on the word “PowerShell” itself) in order to see a link to the Session Menu, where you can then change the PS version.

Images to follow

VS Code version: Code 1.68.1 (30d9c6cd9483b2cc586687151bcbcd635f373630, 2022-06-14T12:48:58.283Z) OS version: Windows_NT x64 10.0.22000 Restricted Mode: No

System Info

Item	Value
CPUs	Intel® Core™ i7-9850H CPU @ 2.60GHz (12 x 2592)
GPU Status	2d_canvas: enabled canvas_oop_rasterization: disabled_off direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on oop_rasterization: enabled opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_renderer: enabled_on video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled
Load (avg)	undefined
Memory (System)	31.78GB (15.74GB free)
Process Argv	–crash-reporter-id fdd18362-22ae-4526-bbb3-f5ff8550b378
Screen Reader	yes
VM	22%

Extensions (15)

Extension	Author (truncated)	Version
githistory	don	0.6.19
vscode-npm-script	eg2	0.3.25
beautify	Hoo	1.5.0
vscode-edit-csv	jan	0.7.1
rainbow-csv	mec	2.4.0
vscode-edge-devtools	ms-	2.0.0
python	ms-	2022.8.0
vscode-pylance	ms-	2022.6.20
jupyter	ms-	2022.5.1001601848
jupyter-keymap	ms-	1.0.0
jupyter-renderers	ms-	1.0.8
powershell-preview	ms-	2022.6.1
debugger-for-edge	msj	1.0.15
code-spell-checker	str	2.2.4
html-preview-vscode	tht	0.2.5

A/B Experiments

vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscoreces:30445986
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
vsc1dst:30438360
pythonvs932:30410667
wslgetstarted:30449410
vscscmwlcmt:30465135
cppdebug:30492333
vsclangdc:30486549
841h4636:30513380

[andschwa]

We’ve definitely had a number of user complaints about this since the update. It was quiet for a while but they eventually rolled in, to the point that we address it in our docs. So being able to pin it automatically would be helpful.

[Tyriar]

@jrieken more language status feedback, default pinning would help here too