Can't start Windows Terminal after installation

[saw-lau]

Windows Terminal version

1.19.10302.0

Windows build number

10.0.19045.0

Other Software

App Installer 1.21.3482.0.

Steps to reproduce

1. Download Microsoft.WindowsTerminal_1.19.10302.0_8wekyb3d8bbwe.msixbundle from Releases.
2. Double click to install via App Installer.
3. After installation launch.

Expected Behavior

Terminal launches.

Actual Behavior

The following error is displayed:

C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.19.10302.0_x64__8...\WindowsTerminal.exe

File system error (12175).

[github-actions[bot]]

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Closed similar issues:

• Windows Terminal won't start (#4701), similarity score: 0.88
• Windows Terminal fails to start (#12690), similarity score: 0.85
• Windows Terminal Installation Failed (#5932), similarity score: 0.82
• Windows Terminal is unable to start in windows 11 (#14110), similarity score: 0.82
• Can not reset/reinstall Windows Terminal (#16571), similarity score: 0.81

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[saw-lau]

If I download the standalone Microsoft.WindowsTerminal_1.19.10302.0_x64.zip, unzip this and run WindowsTerminal.exe from there it works.

[lhecker]

12175 is either one of these 2 failures:

• ERROR_INTERNET_DECODING_FAILED

  WinINet failed to perform content decoding on the response. For more information, see the Content Encoding topic.

• ERROR_WINHTTP_SECURE_FAILURE

  One or more errors were found in the Secure Sockets Layer (SSL) certificate sent by the server. To determine what type of error was encountered, check for a WINHTTP_CALLBACK_STATUS_SECURE_FAILURE notification in a status callback function. For more information, see WINHTTP_STATUS_CALLBACK.

I'd say you've likely encountered a temporary outage in the app store's backend. Does the issue still occur?

[saw-lau]

12175 is either one of these 2 failures:

[snip]

I'd say you've likely encountered a temporary outage in the app store's backend. Does the issue still occur?

Thanks for the explanation, @lhecker.

I've just tried this again and get the same behaviour.

I'm trying to install this on a corporate laptop which doesn't have access to the Windows Store and is behind a proxy - I wonder if that's the issue? (Although I did manage to install 1.18.10301.0 on another laptop and have just successfully updated this to 1.19.10302.0.)

[lhecker]

I'm trying to install this on a corporate laptop which doesn't have access to the Windows Store and is behind a proxy - I wonder if that's the issue?

Yes that's an issue. The .msixbundle is effectively the same as installing from the app store and just like there, it requires internet access initially for "online activation". [^1]

Instead, you need to use an "offline" installation. Our documentation for that is here: https://learn.microsoft.com/en-us/windows/terminal/distributions Please let me know if you have any issues with that! I'll be closing this issue in the meantime, since we unfortunately can't do anything about it.

[^1]: We're often asked why this is, but we can't answer that because we simply don't know either. This is solely in the hands of the folks who made .msix and the app store.