Windows Server 2016 #20863

Closed
opened 2026-01-31 07:26:12 +00:00 by claunia · 1 comment
Owner

Originally created by @RJurjevic on GitHub (Nov 21, 2023).

Windows Terminal version

1.18.2822.0

Windows build number

10.0.14393

Other Software

No response

Steps to reproduce

Run WindowsTerminal.exe and it won't start.

Expected Behavior

WindowsTerminal.exe should have started.

Actual Behavior

WindowsTerminal.exe failed to start as it seems it did not find a function in a DLL. The error was "The procedure entry point SetThreadDescription could not be located in the dynamic link library."

Originally created by @RJurjevic on GitHub (Nov 21, 2023). ### Windows Terminal version 1.18.2822.0 ### Windows build number 10.0.14393 ### Other Software _No response_ ### Steps to reproduce Run WindowsTerminal.exe and it won't start. ### Expected Behavior WindowsTerminal.exe should have started. ### Actual Behavior WindowsTerminal.exe failed to start as it seems it did not find a function in a DLL. The error was "The procedure entry point SetThreadDescription could not be located in the dynamic link library."
claunia added the Needs-TriageIssue-Bug labels 2026-01-31 07:26:12 +00:00
Author
Owner

@zadjii-msft commented on GitHub (Nov 21, 2023):

Yep, it sure won't work on Server 2016!

The minimum required Windows version for the Terminal is 19041. See our FAQ for more details.

@zadjii-msft commented on GitHub (Nov 21, 2023): Yep, it sure won't work on Server 2016! The minimum required Windows version for the Terminal is 19041. See our [FAQ ](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)for more details.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#20863