Unable to open Windows Terminal Preview after installing PowerShell 7.1.3 #13005

Closed
opened 2026-01-31 03:31:14 +00:00 by claunia · 13 comments
Owner

Originally created by @tstephansen on GitHub (Mar 12, 2021).

Environment

Windows build number: 10.0.19042.0
Windows Terminal version (if applicable): 1.7.572.0

Any other software?
Microsoft Store

Steps to reproduce

Install powershell 7.1.3.
This causes Windows Terminal Preview to not open.
Repair Windows Terminal Preview in settings.
Reset Windows Terminal Preview in settings.
Uninstall Windows Terminal Preview.
Reinstall Windows Terminal Preview from the Microsoft Store.

Expected behavior

Windows Terminal Preview should open after installing Powershell 7.1.3.

Actual behavior

Windows Terminal Preview does not open.

EDIT:
I am unable to share feedback for it through the feedback hub. However, I've included the information below from the Diagnostic Data Viewer.

WindowsTerminal.exe

Description
Faulting Application Path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminalPreview_1.7.572.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Creation Time: 3/12/2021 2:03:03 PM
Problem: Stopped working
Status: Report sent

Problem signature
Problem Event Name: MoAppCrash
Package Full Name: Microsoft.WindowsTerminalPreview_1.7.572.0_x64__8wekyb3d8bbwe
Application Name: praid:App
Application Version: 1.7.2102.26002
Application Timestamp: 60394d91
Fault Module Name: Microsoft.Terminal.Settings.Model.dll
Fault Module Version: 1.7.2102.26002
Fault Module Timestamp: 60394b83
Exception Code: c0000005
Exception Offset: 00000000000713c1

Extra information about the problem
Bucket ID: b30ad9210bb5f0c21b3f7f2d191cb448 (1963427794228393032)

Originally created by @tstephansen on GitHub (Mar 12, 2021). # Environment ```none Windows build number: 10.0.19042.0 Windows Terminal version (if applicable): 1.7.572.0 Any other software? Microsoft Store ``` # Steps to reproduce Install powershell 7.1.3. This causes Windows Terminal Preview to not open. Repair Windows Terminal Preview in settings. Reset Windows Terminal Preview in settings. Uninstall Windows Terminal Preview. Reinstall Windows Terminal Preview from the Microsoft Store. # Expected behavior Windows Terminal Preview should open after installing Powershell 7.1.3. # Actual behavior Windows Terminal Preview does not open. EDIT: I am unable to share feedback for it through the feedback hub. However, I've included the information below from the Diagnostic Data Viewer. WindowsTerminal.exe Description Faulting Application Path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminalPreview_1.7.572.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe Creation Time: 3/12/2021 2:03:03 PM Problem: Stopped working Status: Report sent Problem signature Problem Event Name: MoAppCrash Package Full Name: Microsoft.WindowsTerminalPreview_1.7.572.0_x64__8wekyb3d8bbwe Application Name: praid:App Application Version: 1.7.2102.26002 Application Timestamp: 60394d91 Fault Module Name: Microsoft.Terminal.Settings.Model.dll Fault Module Version: 1.7.2102.26002 Fault Module Timestamp: 60394b83 Exception Code: c0000005 Exception Offset: 00000000000713c1 Extra information about the problem Bucket ID: b30ad9210bb5f0c21b3f7f2d191cb448 (1963427794228393032)
claunia added the Needs-TriageResolution-Fix-CommittedNeeds-Tag-Fix labels 2026-01-31 03:31:14 +00:00
Author
Owner

@tstephansen commented on GitHub (Mar 12, 2021):

I tried to debug this myself on my computer and I'm getting the following exception thrown in the Windows.Storage.h file. I'm not an expert at debugging C++ by any means but hopefully this information helps.

Exception thrown at 0x00007FFFAE9A49A7 (Microsoft.Terminal.Settings.Model.dll) in WindowsTerminal.exe: 0xC0000005: Access violation reading location 0x0000000000000000.

It is being called from CascadiaSettingsSerialization.cpp line 493.

auto path = winrt::to_string(foundFolder.Path());

After looking in the debug output window I saw an exception being thrown right before the crash.

Exception thrown at 0x00007FF89F03D759 (KernelBase.dll) in WindowsTerminal.exe: WinRT originate error - 0x80070002 : 'An item cannot be found at the specified path (C:\Program Files\WindowsApps\WhitewaterFoundryLtd.Co.RaftWSL_21.3.0.0_x64__kd1vv0z0vy70w\Public).'.

After I uninstalled Raft WSL I had no problem opening Windows Terminal Preview. Why would Raft WSL affect Windows Terminal Preview from opening?

@tstephansen commented on GitHub (Mar 12, 2021): I tried to debug this myself on my computer and I'm getting the following exception thrown in the Windows.Storage.h file. I'm not an expert at debugging C++ by any means but hopefully this information helps. Exception thrown at 0x00007FFFAE9A49A7 (Microsoft.Terminal.Settings.Model.dll) in WindowsTerminal.exe: 0xC0000005: Access violation reading location 0x0000000000000000. It is being called from CascadiaSettingsSerialization.cpp line 493. auto path = winrt::to_string(foundFolder.Path()); After looking in the debug output window I saw an exception being thrown right before the crash. Exception thrown at 0x00007FF89F03D759 (KernelBase.dll) in WindowsTerminal.exe: WinRT originate error - 0x80070002 : 'An item cannot be found at the specified path (C:\Program Files\WindowsApps\WhitewaterFoundryLtd.Co.RaftWSL_21.3.0.0_x64__kd1vv0z0vy70w\Public).'. After I uninstalled Raft WSL I had no problem opening Windows Terminal Preview. Why would Raft WSL affect Windows Terminal Preview from opening?
Author
Owner

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

Whoa. Whoa. @PankajBhojwani this is in fragment parsing!

@DHowett commented on GitHub (Mar 12, 2021): Whoa. _Whoa_. @PankajBhojwani this is in fragment parsing!
Author
Owner

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

@tstephansen There's a feature that we added in v1.7 that allows a WSL distribution (or other application package) to add a profile to Terminal, or to add a specific configuration to Terminal.

Somebody may need to report to them that their fragment is actually breaking Terminal. We should also not crash when this happens.

@DHowett commented on GitHub (Mar 12, 2021): @tstephansen There's a feature that we added in v1.7 that allows a WSL distribution (or other application package) to add a profile to Terminal, or to add a specific configuration to Terminal. Somebody may need to report to them that their fragment is actually breaking Terminal. We should also not _crash_ when this happens.
Author
Owner

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

Then again: we have this wrapped in an exception handler. Huh.

@DHowett commented on GitHub (Mar 12, 2021): Then again: we have this wrapped in an exception handler. _Huh._
Author
Owner

@tstephansen commented on GitHub (Mar 12, 2021):

Any ideas on why this started happening after installing Powershell 7.1.3? Everything seemed to be working fine until I ran the install. After that I was unable to open terminal. It could be coincidence or either Terminal or Raft could have updated been today. I don't know how to see the version history or update dates for applications in the Microsoft Store so I'm not really sure.

@tstephansen commented on GitHub (Mar 12, 2021): Any ideas on why this started happening after installing Powershell 7.1.3? Everything seemed to be working fine until I ran the install. After that I was unable to open terminal. It could be coincidence or either Terminal or Raft could have updated been today. I don't know how to see the version history or update dates for applications in the Microsoft Store so I'm not really sure.
Author
Owner

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

If you recently got updated from 1.6 to 1.7, that could've caused this. If you go to the "Downloads & Updates" page in the Store (... menu), it'll show you when each application was last updated. Hopefully.

@DHowett commented on GitHub (Mar 12, 2021): If you recently got updated from 1.6 to 1.7, that could've caused this. If you go to the "Downloads & Updates" page in the Store (`...` menu), it'll show you when each application was last updated. Hopefully.
Author
Owner

@crramirez commented on GitHub (Mar 12, 2021):

Hello,

I am sorry for that. A new version of Raft WSL is on the way. I will notify you here when it is life. I couldn't find any workaround.

Regards,
Carlos

@crramirez commented on GitHub (Mar 12, 2021): Hello, I am sorry for that. A new version of Raft WSL is on the way. I will notify you here when it is life. I couldn't find any workaround. Regards, Carlos
Author
Owner

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

@crramirez You're our first public user of fragments, by the way! Would you/one of yours mind e-mailing me and my PM (duhowett@microsoft, cinnamon@microsoft) to chat about them? Thanks.

@DHowett commented on GitHub (Mar 12, 2021): @crramirez You're our first public user of fragments, by the way! Would you/one of yours mind e-mailing me and my PM (duhowett@microsoft, cinnamon@microsoft) to chat about them? Thanks.
Author
Owner

@crramirez commented on GitHub (Mar 13, 2021):

@DHowett sure thanks a lot.

@crramirez commented on GitHub (Mar 13, 2021): @DHowett sure thanks a lot.
Author
Owner

@crramirez commented on GitHub (Mar 15, 2021):

Raft WSL version 21.3.1 is live with the regression in Windows Terminal 1.7 fixed

@crramirez commented on GitHub (Mar 15, 2021): Raft WSL version 21.3.1 is live with the regression in Windows Terminal 1.7 fixed
Author
Owner

@rbeesley commented on GitHub (Mar 19, 2021):

Good catch resolving this. I had this problem for a little while now with the Preview and not on the Production release, so I started diving into Event Viewer to gather details. I was getting the same fault bucket and after updating Raft WSL it resolved the crash.

@rbeesley commented on GitHub (Mar 19, 2021): Good catch resolving this. I had this problem for a little while now with the Preview and not on the Production release, so I started diving into Event Viewer to gather details. I was getting the same fault bucket and after updating Raft WSL it resolved the crash.
Author
Owner

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

:tada:This issue was addressed in #9477, which has now been successfully released as Windows Terminal v1.7.1033.0.🎉

Handy links:

@ghost commented on GitHub (Apr 14, 2021): :tada:This issue was addressed in #9477, which has now been successfully released as `Windows Terminal v1.7.1033.0`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.7.1033.0) * [Store Download](https://www.microsoft.com/store/apps/9n8g5rfz9xk3?cid=storebadge&ocid=badge)
Author
Owner

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

:tada:This issue was addressed in #9477, which has now been successfully released as Windows Terminal Preview v1.8.1032.0.🎉

Handy links:

@ghost commented on GitHub (Apr 14, 2021): :tada:This issue was addressed in #9477, which has now been successfully released as `Windows Terminal Preview v1.8.1032.0`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.8.1032.0) * [Store Download](https://www.microsoft.com/store/apps/9n8g5rfz9xk3?cid=storebadge&ocid=badge)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#13005