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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Installing Microsoft Windows Terminal on Windows Server 2019 editions #7560
Comments
@nunix can provide some useful info here. |
Yes but Nuno found a way to get it working. Hence why I tagged him. |
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! |
@DHowett is the terminal going to work on Windows Server 2022? |
If it has the desktop experience package, yes. |
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 |
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 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. |
馃毃馃毃馃毃馃毃馃毃馃毃馃毃馃毃馃毃馃毃
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
Use any non-core editions of Windows Server (Any year). My use case is Windows Server 2019 Standard.
Attempt installation of Microsoft Windows Terminal by either (2a) Add-AppxPackage from release on GitHub OR (2b) via chocolatey package manager.
2a.
2b.
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):
For method (2b - chocolatey package manager install):
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.
The text was updated successfully, but these errors were encountered: