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

Installing Microsoft Windows Terminal on Windows Server 2019 editions #10537

New Issue
Closed
opened 2026-01-31 02:24:08 +00:00 by claunia · 11 comments
claunia commented 2026-01-31 02:24:08 +00:00
Owner
Copy Link

Originally created by @Jayonics on GitHub (Sep 8, 2020).

🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨

Environment

Windows Version: Windows Server 2019 - Standard

Windows build number: Win32NT 10.0.17763.0 Microsoft Windows NT 10.0.17763.0
Windows Terminal version: None successfully installed, attempted installation on version 1.2.2381.0

Any other software?
Chocolatey (As an attempted alternate means of installation besides PowerShell 'Add-AppxPackage' )

Steps to reproduce

  1. Use any non-core editions of Windows Server (Any year). My use case is Windows Server 2019 Standard.

  2. Attempt installation of Microsoft Windows Terminal by either (2a) Add-AppxPackage from release on GitHub OR (2b) via chocolatey package manager.

2a.

image

2b.

image

Expected behavior

Microsoft Windows Terminal Installs successfully and can be run the same way it is run on Windows 10 editions that do not install it via the Microsoft Store.

Actual behavior

Errors in the installation of Microsoft Windows Terminal due to incompatible OS builds of Windows Server editions (Non-core) that are behind the OS builds of Windows 10.

For method (2a - Powershell AppxPackage install):
image

For method (2b - chocolatey package manager install):
image

NOTES: It seems unlikely that this can be resolved via installing the current Windows Terminal version in any way on Non-core versions of Windows Server. Perhaps a less eloquent solution to this problem would be installing the last compatible Microsoft Windows Terminal release with a supported OS version of 10.0.17763.1432 (My Windows Server 2019 Standard current OS version) or lower. If anyone knows what release of Microsoft Windows Terminal last supported that version it could, at least be a temporary fix for installation of this program.

Sorry if this is a comment, but it appears as if the thread content has disappeared so I am reposting it here.

Originally created by @Jayonics on GitHub (Sep 8, 2020). 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 # Environment Windows Version: Windows Server 2019 - Standard Windows build number: Win32NT 10.0.17763.0 Microsoft Windows NT 10.0.17763.0 Windows Terminal version: None successfully installed, attempted installation on version 1.2.2381.0 Any other software? Chocolatey (As an attempted alternate means of installation besides PowerShell 'Add-AppxPackage' ) # Steps to reproduce 1. Use any non-core editions of Windows Server (Any year). My use case is Windows Server 2019 Standard. 2. Attempt installation of Microsoft Windows Terminal by either (2a) Add-AppxPackage from release on GitHub OR (2b) via chocolatey package manager. 2a. ![image](https://user-images.githubusercontent.com/45290659/92467974-529e1100-f1ca-11ea-9146-312b4e94b571.png) 2b. ![image](https://user-images.githubusercontent.com/45290659/92468026-69dcfe80-f1ca-11ea-91b7-344278126654.png) # Expected behavior Microsoft Windows Terminal Installs successfully and can be run the same way it is run on Windows 10 editions that do not install it via the Microsoft Store. # Actual behavior Errors in the installation of Microsoft Windows Terminal due to incompatible OS builds of Windows Server editions (Non-core) that are behind the OS builds of Windows 10. For method (2a - Powershell AppxPackage install): ![image](https://user-images.githubusercontent.com/45290659/92467247-2afa7900-f1c9-11ea-93a7-82410d9a2e4e.png) For method (2b - chocolatey package manager install): ![image](https://user-images.githubusercontent.com/45290659/92467331-52e9dc80-f1c9-11ea-87d8-7982c70bff48.png) NOTES: It seems unlikely that this can be resolved via installing the current Windows Terminal version in any way on Non-core versions of Windows Server. Perhaps a less eloquent solution to this problem would be installing the last compatible Microsoft Windows Terminal release with a supported OS version of 10.0.17763.1432 (My Windows Server 2019 Standard current OS version) or lower. If anyone knows what release of Microsoft Windows Terminal last supported that version it could, at least be a temporary fix for installation of this program. Sorry if this is a comment, but it appears as if the thread content has disappeared so I am reposting it here.
claunia added the Resolution-Duplicate label 2026-01-31 02:24:08 +00:00
claunia commented 2026-01-31 02:24:09 +00:00
Author
Owner
Copy Link

@WSLUser commented on GitHub (Sep 8, 2020):

@nunix can provide some useful info here.

@WSLUser commented on GitHub (Sep 8, 2020): @nunix can provide some useful info here.
claunia commented 2026-01-31 02:24:09 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Sep 8, 2020):

I'm fairly sure Windows Server 2019 isn't supported (see issues #2177, #6717, and #6956). Also see issue #1643 for more info on what would be required to get the Windows Terminal running on older versions of Windows.

@j4james commented on GitHub (Sep 8, 2020): I'm fairly sure Windows Server 2019 isn't supported (see issues #2177, #6717, and #6956). Also see issue #1643 for more info on what would be required to get the Windows Terminal running on older versions of Windows.
claunia commented 2026-01-31 02:24:10 +00:00
Author
Owner
Copy Link

@WSLUser commented on GitHub (Sep 8, 2020):

Yes but Nuno found a way to get it working. Hence why I tagged him.

@WSLUser commented on GitHub (Sep 8, 2020): Yes but Nuno found a way to get it working. Hence why I tagged him.
claunia commented 2026-01-31 02:24:10 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Sep 8, 2020):

Terminal has never run on a version of Windows below 18362. Sorry!

/dup #2177 #6717 #1643

@DHowett commented on GitHub (Sep 8, 2020): Terminal has never run on a version of Windows below 18362. Sorry! /dup #2177 #6717 #1643
claunia commented 2026-01-31 02:24:10 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Sep 8, 2020):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Sep 8, 2020): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
claunia commented 2026-01-31 02:24:10 +00:00
Author
Owner
Copy Link

@AndrewSav commented on GitHub (Mar 27, 2021):

@DHowett is the terminal going to work on Windows Server 2022?

@AndrewSav commented on GitHub (Mar 27, 2021): @DHowett is the terminal going to work on [Windows Server 2022](https://cloudblogs.microsoft.com/windowsserver/2021/03/02/announcing-windows-server-2022-now-in-preview/)?
claunia commented 2026-01-31 02:24:10 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Mar 27, 2021):

If it has the desktop experience package, yes.

@DHowett commented on GitHub (Mar 27, 2021): If it has the desktop experience package, yes.
claunia commented 2026-01-31 02:24:10 +00:00
Author
Owner
Copy Link

@gahan9 commented on GitHub (Dec 31, 2021):

Any minimalistic implementation of windows terminal can be provided for Server 2019? since I find most helpful feature is using tabs for different terminal [powershell, command prompt, git bash etc] and also allows connection to quick connect to ssh system.

Don't care much about graphics experience and rendering, but how about having a window capable of at least launching session as per json structure? I just think that performance and experience of windows terminal is better than ConEmu and certainly want that experience to expand to Server 2019

@gahan9 commented on GitHub (Dec 31, 2021): Any minimalistic implementation of windows terminal can be provided for Server 2019? since I find most helpful feature is using tabs for different terminal [powershell, command prompt, git bash etc] and also allows connection to quick connect to ssh system. Don't care much about graphics experience and rendering, but how about having a window capable of at least launching session as per json structure? I just think that performance and experience of windows terminal is better than [ConEmu](https://conemu.github.io/) and certainly want that experience to expand to Server 2019
claunia commented 2026-01-31 02:24:11 +00:00
Author
Owner
Copy Link

@cwanized commented on GitHub (Oct 24, 2022):

Any chance to see a Windows Terminal version for Windows Server 2019? We currently update 70 environments to SfB 2019 which only is supported with Windows Server 2019 (thanks MS) - Windows Server 2019 is supported till 2029 and it would be a bummer if we can't use Windows terminal for our next server generation. As others already said, we can live with a subset of the features but a basic version of Windows terminal would be helfpul for the future...

@cwanized commented on GitHub (Oct 24, 2022): Any chance to see a Windows Terminal version for Windows Server 2019? We currently update 70 environments to SfB 2019 which only is supported with Windows Server 2019 (thanks MS) - Windows Server 2019 is supported till 2029 and it would be a bummer if we can't use Windows terminal for our next server generation. As others already said, we can live with a subset of the features but a basic version of Windows terminal would be helfpul for the future...
claunia commented 2026-01-31 02:24:11 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Oct 24, 2022):

@cwanized Sorry, but probably not. There aren't just optional parts of the Terminal we could disable on server 2019, there's fundamental OS features we rely on that are missing entirely. If server is what you need, then Server 2022 is where you're gonna get the Terminal.

@zadjii-msft commented on GitHub (Oct 24, 2022): @cwanized Sorry, but probably not. There aren't just optional parts of the Terminal we could disable on server 2019, there's fundamental OS features we rely on that are missing entirely. If server is what you need, then Server 2022 is where you're gonna get the Terminal.
claunia commented 2026-01-31 02:24:11 +00:00
Author
Owner
Copy Link

@Jayonics commented on GitHub (Oct 29, 2022):

@cwanized Sorry, but probably not. There aren't just optional parts of the Terminal we could disable on server 2019, there's fundamental OS features we rely on that are missing entirely. If server is what you need, then Server 2022 is where you're gonna get the Terminal.

At the time Windows server 2022 was not out but as you said, windows terminal works fine on windows server 2022.

@Jayonics commented on GitHub (Oct 29, 2022): > @cwanized Sorry, but probably not. There aren't just optional parts of the Terminal we could disable on server 2019, there's fundamental OS features we rely on that are missing entirely. If server is what you need, then Server 2022 is where you're gonna get the Terminal. At the time Windows server 2022 was not out but as you said, windows terminal works fine on windows server 2022.
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 Resolution-Duplicate
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#10537
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?