Terminal version 1.8.* or 1.7.1033.0 installed from scoop or running unpackaged crashes on startup #13438

Closed
opened 2026-01-31 03:42:43 +00:00 by claunia · 16 comments
Owner

Originally created by @vefatica on GitHub (Apr 14, 2021).

An unpackaged installation (unzipped) of 1.8.1032.0 doesn't work. I get a momentary all-white window (correct size/position so I figure the settings file is being read). I also get crash reports in the reliability monitor.

Originally created by @vefatica on GitHub (Apr 14, 2021). An unpackaged installation (unzipped) of 1.8.1032.0 doesn't work. I get a momentary all-white window (correct size/position so I figure the settings file is being read). I also get crash reports in the reliability monitor.
Author
Owner

@DHowett commented on GitHub (Apr 14, 2021):

Unpackaged installations are not, and have never been, officially supported. Sorry.

@DHowett commented on GitHub (Apr 14, 2021): Unpackaged installations are not, and have never been, officially supported. Sorry.
Author
Owner

@vefatica commented on GitHub (Apr 14, 2021):

That may be but until now, they have worked.

@vefatica commented on GitHub (Apr 14, 2021): That may be but until now, they have worked.
Author
Owner

@DHowett commented on GitHub (Apr 14, 2021):

It seems to be broken because of a bug in C++/WinRT (ugh), not some change we made. I'm pursuing the right fix. 😄

@DHowett commented on GitHub (Apr 14, 2021): It seems to be broken because of a bug in C++/WinRT (ugh), not some change we made. I'm pursuing the right fix. :smile:
Author
Owner

@DHowett commented on GitHub (Apr 14, 2021):

FYI- https://github.com/microsoft/cppwinrt/issues/926

@DHowett commented on GitHub (Apr 14, 2021): FYI- https://github.com/microsoft/cppwinrt/issues/926
Author
Owner

@piersmyers commented on GitHub (Apr 15, 2021):

Could I just add to this that using the unpackaged method is the only way to get to use Windows Terminal when the Microsoft Store has been locked down (corporate policy). I had the same crashing in 1.8 so have reverted back to 1.7.

Is it possible to add an official non-store installation please?

@piersmyers commented on GitHub (Apr 15, 2021): Could I just add to this that using the unpackaged method is the only way to get to use Windows Terminal when the Microsoft Store has been locked down (corporate policy). I had the same crashing in 1.8 so have reverted back to 1.7. Is it possible to add an official non-store installation please?
Author
Owner

@igitur commented on GitHub (Apr 15, 2021):

Could I just add to this that using the unpackaged method is the only way to get to use Windows Terminal when the Microsoft Store has been locked down (corporate policy). I had the same crashing in 1.8 so have reverted back to 1.7.

Same here. Microsoft Store is locked down for me. But I can download the .msixbundle file from the Releases page and install it using Add-AppPackage command. Are you not able to do the same?

@igitur commented on GitHub (Apr 15, 2021): > Could I just add to this that using the unpackaged method is the only way to get to use Windows Terminal when the Microsoft Store has been locked down (corporate policy). I had the same crashing in 1.8 so have reverted back to 1.7. Same here. Microsoft Store is locked down for me. But I can download the `.msixbundle` file from the [Releases](https://github.com/microsoft/terminal/releases/tag/v1.7.1033.0) page and install it using `Add-AppPackage` command. Are you not able to do the same?
Author
Owner

@mparry commented on GitHub (Apr 19, 2021):

In case it's of any help at all, the behaviour I see is that 1.8 will crash on start-up unless I run 1.7 first (which I still have a copy of in a parallel directory). If I do that and close it, 1.8 seems to happily run from then onwards, until I reboot and I have to go through the same process again.

@mparry commented on GitHub (Apr 19, 2021): In case it's of any help at all, the behaviour I see is that 1.8 will crash on start-up unless I run 1.7 first (which I still have a copy of in a parallel directory). If I do that and close it, 1.8 seems to happily run from then onwards, until I reboot and I have to go through the same process again.
Author
Owner

@K2ouMais commented on GitHub (Apr 19, 2021):

Unpacked v1.7.1033.0 and 1.8.1032.0 dont work anymore.

The only working version for me is 1.6.10571.0.

Please dont take this away, because we dont have windows store activated on our PCs and dont have any admin rights.

Unpacking it, was the only way to use this great Terminal.

Thank you

@K2ouMais commented on GitHub (Apr 19, 2021): Unpacked v1.7.1033.0 and 1.8.1032.0 dont work anymore. The only working version for me is 1.6.10571.0. Please dont take this away, because we dont have windows store activated on our PCs and dont have any admin rights. Unpacking it, was the only way to use this great Terminal. Thank you
Author
Owner

@DHowett commented on GitHub (Apr 19, 2021):

We're determining the release cadence for this fix. Stay tuned.

@DHowett commented on GitHub (Apr 19, 2021): We're determining the release cadence for this fix. Stay tuned.
Author
Owner

@DHowett commented on GitHub (Apr 19, 2021):

Please dont take this away, because we dont have windows store activated on our PCs and dont have any admin rights.

from @K2ouMais

It is possible to install the msixbundle without the store. You can use Add-AppxPackage from PowerShell, even if you are not an administrator. This is a supported way to use Terminal.

@DHowett commented on GitHub (Apr 19, 2021): > Please dont take this away, because we dont have windows store activated on our PCs and dont have any admin rights. _from @K2ouMais_ It is possible to install the msixbundle _without the store_. You can use `Add-AppxPackage` from PowerShell, even if you are not an administrator. This is a supported way to use Terminal.
Author
Owner

@ghost commented on GitHub (Apr 19, 2021):

:tada:This issue was addressed in #9893, which has now been successfully released as Windows Terminal v1.7.1901.0 (Scoop Compatibility).🎉

@ghost commented on GitHub (Apr 19, 2021): :tada:This issue was addressed in #9893, which has now been successfully released as `Windows Terminal v1.7.1901.0 (Scoop Compatibility)`.:tada:
Author
Owner

@ghost commented on GitHub (Apr 19, 2021):

:tada:This issue was addressed in #9893, which has now been successfully released as Windows Terminal Preview v1.8.1092.0 (Scoop Compatibility).🎉

@ghost commented on GitHub (Apr 19, 2021): :tada:This issue was addressed in #9893, which has now been successfully released as `Windows Terminal Preview v1.8.1092.0 (Scoop Compatibility)`.:tada:
Author
Owner

@alancnet commented on GitHub (Apr 20, 2021):

v1.8.1092.0 worked for me using Add-AppxPackage .\Microsoft.WindowsTerminalPreview_1.8.1092.0_8wekyb3d8bbwe.msixbundle

@alancnet commented on GitHub (Apr 20, 2021): v1.8.1092.0 worked for me using `Add-AppxPackage .\Microsoft.WindowsTerminalPreview_1.8.1092.0_8wekyb3d8bbwe.msixbundle`
Author
Owner

@piersmyers commented on GitHub (Apr 20, 2021):

If I do this:

Import-Module -Name Appx -UseWindowsPowershell
Add-AppxPackage .\Microsoft.WindowsTerminal_1.7.1091.0_8wekyb3d8bbwe.msixbundle

it installs fine but when I click on the Windows Terminal link on the start menu it fails to run and get this error:

image

I suspect this may be down to our over zealous antivirus software. The manually unbundled version of 1.7 still works fine thankfully though.

Ah, the joys of being stuck on a locked down corporate device :(

@piersmyers commented on GitHub (Apr 20, 2021): If I do this: `Import-Module -Name Appx -UseWindowsPowershell` `Add-AppxPackage .\Microsoft.WindowsTerminal_1.7.1091.0_8wekyb3d8bbwe.msixbundle` it installs fine but when I click on the Windows Terminal link on the start menu it fails to run and get this error: ![image](https://user-images.githubusercontent.com/5651200/115369727-4fd3b780-a1c0-11eb-809f-00d3adffb65f.png) I suspect this may be down to our over zealous antivirus software. The manually unbundled version of 1.7 still works fine thankfully though. Ah, the joys of being stuck on a locked down corporate device :(
Author
Owner

@mparry commented on GitHub (Apr 20, 2021):

FWIW, we have similar problems in a constrained environment, except that clicking on the WT link in the Start Menu simply does nothing at all. Manually unbundling is fine.

@mparry commented on GitHub (Apr 20, 2021): FWIW, we have similar problems in a constrained environment, except that clicking on the WT link in the Start Menu simply does nothing at all. Manually unbundling is fine.
Author
Owner

@K2ouMais commented on GitHub (Apr 20, 2021):

FWIW, we have similar problems in a constrained environment, except that clicking on the WT link in the Start Menu simply does nothing at all. Manually unbundling is fine.

Have exactly the same problem... I can install it with "Add-AppxPackage", but when I click on the icon I get an error Message.

wt

@K2ouMais commented on GitHub (Apr 20, 2021): > FWIW, we have similar problems in a constrained environment, except that clicking on the WT link in the Start Menu simply does nothing at all. Manually unbundling is fine. Have exactly the same problem... I can install it with "Add-AppxPackage", but when I click on the icon I get an error Message. ![wt](https://user-images.githubusercontent.com/52510455/115400761-f1233380-a1e9-11eb-96ec-34b13affaa5b.png)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#13438