starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

How does LTSC install the terminal? #5394

New Issue
Closed
opened 2026-01-31 00:12:23 +00:00 by claunia · 13 comments
claunia commented 2026-01-31 00:12:23 +00:00
Owner
Copy Link

Originally created by @Hiddensu on GitHub (Dec 5, 2019).

???

Originally created by @Hiddensu on GitHub (Dec 5, 2019). ???
claunia added the Issue-FeatureNeeds-Tag-Fix labels 2026-01-31 00:12:23 +00:00
claunia commented 2026-01-31 00:12:24 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Dec 5, 2019):

It doesn’t, sorry.

@DHowett-MSFT commented on GitHub (Dec 5, 2019): It doesn’t, sorry.
claunia commented 2026-01-31 00:12:24 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Dec 5, 2019):

For more context: we've discussed this at length previously why the terminal doesn't work on older versions of Windows. From another discussion:

https://github.com/microsoft/terminal/issues/1643#issuecomment-505971691

Sorry. Right now, there's two big blockers to adoption on 1809.

* XAML islands was a technology preview and didn't support high-DPI, DPI changes, or accessibility in 1809. We rely on them heavily.

* 1903 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.

We just can't go back to 1809.

https://github.com/microsoft/terminal/issues/1909#issuecomment-510042323

the Windows Terminal REQUIRES features from the latest Windows release.

Unfortunately, there's really no workarounds available to us. 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 the latest Windows 10 release, there's nothing we can do about it.

If you'll want to use the terminal, you'll need to be on the latest Windows 10 version.

https://github.com/microsoft/terminal/issues/841#issuecomment-492940388

https://github.com/microsoft/terminal/issues/498#issuecomment-490091740

There are no plans currently.

We're dependent upon C++/WinRT and XAML Islands (UWP XAML) for our UI. We're also using DX/DWrite for the text renderer. Unless those are ported to linux sometime, then I'd say there's very little chance we ever support linux.

Furthermore, our entire build system is MsBuild-based, and I could be wrong, but I don't think our build system will work on linux.

https://github.com/microsoft/terminal/issues/1893#issuecomment-509728952

https://github.com/microsoft/terminal/issues/2024#issuecomment-512788360

https://github.com/microsoft/terminal/issues/2480

@zadjii-msft commented on GitHub (Dec 5, 2019): For more context: we've discussed this at length previously why the terminal doesn't work on older versions of Windows. From another discussion: ### https://github.com/microsoft/terminal/issues/1643#issuecomment-505971691 > Sorry. Right now, there's two big blockers to adoption on 1809. > > * XAML islands was a technology preview and didn't support high-DPI, DPI changes, or accessibility in 1809. We rely on them heavily. > > * 1903 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. > > > We just can't go back to 1809. ### https://github.com/microsoft/terminal/issues/1909#issuecomment-510042323 > > > > the Windows Terminal **REQUIRES** features from the latest Windows release. > > Unfortunately, there's really no workarounds available to us. 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 the latest Windows 10 release, there's nothing we can do about it. > > If you'll want to use the terminal, you'll _need_ to be on the latest Windows 10 version. ### https://github.com/microsoft/terminal/issues/841#issuecomment-492940388 ### https://github.com/microsoft/terminal/issues/498#issuecomment-490091740 > > > There are no plans currently. > > We're dependent upon C++/WinRT and XAML Islands (UWP XAML) for our UI. We're also using DX/DWrite for the text renderer. Unless those are ported to linux sometime, then I'd say there's very little chance we ever support linux. > > Furthermore, our entire build system is MsBuild-based, and I could be wrong, but I don't think our build system will work on linux. ### https://github.com/microsoft/terminal/issues/1893#issuecomment-509728952 ### https://github.com/microsoft/terminal/issues/2024#issuecomment-512788360 ### https://github.com/microsoft/terminal/issues/2480
claunia commented 2026-01-31 00:12:24 +00:00
Author
Owner
Copy Link

@nonetrix commented on GitHub (Apr 7, 2021):

Yeah LSTC is too old and doesn't support stuff needed to run it I guess was hoping I could install it manually rather than from the MS store.

Best bet is to wait for the next version of LTSC when ever that is or use normal Windows 10, you could also look at alacritty I use it on Linux and apparently it's on windows, uses rust and opengl might not be as good but it's something and it's better than cmd.

@nonetrix commented on GitHub (Apr 7, 2021): Yeah LSTC is too old and doesn't support stuff needed to run it I guess was hoping I could install it manually rather than from the MS store. Best bet is to wait for the next version of LTSC when ever that is or use normal Windows 10, you could also look at alacritty I use it on Linux and apparently it's on windows, uses rust and opengl might not be as good but it's something and it's better than cmd.
claunia commented 2026-01-31 00:12:24 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Feb 22, 2022):

Windows Terminal successfully installs on Windows 10 Enterprise LTSC 2021 with Add-AppXPackage. Yeah it finally got an update.

@ghost commented on GitHub (Feb 22, 2022): Windows Terminal successfully installs on Windows 10 Enterprise LTSC 2021 with `Add-AppXPackage`. Yeah it finally got an update.
claunia commented 2026-01-31 00:12:25 +00:00
Author
Owner
Copy Link

@rj-hwang commented on GitHub (Apr 15, 2022):

Windows Terminal successfully installs on Windows 10 Enterprise LTSC 2021 with Add-AppXPackage. Yeah it finally got an update.

How?

@rj-hwang commented on GitHub (Apr 15, 2022): > Windows Terminal successfully installs on Windows 10 Enterprise LTSC 2021 with `Add-AppXPackage`. Yeah it finally got an update. How?
claunia commented 2026-01-31 00:12:25 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Apr 18, 2022):

Windows Terminal successfully installs on Windows 10 Enterprise LTSC 2021 with Add-AppXPackage. Yeah it finally got an update.

How?

Please, if you know how to use powershell then you must be able yo install a package. I mean just google it and you’ll get an immediate answer. Why even bother to ask here?

@ghost commented on GitHub (Apr 18, 2022): > > Windows Terminal successfully installs on Windows 10 Enterprise LTSC 2021 with `Add-AppXPackage`. Yeah it finally got an update. > > How? Please, if you know how to use powershell then you must be able yo install a package. I mean just google it and you’ll get an immediate answer. Why even bother to ask here?
claunia commented 2026-01-31 00:12:25 +00:00
Author
Owner
Copy Link

@averyfreeman commented on GitHub (Aug 15, 2022):

Yeah LSTC is too old and doesn't support stuff needed to run it I guess was hoping I could install it manually rather than from the MS store.

Best bet is to wait for the next version of LTSC when ever that is or use normal Windows 10, you could also look at alacritty I use it on Linux and apparently it's on windows, uses rust and opengl might not be as good but it's something and it's better than cmd.

I am on new LTSC 2021 install. After installing MS Store (for AppX), install MS App Installer from MS Store (has Winget, etc.).

Update: May need to install VCLib110 and 120 in addition to UWP UI and VCLib140 on certain LTSC builds (e.g. LTSC IoT).

@averyfreeman commented on GitHub (Aug 15, 2022): > Yeah LSTC is too old and doesn't support stuff needed to run it I guess was hoping I could install it manually rather than from the MS store. > > Best bet is to wait for the next version of LTSC when ever that is or use normal Windows 10, you could also look at alacritty I use it on Linux and apparently it's on windows, uses rust and opengl might not be as good but it's something and it's better than cmd. I am on new LTSC 2021 install. After installing MS Store (for AppX), install MS App Installer from MS Store (has Winget, etc.). Update: May need to install VCLib110 and 120 in addition to UWP UI and VCLib140 on certain LTSC builds (e.g. LTSC IoT).
claunia commented 2026-01-31 00:12:25 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Feb 24, 2023):

Windows 10 Enterprise LTSC 21H2 (19044.2604)

Download the C++ Runtime Framework for your architecture. In my case this was:
Microsoft.VCLibs.x64.14.00.Desktop.appx

Download the Windows 10 Terminal msix bundle from the releases page. In my case this was:
Microsoft.WindowsTerminal_Win10_1.16.10261.0_8wekyb3d8bbwe.msixbundle

Open an Administrator PowerShell window (right click and run as Administrator).

Navigate to your download directory.

Use Add-AppxPackage to install the C++ framework then Terminal. In my case this was:
Add-AppxPackage .\Microsoft.VCLibs.x64.14.00.Desktop.appx
then
Add-AppxPackage .\Microsoft.WindowsTerminal_Win10_1.16.10261.0_8wekyb3d8bbwe.msixbundle

Done!

Hopefully this helps someone else looking for the same answer. I'm thrilled to have Terminal up and running on LTSC!

@ghost commented on GitHub (Feb 24, 2023): Windows 10 Enterprise LTSC 21H2 (19044.2604) Download the C++ Runtime Framework for your architecture. In my case this was: Microsoft.VCLibs.x64.14.00.Desktop.appx Download the Windows 10 Terminal msix bundle from the releases page. In my case this was: Microsoft.WindowsTerminal_Win10_1.16.10261.0_8wekyb3d8bbwe.msixbundle Open an Administrator PowerShell window (right click and run as Administrator). Navigate to your download directory. Use Add-AppxPackage to install the C++ framework then Terminal. In my case this was: Add-AppxPackage .\Microsoft.VCLibs.x64.14.00.Desktop.appx then Add-AppxPackage .\Microsoft.WindowsTerminal_Win10_1.16.10261.0_8wekyb3d8bbwe.msixbundle Done! Hopefully this helps someone else looking for the same answer. I'm thrilled to have Terminal up and running on LTSC!
claunia commented 2026-01-31 00:12:25 +00:00
Author
Owner
Copy Link

@notrealdev commented on GitHub (Apr 6, 2023):

Thank @K7CTC
It works for me ☺️

@notrealdev commented on GitHub (Apr 6, 2023): Thank @K7CTC It works for me ☺️
claunia commented 2026-01-31 00:12:25 +00:00
Author
Owner
Copy Link

@VitaliyAT commented on GitHub (Aug 16, 2023):

Windows 10 LTSC 21H2 19044.3324
it runs but can't be install... strange... a lot

Don't want to install MS Store for it... not for this LTSC was installed... Manually copy it in Program Files, create lnk and put it in Start menu. After that, pin it to quick access. Done. It was impossibly made such installer, yea?

@VitaliyAT commented on GitHub (Aug 16, 2023): `Windows 10 LTSC 21H2 19044.3324` it runs but can't be install... strange... a lot Don't want to install MS Store for it... not for this LTSC was installed... Manually copy it in Program Files, create lnk and put it in Start menu. After that, pin it to quick access. Done. It was impossibly made such installer, yea?
claunia commented 2026-01-31 00:12:26 +00:00
Author
Owner
Copy Link

@realsarius commented on GitHub (Aug 27, 2023):

The Windows 10 PreinstallKit in Releases has Windows Terminal and its dependencies for multiple architectures. Just download that, install the dependencies and the terminal and enjoy

@realsarius commented on GitHub (Aug 27, 2023): The Windows 10 PreinstallKit in Releases has Windows Terminal and its dependencies for multiple architectures. Just download that, install the dependencies and the terminal and enjoy
claunia commented 2026-01-31 00:12:26 +00:00
Author
Owner
Copy Link

@notrealdev commented on GitHub (Sep 10, 2023):

@VitaliyAT can you try it?
Imgur

@notrealdev commented on GitHub (Sep 10, 2023): @VitaliyAT can you try it? ![Imgur](https://i.imgur.com/DqEO5B2.png)
claunia commented 2026-01-31 00:12:26 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Sep 13, 2023):

@realsarius is correct.

To update my original post:

I'm running Windows 10 Enterprise LTSC 21H2 (19044.3448)

Download the Windows Terminal Windows 10 Preinstall Kit from the releases page. In my case this was:
Microsoft.WindowsTerminal_1.17.11461.0_8wekyb3d8bbwe.msixbundle_Windows10_PreinstallKit.zip

Extract to a location of your preference.

Open an Administrator PowerShell window (right click and run as Administrator).

Navigate to the directory you extracted to.

Use Add-AppxPackage to install the prerequisites. In my case this was:
Add-AppxPackage .\Microsoft.VCLibs.140.00.UWPDesktop_14.0.30704.0_x64__8wekyb3d8bbwe.appx
then
Add-AppxPackage .\Microsoft.UI.Xaml.2.7_7.2208.15002.0_x64__8wekyb3d8bbwe.appx

Then use Add-AppxPackage to install the Windows Terminal msixbundle file. In my case this was:
Add-AppxPackage .\1ff951bd438b4b28b40cb1599e7c9f72.msixbundle

Done!

Hopefully this helps someone else looking for the same answer. I'm happy to have the latest release of Terminal up and running on LTSC!

@ghost commented on GitHub (Sep 13, 2023): @realsarius is correct. To update my original post: I'm running Windows 10 Enterprise LTSC 21H2 (19044.3448) Download the Windows Terminal Windows 10 Preinstall Kit from the releases page. In my case this was: Microsoft.WindowsTerminal_1.17.11461.0_8wekyb3d8bbwe.msixbundle_Windows10_PreinstallKit.zip Extract to a location of your preference. Open an Administrator PowerShell window (right click and run as Administrator). Navigate to the directory you extracted to. Use Add-AppxPackage to install the prerequisites. In my case this was: Add-AppxPackage .\Microsoft.VCLibs.140.00.UWPDesktop_14.0.30704.0_x64__8wekyb3d8bbwe.appx then Add-AppxPackage .\Microsoft.UI.Xaml.2.7_7.2208.15002.0_x64__8wekyb3d8bbwe.appx Then use Add-AppxPackage to install the Windows Terminal msixbundle file. In my case this was: Add-AppxPackage .\1ff951bd438b4b28b40cb1599e7c9f72.msixbundle Done! Hopefully this helps someone else looking for the same answer. I'm happy to have the latest release of Terminal up and running on LTSC!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Issue-Feature Needs-Tag-Fix
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#5394
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?