uet
uet copied to clipboard
WSL can't be started as SYSTEM
For Windows+WSL mode, wsl.exe doesn't work when the service is running as SYSTEM. Upon further investigation, it appears if you're running as SYSTEM, you can't runas into any other user - even if you know the password.
The only way I can see to workaround this is by having RKM create a second service that runs as a generated RKM user, and have that service let the main service interact with WSL via HTTP calls. It's total junk, but I don't see any other way of making this work out of the box.
The experiment to provision a local user and use runas is in the wsl-system branch, though it doesn't for the reasons listed in the issue description.