Need a clear doc page that shows which OS versions Terminal will run on #20395

Closed
opened 2026-01-31 07:12:31 +00:00 by claunia · 5 comments
Owner

Originally created by @kilasuit on GitHub (Aug 22, 2023).

Coming from this issue in the PowerShell Repo (that I created) I found PowerShell has this nice easy to understand document section for supported versions of windows

This Doc is the closest similar one & I think could be updated to show where you expect Terminal to actually run, like as show above would provide much needed clarity going forward.

Originally created by @kilasuit on GitHub (Aug 22, 2023). Coming from this [issue in the PowerShell Repo (that I created)](https://github.com/PowerShell/PowerShell/issues/18148) I found PowerShell has this nice easy to understand document section for [supported versions of windows](https://learn.microsoft.com/en-us/powershell/scripting/install/installing-powershell-on-windows?view=powershell-7.3#supported-versions-of-windows) [This Doc](https://learn.microsoft.com/en-gb/windows/terminal/distributions) is the closest similar one & I think could be updated to show where you expect Terminal to actually run, like as show above would provide much needed clarity going forward.
claunia added the Needs-TriageNeeds-Tag-FixIssue-Docs labels 2026-01-31 07:12:31 +00:00
Author
Owner

@zadjii-msft commented on GitHub (Aug 22, 2023):

I mean, it's pretty front and center at the top of the README

Windows Terminal requires Windows 10 2004 (build 19041) or later

But we can just add a note at the top of that docs page too. No need to have a whole matrix of options - it's just >10.0.19041 for all terminal versions.

@zadjii-msft commented on GitHub (Aug 22, 2023): I mean, it's pretty front and center at the top of the [README](https://github.com/microsoft/terminal#installing-and-running-windows-terminal) > Windows Terminal requires Windows 10 2004 (build 19041) or later But we can just add a note at the top of that docs page too. No need to have a whole matrix of options - it's just >10.0.19041 for all terminal versions.
Author
Owner

@kilasuit commented on GitHub (Aug 22, 2023):

Sorry but this is what I mean by it's not clear & why just using build numbers makes it unclear & would with a matrix with clearer notes as to why it's unsupportable on those os'es would likely have stopped you having ever had the support 2016/2019 issues being raised.
It also does not help that Windows 11 still shows up as Windows 10 in many places
being crystal clear helps stop confusion, and your docs in this case aren't crystal clear, hence the ask for a matrix.
I know to you & others within & outside Microsoft that build numbers make a lot of sense, but the way they are right now is super confusing to many of us, especially if we are managing mixed estates.

Just trying to give some honest and useful feedback here that would definitely help many going forward for what isn't really a big ask in much needed clarity.

@kilasuit commented on GitHub (Aug 22, 2023): Sorry but this is what I mean by it's not clear & why just using build numbers makes it unclear & would with a matrix with clearer notes as to why it's unsupportable on those os'es would likely have stopped you having ever had the support 2016/2019 issues being raised. It also does not help that Windows 11 still shows up as Windows 10 in many places being crystal clear helps stop confusion, and your docs in this case aren't crystal clear, hence the ask for a matrix. I know to you & others within & outside Microsoft that build numbers make a lot of sense, but the way they are right now is super confusing to many of us, especially if we are managing mixed estates. Just trying to give some honest and useful feedback here that would definitely help many going forward for what isn't really a big ask in much needed clarity.
Author
Owner

@kilasuit commented on GitHub (Aug 22, 2023):

Also I'm lucky in that I do understand build numbers to an extent having been a Windows Insider since 2014, but having to play the calculation game on things like which of the LTSC builds this is supported on, is time me & others shouldn't be needing to waste in trying to work out when a matrix would solve it

@kilasuit commented on GitHub (Aug 22, 2023): Also I'm lucky in that I do understand build numbers to an extent having been a Windows Insider since 2014, but having to play the calculation game on things like which of the LTSC builds this is supported on, is time me & others shouldn't be needing to waste in trying to work out when a matrix would solve it
Author
Owner

@zadjii-msft commented on GitHub (Aug 23, 2023):

Moved to our docs repo: https://github.com/MicrosoftDocs/terminal/issues/701

@zadjii-msft commented on GitHub (Aug 23, 2023): Moved to our docs repo: https://github.com/MicrosoftDocs/terminal/issues/701
Author
Owner

@kilasuit commented on GitHub (Aug 23, 2023):

sorry for raising in the wrong repo @zadjii-msft & thank you for raising in the right one!

@kilasuit commented on GitHub (Aug 23, 2023): sorry for raising in the wrong repo @zadjii-msft & thank you for raising in the right one!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#20395