Installing WSL 2 as one user results in other users' installations behaving like WSL 1 (despite both users reporting default version = 2)

[davebarkerxyz]

Version

Microsoft Windows [Version 10.0.19043.1466]

WSL Version

• WSL 2
• WSL 1

Kernel Version

5.10.60.1

Distro Version

No response

Other Software

No response

Repro Steps

• Login to Windows as User 1
• Install WSL with wsl --install (rebooting as necessary)
• Run wsl --status and confirm that "Default Version: 2" is indicated
• Import a container image (e.g. wsl --import myorg-ubuntu myorg-ubuntu myorg-ubuntu-base.tar)
• Check that a VHDX file has been created at the import location and that wsl.exe --list --all -v shows the container as being version 2
• Reboot or sign out of Windows (the behaviour is the same in either case)
• Login to Windows as User 2
• Run wsl --status and confirm that "Default Version: 2" is indicated
• Import a container image (e.g. wsl --import myorg-ubuntu myorg-ubuntu myorg-ubuntu-base.tar)

Expected Behavior

As User 2's wsl --status output indicated "Default Version: 2", User 2's import command should generate a VHDX file at the import location, and wsl --list --all -v should show a version 2 container listed (as it did for User 1).

Actual Behavior

Despite wsl --status indicating "Default Version: 2" for both User 1 and User 2, User 2's import command unpacks the tarball to the host filesystem, resulting in a rootfs folder at the import location. The container created is listed by wsl --list --all -v as version 1.

While logged in as User 2, unregistering the container with wsl --unregister myorg-ubuntu, running wsl --set-default-version 2 then re-importing the image creates a version 2 container (with VHDX storage). wsl --status still lists version 2 as the default, but now the behaviour matches the indicated version.

Diagnostic Logs

No response

[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!