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

Windows Terminal Preview v1.18.1462.0 doesn't start on Windows Server 2019 #20293

New Issue
Closed
opened 2026-01-31 07:09:17 +00:00 by claunia · 9 comments
claunia commented 2026-01-31 07:09:17 +00:00
Owner
Copy Link

Originally created by @mhechthz on GitHub (Jul 26, 2023).

Windows Terminal version

No response

Windows build number

Microsoft Windows [Version 10.0.17763.4645]

Other Software

No response

Steps to reproduce

Just start WindowsTermina.exe or wt.exe

Expected Behavior

should run

Actual Behavior

doesn't run

I downloaded the zip File and extracted this to a local directory. On double-clicking WindowsTerminal.exe or wt.exe nothoing ahppens. Running on shell also doesn't work. Also not wt.exe --help.

Add-AppPackage -Path .\Microsoft.WindowsTerminal_Win10_1.16.10261.0_8wekyb3d8bbwe.msixbundle says: Das Paket erfordert auf der Gerätefamilie Windows.Mobile mindestens die Betriebssystemversion 10.0.19041.0.

Originally created by @mhechthz on GitHub (Jul 26, 2023). ### Windows Terminal version _No response_ ### Windows build number Microsoft Windows [Version 10.0.17763.4645] ### Other Software _No response_ ### Steps to reproduce Just start WindowsTermina.exe or wt.exe ### Expected Behavior should run ### Actual Behavior doesn't run I downloaded the zip File and extracted this to a local directory. On double-clicking WindowsTerminal.exe or wt.exe nothoing ahppens. Running on shell also doesn't work. Also not wt.exe --help. Add-AppPackage -Path .\Microsoft.WindowsTerminal_Win10_1.16.10261.0_8wekyb3d8bbwe.msixbundle says: `Das Paket erfordert auf der Gerätefamilie Windows.Mobile mindestens die Betriebssystemversion 10.0.19041.0.`
claunia added the Needs-TriageIssue-Bug labels 2026-01-31 07:09:17 +00:00
claunia commented 2026-01-31 07:09:18 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Jul 26, 2023):

Unfortunately, your Windows version is simply too old. As the message says, it requires at least build 19041, but your Windows is still on 17763. In short, you'll have to upgrade to Windows Server 2022 to use Windows Terminal.
For better or worse, Windows Terminal is built on top of XAML Islands which will not work right on anything older than build 18362. I forgot why we require 19041 now, but I'm pretty sure that 18362 vs 19041 doesn't really matter as the next newer version of Windows Server is 2022, which is build 20348. And the next newer still supported Windows 10 version is 19044.

@lhecker commented on GitHub (Jul 26, 2023): Unfortunately, your Windows version is simply too old. As the message says, it requires at least build 19041, but your Windows is still on 17763. In short, you'll have to upgrade to Windows Server 2022 to use Windows Terminal. For better or worse, Windows Terminal is built on top of XAML Islands which will not work right on anything older than build 18362. I forgot why we require 19041 now, but I'm pretty sure that 18362 vs 19041 doesn't really matter as the next newer version of Windows Server is 2022, which is build 20348. And the next newer still supported Windows 10 version is 19044.
claunia commented 2026-01-31 07:09:18 +00:00
Author
Owner
Copy Link

@mhechthz commented on GitHub (Jul 26, 2023):

So there is no chance to get any (older) version of WindowsTerminal to run on this system?

@mhechthz commented on GitHub (Jul 26, 2023): So there is no chance to get any (older) version of WindowsTerminal to run on this system?
claunia commented 2026-01-31 07:09:18 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Jul 26, 2023):

I believe even the oldest version of Windows Terminal required 18362. You can use OpenConsole with the new text renderer if you'd like to at least get better Unicode support and performance. Doing that however is a bit complicated and/or cumbersome.

@lhecker commented on GitHub (Jul 26, 2023): I believe even the oldest version of Windows Terminal required 18362. You can use OpenConsole with the new text renderer if you'd like to at least get better Unicode support and performance. Doing that however is a bit complicated and/or cumbersome.
claunia commented 2026-01-31 07:09:18 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 26, 2023):

So there is no chance to get any (older) version of WindowsTerminal to run on this system?

That's correct. This is an FAQ topic here: Can I use the Terminal on (Windows 7, Windows Server 2019, any other down-level Windows version)

@zadjii-msft commented on GitHub (Jul 26, 2023): > So there is no chance to get any (older) version of WindowsTerminal to run on this system? That's correct. This is an FAQ topic here: [Can I use the Terminal on (Windows 7, Windows Server 2019, any other down-level Windows version) ](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)
claunia commented 2026-01-31 07:09:18 +00:00
Author
Owner
Copy Link

@mhechthz commented on GitHub (Jul 26, 2023):

Thank You!

@mhechthz commented on GitHub (Jul 26, 2023): Thank You!
claunia commented 2026-01-31 07:09:19 +00:00
Author
Owner
Copy Link

@tsuyo commented on GitHub (Sep 12, 2023):

@lhecker I have the exact issue even on Version 10.0.20348 Build 20348 (Windows Server 2022). wt.exe & WindowsTerminal.exe in the package don't work, but OpenConsole.exe only works. Which log should I check?

@tsuyo commented on GitHub (Sep 12, 2023): @lhecker I have the exact issue even on Version 10.0.20348 Build 20348 (Windows Server 2022). wt.exe & WindowsTerminal.exe in the package don't work, but OpenConsole.exe only works. Which log should I check?
claunia commented 2026-01-31 07:09:19 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Sep 12, 2023):

@tsuyo This issue is about the error message

The package requires OS version 10.0.19041.0 or higher on the Windows.Mobile device
family.

Your issue is probably a different one. You can read more about issues that are specific to Windows Server here: https://github.com/microsoft/terminal/discussions/13983

As DHowett notes in a comment, the "preinstallation kit" contains all the dependencies you need to install it on Windows Server. If you use it (or the manual instructions in the discussion) and the issue still persists, please create a new issue. 🙂

@lhecker commented on GitHub (Sep 12, 2023): @tsuyo This issue is about the error message > The package requires OS version 10.0.19041.0 or higher on the Windows.Mobile device family. Your issue is probably a different one. You can read more about issues that are specific to Windows Server here: https://github.com/microsoft/terminal/discussions/13983 As DHowett notes in a comment, the "preinstallation kit" contains all the dependencies you need to install it on Windows Server. If you use it (or the manual instructions in the discussion) and the issue still persists, please [create a new issue](https://github.com/microsoft/terminal/issues/new/choose). 🙂
claunia commented 2026-01-31 07:09:19 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Sep 12, 2023):

Oh right, I forgot to mention that you can find the preinstall kit on our release page: https://github.com/microsoft/terminal/releases
Each release has a preinstall kit under the assets section.

@lhecker commented on GitHub (Sep 12, 2023): Oh right, I forgot to mention that you can find the preinstall kit on our release page: https://github.com/microsoft/terminal/releases Each release has a preinstall kit under the assets section.
claunia commented 2026-01-31 07:09:19 +00:00
Author
Owner
Copy Link

@tsuyo commented on GitHub (Sep 12, 2023):

@lhecker Thanks for your reply. I referred to #13983, but I can't still open the latest stable version with the same permission issue as #13983. However, I found I can do it with the 1.18 preview version for whatever reason. For now, it's OK, but I believe there might be some issues with the stable version on some environments.

@tsuyo commented on GitHub (Sep 12, 2023): @lhecker Thanks for your reply. I referred to [#13983](https://github.com/microsoft/terminal/discussions/13983), but I can't still open the latest stable version with the same permission issue as #13983. However, I found I can do it with the 1.18 preview version for whatever reason. For now, it's OK, but I believe there might be some issues with the stable version on some environments.
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-Bug Needs-Triage
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#20293
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?