Right clicking the Windows Terminal icon in the taskbar doesn't allow directly launching profiles like it used to.

[ItsIgnacioPortal]

Windows Terminal version

1.18.3181.0

Windows build number

10.0.19045.3803

Other Software

No response

Steps to reproduce

1. Open windows terminal
2. Right click it's icon in the task bar

Expected Behavior

Previously there was a menu where you could launch any of your Windows Terminal profiles after right clicking the terminal icon in the taskbar. All of the options that were shown within windows terminal were shown in this menu:

Actual Behavior

But now, all I see is "Terminal"

This feature was already implemented in previous versions of Windows Terminal, but it seems to have been reverted now, for some reason.

[github-actions]

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Closed similar issues:

• Add ability to quickly launch Windows Terminal with a desired profile instead of the one set currently as default. (#7540), similarity score: 0.83
• Enable launching of any terminal profile directly from taskbar (and not just the default profile) (#6667), similarity score: 0.82
• Opening Windows Terminal by default doesn't pick the right profile (#10228), similarity score: 0.81
• Launch profiles by alt-clicking in task bar. (#3757), similarity score: 0.81

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[zadjii-msft]

Here's a thought - does this happen on a cold launch of the Terminal/? (e.g. make sure to close all Terminal windows, then launch the terminal fresh) Or does this only happen after you've closed one terminal window, while the Terminal is still running?

I bet this is a window refrigeration issue - it is on Windows 10, and jumplist code is in that part of the codebase

[ItsIgnacioPortal]

does this only happen after you've closed one terminal window, while the Terminal is still running?

I've tested that now, and it doesn't seem to trigger the issue.

Oddly enough, the issue seems to be completely gone now. I'm still in the same Windows version, and the same Windows Terminal version (v1.18.3181.0). The only thing that's changed is that I upgraded some system dependencies:

• Microsoft Visual C++ 2021 Redistributable (x64) - v11.0.61030.0

• Microsoft Visual C++ 2021 Redistributable (x86) - v11.0.61030.0

• Microsoft Visual C++ 2015-2022 Redistributable (x64) - v14.38.33130.0

• Microsoft Visual C++ 2015-2022 Redistributable (x86) - v14.38.33130.0

• Microsoft Windows Desktop Runtime (x64) - v6.0.25.33020

• Microsoft Windows Desktop Runtime (x86) - v6.0.25.33020

• Microsoft Windows Desktop Runtime (x64) - v7.0.14.33020

• Microsoft Windows Desktop Runtime (x86) - v7.0.14.33020

• Microsoft Windows Desktop Runtime (x86) - v8.0.0.33101

• Microsoft Windows Desktop Runtime (x64) - v8.0.0.33101

• Java 8 Update 391 (64-bit) - v8.0.3910.13

• Java 8 Update 391 - v8.0.3910.13

And now the launch options are showing up correctly: