terminal: On windows 10 (19044.2604, 21H2), windows terminal from v1.16.2023.0 to v1.17.1023 doesn't work.

I’m curious that why the version is not 1.18.1462.0

Oh, technically the Terminal version numbers in the packaged version use the app package catalog to generate that string. For the unpackaged builds, since we obviously can’t use the package version, we instead just stamp the “timestamp” into the build. So 1.18.1462.0 == 1.18.239526002 == the second build on the 26th of May of 2023

@D-Maxwell if you’re still seeing this with 1.18 Stable / 1.19 Preview (which came out this week), can you grab dumps using these steps and send them to us? That’d be helpful.

Actually, in that case, I might just have you file a new thread, since whatever issue OP was seeing is clearly gone by 1.18. I don’t want to cross pollute this solved thread with notes from a new regression 😉

Looping back on this.

• This doesn’t seem like it’s the other admin crashes we’re seeing circa 1.17 (the IPackageStatics ones)
• No dump is generated, which makes it seeem like Terminal isn’t crashing, it’s just failing to launch.
• I really don’t think this is the N SKU thing. I thought we patched that all up by now.
  • which was: #13751
  • fixed in ce26137128f2ccd28b1ac21a249c100c88b740a9,
    • in https://github.com/microsoft/terminal/tree/v1.15.2874.0
    • NOT in https://github.com/microsoft/terminal/tree/v1.16.2641.0
    • does look like it was in https://github.com/microsoft/terminal/tree/v1.17.1023.0
  • so it’s not that

Can you maybe try downloading the .zip[^1] from https://github.com/microsoft/terminal/releases/tag/v1.18.1462.0, and running windowsterminal.exe directly/? If that really does nothing, then there might be something in in event viewer. I’m honestly not well versed in Event Viewer though.

[^1]: the correct one for your arch, of course

Okay, another thing to test.

Can you capture an ETL trace, following these steps?

That’ll tell us definitively if the Terminal is started at all. If it is, then that might give us a place to narrow it down. If Terminal isn’t started, then… oof.