Windows Terminal cannot be launched and cannot be uninstalled/repaired

[slaymaker1907]

Windows Terminal version

1.16.10262.0

Windows build number

10.0.22621.0

Other Software

No response

Steps to reproduce

I hit close while running SQL Server in the Terminal (it is a custom build as I am on the SQL team) and it seems to have catastrophically corrupted Windows Terminal somehow to such a degree that it can't even be uninstalled.

Expected Behavior

I should be able to launch and uninstall.

Actual Behavior

Whenever it crashes, the following error is being reported in Event Viewer:

Faulting application name: WindowsTerminal.exe, version: 1.16.2301.26002, time stamp: 0x63d332f5
Faulting module name: Microsoft.Terminal.Settings.Model.dll, version: 1.16.2301.26002, time stamp: 0x63d3317c
Exception code: 0xc0000005
Fault offset: 0x00000000000fa96d
Faulting process id: 0x0x4D48
Faulting application start time: 0x0x1D97886AD310BBC
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.16.10262.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.16.10262.0_x64__8wekyb3d8bbwe\Microsoft.Terminal.Settings.Model.dll
Report Id: 5e9724bf-5d0a-452f-983a-dc42cc63b894
Faulting package full name: Microsoft.WindowsTerminal_1.16.10262.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

When I attempt to uninstall, I get error 0x80073cfa from Windows Settings.

[DHowett]

Wow, that's not great. Do you have any dumps on your machine or a post mortem / JIT / remote you can share out? I've never seen this particular failure before, and I couldn't find any watsons in this module that matched up with that offset.

[slaymaker1907]

Now it seems to be in a partially removed state such that I can't replicate it (it still shows up in search, but it does not show up in Windows Settings). However, I did find a few dumps (internal to Microsoft).

[DHowett]

So, the one thing I can see in this Terminal dump is an AV querying the Visual Studio Setup COM objects. That's surprising. We absolutely shouldn't AV there.