Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How do I install Windows Terminal on a Windows Server 2019 system? #1483

Closed
David-Noble-at-work opened this issue Jun 23, 2019 · 13 comments
Closed
Assignees
Labels
Issue-Docs It's a documentation issue that really should be on MicrosoftDocs/Console-Docs Product-Terminal The new Windows Terminal. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@David-Noble-at-work
Copy link

I don't have access to the Store app. Must I build or can I download an installer to try out Windows Terminal?

@David-Noble-at-work David-Noble-at-work added the Issue-Docs It's a documentation issue that really should be on MicrosoftDocs/Console-Docs label Jun 23, 2019
@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Jun 23, 2019
@VimalShekar
Copy link

+1
Need the appx package so we can use this on Windows Server.

@alexrjs
Copy link

alexrjs commented Jun 24, 2019

Yup, in some companies, Windows Store is simply disabled, so a download alternative would be excellent...

@DHowett-MSFT
Copy link
Contributor

I'm going to make #1386 the master issue for alternate distribution mechanisms. Thanks!

@DHowett-MSFT DHowett-MSFT added Product-Terminal The new Windows Terminal. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Jun 24, 2019
@TroelsWibergJensen
Copy link

I have not been able to install Windows Terminal on a Server 2019 machine!
image

@DHowett
Copy link
Member

DHowett commented Sep 8, 2020

That error message indicates that your build of Windows is too old.

@ReillyBrogan
Copy link

@DHowett Well, can the install requirement be reduced to 1809 instead? Or does it rely on APIs that aren't present in that version?

@DHowett
Copy link
Member

DHowett commented Sep 12, 2020

It does rely on APIs that are only present in 1903 and above.

@DHowett
Copy link
Member

DHowett commented Sep 12, 2020

If we did not have a technical limitation, we would not impose such an otherwise arbitrary restriction.

@David-Noble-at-work
Copy link
Author

I just installed the latest Windows Server 2019, the September 2020 release, OS Version 10.0.17763.1457. Apparently that's not sufficient for Windows Terminal which requires 10.0.18362.0 or greater. Where does one get a copy of Windows Server 2019 that meets the requirements imposed by the current Windows Terminal?

@zadjii-msft
Copy link
Member

@David-Noble-at-work I don't believe there's a Windows Server release at/above version 10.0.18362 yet, sorry 😞

@ReillyTevera
Copy link

@David-Noble-at-work @zadjii-msft That's not completely true. You are correct that there is not yet a full release (2019, 2016 etc) past that version however Windows Server is also available under the "Semi-Annual" release channel which follows the cadence of Windows 10 releases. You need to have volume licensing and active Software Assurance to use that channel however, and given that Microsoft has had some major QA issues around the Windows 10 feature releases (and Windows Server shares the same codebase) I wouldn't recommend using that for any workload that is something you care about, especially if your only reason for using those releases is for Windows Terminal.

@soundarmoorthy
Copy link

Why not have a simple installer that can be used to install it on windows server 2019 ? Does it require any dependencies that would complicate the installation in windows server 2019 ? I am reasonably sure that much of the IT Admin community would appreciate such an availability. Forget 2019, i am not able to install on 2016 as well, If that helps.

@DHowett
Copy link
Member

DHowett commented Nov 15, 2020

#1483 (comment)

#1483 (comment)

Please consider reading a thread before you comment on it.

@microsoft microsoft locked as resolved and limited conversation to collaborators Nov 15, 2020
@ghost ghost removed the Needs-Tag-Fix Doesn't match tag requirements label Nov 15, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Issue-Docs It's a documentation issue that really should be on MicrosoftDocs/Console-Docs Product-Terminal The new Windows Terminal. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests