Closed jxy-s closed 1 month ago
If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.
/emailed-logs
This is by design. If you don't want users to be able to use the inbox version of WSL (which does not support Intune policies) you must set this policy to false.
Allow the Inbox version of the Windows Subsystem for Linux https://learn.microsoft.com/en-us/windows/wsl/intune#recommended-settings
Windows Version
10.0.22631.4317
WSL Version
0.0.0.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.10.102.1
Distro Version
Ubuntu 22.04
Other Software
No response
Repro Steps
wsl --install -d Ubuntu
wsl
wsl --uninstall
wsl
WSL Service
(wslservice.exe
)wsl --list -v
WSL Service
.Note: I am not sure if this is an expected configuration or state for WSL or not. I am unable to find any documentation on this. But overall it seems like undesired behavior at best or a potential security vulnerability or bypass at worst.
Expected Behavior
When WSL2 is active on the machine and WSL plugins are registered with the Windows Subsystem for Linux. Starting virtual machines or distribution containers should result in the WSL plugin being notified of this activity.
Actual Behavior
When WSL is "uninstalled"(
wsl --uninstall
) the WSL2 virtual machines and containers are still allowed to start despite the WSL Service not being installed and active on the system. This results in WSL plugins not being notified of WSL2 activity on the system.Another consequence of this state is that certain commands do not result in expected:
Diagnostic Logs
No response