3

Windows Terminal Becomes the Default Terminal App in Windows 11

 2 years ago
source link: https://news.softpedia.com/news/windows-terminal-becomes-the-default-terminal-app-in-windows-11-535992.shtml
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
neoserver,ios ssh client

The change takes place in the latest preview build

The new build is live in the Dev channel
   The new build is live in the Dev channel

Microsoft has promoted Windows terminal to become the default terminal app in Windows 11, with the change happening in the most recent preview build shipped to insiders in the Dev channel.

Windows 11 build 25188, therefore, replaces Command Prompt and PowerShell with Windows Terminal, though it’s important to keep in mind that Windows Terminal version 1.15 or newer is required to allow the change.

“Windows Terminal is now the default terminal in Windows 11. This means, all command line applications will open in Windows Terminal automatically (Command Prompt and PowerShell, for example). The setting for this change can be found via Settings > Privacy & security > For developers. Please note that Windows Terminal version 1.15 or greater is required for this feature,” Microsoft explains.

As for when this change is projected to take place in the stable version of Windows 11, no ETA is available at this point, as the improvements that are included in the Dev channel don’t come with a specific ETA.

More touch keyboard settings

The latest Windows 11 preview build also includes new touch keyboard settings.

“We are trying out a new touch keyboard setting that replaces the “Show the touch keyboard when there’s no keyboard attached” checkbox under Settings > Time & language > Typing > Touch keyboard with a new dropdown menu with 3 options to control whether tapping an edit control should launch the touch keyboard,” Microsoft explains.

Worth knowing is that this new build comes with a known issue that causes problems for .NET Framework 3.5, with some apps likely to be broken.

“Enabling .NET Framework 3.5 from the Windows Features dialog will not work in this build. If you had it enabled prior to upgrading, it may become disabled. This will potentially lead to issues with apps that rely on these components. We’re working on a fix,” Microsoft says.


About Joyk


Aggregate valuable and interesting links.
Joyk means Joy of geeK