WSL Ubuntu starts in Windows Terminal, not Ubuntu-style terminal and Terminal Starts Ubuntu in Ubuntu style Terminal

[A-s-a-d]

Windows Version

Microsoft Windows [Version 10.0.22631.4460]

WSL Version

WSL version: 2.3.26.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

No response

Distro Version

Ubuntu 24.04

Other Software

No response

Repro Steps

I just installed Wsl and Ubuntu nothing else, i didn't even notice it at first but then opened one with different method and it was completely different.
Normal method i use :
Different method i used to open terminal in a new tab:

Expected Behavior

I'm expecting that when i launch "ubuntu" from start menu it launches me in Ubuntu style terminal and if i launch the "Terminal" it doesent lanuch the Ubuntu but whatever it used to do before ( i think it was powershell or command line not sure).
Ubuntu style terminal :

Actual Behavior

I recently started using WSL and i have some problemes with it :
When launch i launch Ubuntu from start menu it opens in windows terminal.

When i open new Ubuntu terminal from inside the terminal it opens "Ubuntu style" terminal.

When from start menu i search Ubuntu and do "Run As Administrator" it opens this terminal.

and if i launch it from powershell using "wsl -d Ubuntu" it launches inside powershell.

and when i search just "Terminal" and launch it, guess what instead of normal windows terminal it launches the Ubuntu Terminal.

It's very annoying that it's different depending on where you launch it from.

Diagnostic Logs

No response

[github-actions]

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

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!

Closed similar issues:

• WSL.exe in System32 Folder Always Launches New Window (#9646), similarity score: 0.74
• WLS starts in terminal instead of starting the Linux Distro in it's own GUI Window (#8652), similarity score: 0.72
• Two different versions of WSL when I open as regular user versus Admin (#8415), similarity score: 0.72
• WSL being detected but isn't starting (#11297), similarity score: 0.71
• A connection attempt failed because the connected party did not properly respond (#5459), similarity score: 0.71

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