About one year ago I wrote a small blog piece in Swedish regarding my problem with using WSL2 on my laptop and how to work around it by restarting the VMMS (Virtual Machine Management Service). I have been following the WSL GITHUB Issue 5401, to see if somebody would find a better solution/workaround.
After christmas (one year later) I got ”fed up” with constantly restarting the VMMS service, so I revisited the problem AND FOUND A PERMANENT SOLUTION!
The problem and solution is described in this Microsoft article for Hyper-V (I used method #3).
The solution is that your domain administrator has to add the special identity group ”NT VIRTUAL MACHINE\Virtual Machines” (SID S-1-5-83-0) to the Group Policy that modifies the ”Logon as a service” names and groups.
In my case it was the ”Default Domain Policy” that needed to be modified.
The operation (to add the special group to the GPO) has to be performed from a computer which has Hyper-V installed in some form, as the special group is local and only created when the Hyper-V functionality is enabled on the computer.
If you inspect the (fixed) Logon as service properties for the GPO from a computer without Hyper-V enabled, you will only see the Well Known SID S-1-5-83-0 in place of the group name.
When the updated GPO has been applied to your computer, the problem is gone and you can consistently start WSL!