WSL Not Being Populated In Terminal Options if WSL Is Installed After Terminal.

[ZacharySeebeck2020]

Environment

Windows build number: 10.0.18362.0
Windows Terminal version (if applicable): 0.4.2382.0

Any other software? Ubunutu WSL

Steps to reproduce

To reproduce, on an install of Windows that has never had WSL enabled or installed, install the new Windows Terminal preview from the store. Open it to allow itself to get through any first initialization stuff it needs. Then enable WSL and install a Linux distribution. In my case it was Ubuntu but I have a feeling it would break for the others too.

Expected behavior

In the event that you install the new terminal first before you install WSL, that terminal would pick up on the next launch that there has been a new distribution installed and that it needs to add a basic profile into the settings JSON.

Actual behavior

Nothing happens and the Terminal is left with the same options as before. In my case the default options of CMD, Powershell, and Azure.

[DHowett-MSFT]

/dup #754

[ghost]

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!