Support for Windows 10 LTSC #3731

Closed
opened 2026-01-30 23:28:40 +00:00 by claunia · 7 comments
Owner

Originally created by @duanyukai on GitHub (Sep 3, 2019).

Description of the new feature/enhancement

Support for Windows 10 LTSC

Proposed technical implementation details (optional)

Windows 10 LTSC doesn't support Windows Store Apps, but the terminal is an essential part of daily management.

Originally created by @duanyukai on GitHub (Sep 3, 2019). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> # Description of the new feature/enhancement Support for Windows 10 LTSC <!-- A clear and concise description of what the problem is that the new feature would solve. Describe why and how a user would use this new functionality (if applicable). --> # Proposed technical implementation details (optional) Windows 10 LTSC doesn't support Windows Store Apps, but the terminal is an essential part of daily management. <!-- A clear and concise description of what you want to happen. -->
claunia added the Issue-FeatureResolution-By-DesignNeeds-TriageNeeds-Tag-Fix labels 2026-01-30 23:28:40 +00:00
Author
Owner

@DHowett-MSFT commented on GitHub (Sep 3, 2019):

Sorry. We require features that only exist on Windows 1903. If those features can be used on older versions in the future, we will reevalute this.

@DHowett-MSFT commented on GitHub (Sep 3, 2019): Sorry. We require features that only exist on Windows 1903. If those features can be used on older versions in the future, we will reevalute this.
Author
Owner

@Andrew-Hanlon commented on GitHub (Sep 24, 2019):

@DHowett-MSFT Would you be able to provide details (or a link to more information) on which features require 1903+? Thanks!

@Andrew-Hanlon commented on GitHub (Sep 24, 2019): @DHowett-MSFT Would you be able to provide details (or a link to more information) on which features require 1903+? Thanks!
Author
Owner

@zadjii-msft commented on GitHub (Sep 24, 2019):

There's a bunch of threads on this already, but the main one is the Xaml Hosting "XAML Islands" APIs that the Terminal uses to host UWP XAML UI elements in a desktop application.

@zadjii-msft commented on GitHub (Sep 24, 2019): There's a bunch of threads on this already, but the main one is the Xaml Hosting "XAML Islands" APIs that the Terminal uses to host UWP XAML UI elements in a desktop application.
Author
Owner

@pedro2555 commented on GitHub (Dec 18, 2019):

This crap moved me into Linux. Really tired of fighting with Windows. LTSC on a VM, and the host for a proper terminal.

@pedro2555 commented on GitHub (Dec 18, 2019): This crap moved me into Linux. Really tired of fighting with Windows. LTSC on a VM, and the host for a proper terminal.
Author
Owner

@five23 commented on GitHub (Jul 24, 2020):

Lame.

@five23 commented on GitHub (Jul 24, 2020): Lame.
Author
Owner

@aqc-carlodri commented on GitHub (Oct 8, 2021):

Would be great if this was reconsidered!

@aqc-carlodri commented on GitHub (Oct 8, 2021): Would be great if this was reconsidered!
Author
Owner

@zadjii-msft commented on GitHub (Oct 8, 2021):

From the FAQ:

There are some important operating system features we depend on. Namely:

  • XAML Islands is the technology we use to host our XAML UI in a Win32 process. Without that, we'd be unable to display anything. Since XAML Islands is only complete as of 1903, there's nothing we can do about it.
  • 1903 Also added support for side-by-side WinRT component activation, something deep in the COM stack that lets us find our DLLs when they're right next to our EXE.

These are unfortunately features that aren't going to be back-ported to earlier versions of Windows, so we won't be able to bring the Terminal to those versions either.

@zadjii-msft commented on GitHub (Oct 8, 2021): [From the FAQ:](https://github.com/microsoft/terminal/wiki/Frequently-Asked-Questions-(FAQ)#can-i-use-the-terminal-on-windows-7-windows-server-2019-any-other-down-level-windows-version) There are some important operating system features we depend on. Namely: * XAML Islands is the technology we use to host our XAML UI in a Win32 process. Without that, we'd be unable to display anything. Since XAML Islands is only complete as of 1903, there's nothing we can do about it. * 1903 Also added support for side-by-side WinRT component activation, something deep in the COM stack that lets us find our DLLs when they're right next to our EXE. These are unfortunately features that aren't going to be back-ported to earlier versions of Windows, so we won't be able to bring the Terminal to those versions either.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#3731