Update documentation for WSL_DISTRIBUTION_FLAGS for WSL2

[DDoSolitary]

When a distro gets upgraded to WSL2 using wsl /set-version, its Flags registry key is ORed with a new bit flag 0x08, which is not documented for now. It would be nice to have official explanation/documentation for this new flag.

[benhillis]

@DDoSolitary - We are not going to document internal registry state because it is subject to change.

[DDoSolitary]

@benhills The registry value isn't internal at all. It's directly exposed via the argument wslDistributionFlags of the function WslGetDistributionConfiguration which is part of the public API.

[benhillis]

Fair enough. We will update the document when the new flag ships outside of insider builds. FYI setting the flag via that API will not work.

[therealkenc]

It would be nice to have official explanation/documentation for this new flag.

Next one of these please post over in MicrosoftDocs/WSL.

[Biswa96]

The lxss registry isn't changed in three years. Why it can't be documented? It may fix many things in simple ways. For example, to move a WSL2 distribution one can move the VHDX file and change the BasePath registry and done. No need to do import/export. Another example, one can parse the lxss registry key and implement their own wsl -l -v style output. Another example, users can change distribution name easily.

Do we have to wait 1 year to get the WSL2 flag?

[microsoft-github-policy-service]

This issue has been automatically closed since it has not had any activity for the past year. If you're still experiencing this issue please re-file this as a new issue or feature request.

Thank you!