Terminal: If the default shell can't be launched and closeOnExit=true, Terminal buys the farm

[KAMiKAZOW]

Environment

Windows build number:  10.0.18362.295
Windows Terminal version: 0.4.2382.0

Steps to reproduce

• Install a WSL distribution (openSUSE Leap 15.0 in my case).
• Move it to top spot and make it default.
• Uninstall old WSL distribution and install the upgraded one (openSUSE Leap 15.1 in my case).

Expected behavior

Remove uninstalled WSL distributions. Add all installed WSL distributions unless explicitly disabled in WT.

Actual behavior

WT closes right away. I'm somehow expected to know the UUID change (wsl.exe --list does not show the UUIDs).

---

Another bug report claims that behavior for non-existent profiles would be handled gracefully in 0.4. Can't confirm that.

[DHowett-MSFT]

You're not actually expected to know the UUID. The distributions are launched by name alone. Check out the name after wsl.exe -d in your profile configuration.

[DHowett-MSFT]

(You can just delete the guid from the new profile, and WT will automatically generate one for you)

[KAMiKAZOW]

WT still closes right on launch.

[JBanks]

We should add in a fail-safe for the event that the default profile has been corrupted. The current settings directory is quite difficult to find for new users, and could discourage experimentation. Perhaps a safe-mode if the past execution exited immediately?

[DHowett-MSFT]

This is now the master bug for "my default shell doesn't launch and it makes me sad because terminal exits instantly"

[DHowett-MSFT]

This will be helped by #2039 and #2091 (or an evolution thereof).

[msftbot[bot]]

:tada:This issue was addressed in #3623, which has now been successfully released as Windows Terminal Preview v0.8.10091.0.:tada:

Handy links:

• Release Notes
• Store Download