Doesn't start on server 2022 preview #13054

Closed
opened 2026-01-31 03:32:22 +00:00 by claunia · 7 comments
Owner

Originally created by @matsmcp on GitHub (Mar 16, 2021).

Environment

Windows build number: 10.0.20303.1
Windows Terminal version (if applicable): 1.6.10571.0

Any other software?
no

Steps to reproduce

Download.
Install with add-appxpackage -path "path to your download"
Click on windows terminal in start menu.
A white line is shown for a short period under the Windows terminal line.
The terminal never starts

Expected behavior

Running windows terminal

Actual behavior

Nothing

This is on a machine without internet access. That is the norm for our servers

Originally created by @matsmcp on GitHub (Mar 16, 2021). # Environment Windows build number: 10.0.20303.1 Windows Terminal version (if applicable): 1.6.10571.0 Any other software? no # Steps to reproduce Download. Install with add-appxpackage -path "path to your download" Click on windows terminal in start menu. A white line is shown for a short period under the Windows terminal line. The terminal never starts # Expected behavior Running windows terminal # Actual behavior Nothing This is on a machine without internet access. That is the norm for our servers
claunia added the Resolution-Duplicate label 2026-01-31 03:32:22 +00:00
Author
Owner

@skyline75489 commented on GitHub (Mar 16, 2021):

Well, theoretically Server 2022 should have everything in 1903 (18362), I think @DHowett might be interested in this.

@skyline75489 commented on GitHub (Mar 16, 2021): Well, theoretically Server 2022 should have everything in 1903 (18362), I think @DHowett might be interested in this.
Author
Owner

@matsmcp commented on GitHub (Mar 16, 2021):

I did some more digging.

I now have 2 2022 servers.

The First one is virtual and air gapped
Here Windows Terminal doesn't start.

The seccond one is a Whitebox I assembled at home (benefit of working from home).
On this one Windows terminal do Work.

Therefore I suspect this could be some kind of dependency issue that resolves it self if you have an internet connection.
Both boxes can be reinstalled anytime so I'm happy to help troubleshot

@matsmcp commented on GitHub (Mar 16, 2021): I did some more digging. I now have 2 2022 servers. The First one is virtual and air gapped Here Windows Terminal doesn't start. The seccond one is a Whitebox I assembled at home (benefit of working from home). On this one Windows terminal do Work. Therefore I suspect this could be some kind of dependency issue that resolves it self if you have an internet connection. Both boxes can be reinstalled anytime so I'm happy to help troubleshot
Author
Owner

@WSLUser commented on GitHub (Mar 16, 2021):

You're hitting https://github.com/microsoft/terminal/issues/6010. Specifically this: https://github.com/microsoft/terminal/issues/6010#issuecomment-792800655. As stated in the issue a few times, the only possible workaround would be the pre-installation kit.

Note: With Server now starting to have this support, addressal of that issue will become critically more important even if a different team is responsible for addressing it (the msix team).

@WSLUser commented on GitHub (Mar 16, 2021): You're hitting https://github.com/microsoft/terminal/issues/6010. Specifically this: https://github.com/microsoft/terminal/issues/6010#issuecomment-792800655. As stated in the issue a few times, the only possible workaround would be the pre-installation kit. Note: With Server now starting to have this support, addressal of that issue will become critically more important even if a different team is responsible for addressing it (the msix team).
Author
Owner

@DHowett commented on GitHub (Mar 16, 2021):

/dup #6010

This is just the appLicensing issue.

@DHowett commented on GitHub (Mar 16, 2021): /dup #6010 This is just the appLicensing issue.
Author
Owner

@ghost commented on GitHub (Mar 16, 2021):

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!

@ghost commented on GitHub (Mar 16, 2021): 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!
Author
Owner

@matsmcp commented on GitHub (Mar 16, 2021):

Extracting the files did work.
Now looking at building a MSI for it

@matsmcp commented on GitHub (Mar 16, 2021): Extracting the files did work. Now looking at building a MSI for it
Author
Owner

@DHowett commented on GitHub (Mar 16, 2021):

If you're trying for offline deployment, why can you not just use the "Preinstall Kit" shipped with Windows Terminal Stable? It contains an offline licensing package and everything you need to run terminal offline... without resorting to our unsupported unpackaged activation path.

@DHowett commented on GitHub (Mar 16, 2021): If you're trying for offline deployment, why can you not just use the "Preinstall Kit" shipped with Windows Terminal Stable? It contains an offline licensing package and everything you need to run terminal offline... _without_ resorting to our unsupported unpackaged activation path.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#13054