Changed behavior in newest Windows terminal from Microsoft store #11913

Open
opened 2026-01-31 03:00:52 +00:00 by claunia · 0 comments
Owner

Originally created by @joltar on GitHub (Dec 30, 2020).

I have been using Window Terminal to open and use a Pengwin installation. I just installed the latest version. In the previous Terminal I could open the bash (?) for Pengwin or any other Linux installation. Now the only option is for Azure, which I haven't installed. I know the developers on GitHub don't suffer fools gladly, but I am just attempting to learn a little about Linux after being defeated at coding by Fortran on an IBM mainframe at UCB in early 60's. (Leading to a beneficialcareer change to Medicine) TMI. I'm sure altering the settings file would work, If I were able to code in Javascript. But apparently the new Terminal no longer scans for Linux on installation. This may be intentional, but is an inconvenience, if not a bug. And there is apparently no convenient workaround. Apologies if this is a foolish observation. Or posted in the wrong place.

Environment

Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd]
Windows Terminal version (if applicable):

Any other software?

Steps to reproduce

Expected behavior

Actual behavior

Originally created by @joltar on GitHub (Dec 30, 2020). I have been using Window Terminal to open and use a Pengwin installation. I just installed the latest version. In the previous Terminal I could open the bash (?) for Pengwin or any other Linux installation. Now the only option is for Azure, which I haven't installed. I know the developers on GitHub don't suffer fools gladly, but I am just attempting to learn a little about Linux after being defeated at coding by Fortran on an IBM mainframe at UCB in early 60's. (Leading to a beneficialcareer change to Medicine) TMI. I'm sure altering the settings file would work, If I were able to code in Javascript. But apparently the new Terminal no longer scans for Linux on installation. This may be intentional, but is an inconvenience, if not a bug. And there is apparently no convenient workaround. Apologies if this is a foolish observation. Or posted in the wrong place. <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd] Windows Terminal version (if applicable): Any other software? ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> # Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> # Actual behavior <!-- What's actually happening? -->
claunia added the Resolution-Duplicate label 2026-01-31 03:00:52 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#11913