WSL2: After having started new WSL instance many times, it doesn't start any more.

[0xbadfca11]

• Your Windows build number:
  Microsoft Windows [Version 10.0.18917.1000]

• What you're doing and what's happening:
  Every time start a new WSL instance, ext4.vhdx is given a new ACL.
  When after it starts approximately 2000 times, WSL will not start.

Batch file for reproduction

:start
wsl -e /bin/true
wsl --shutdown
goto start

The inherited access control list (ACL) or access control entry (ACE) could not be built.

• What's wrong / what should be happening instead:
  Starts fine anytime.

• For WSL launch issues, please collect detailed logs.
  lxcore.zip

[benhillis]

Excellent bug! I will take a look.

[benhillis]

If you get into this state, you can remove the GUID ACLs from the file via Properties -> Security -> Edit and removing the GUID entries from the "Group or user name"list.

[wisq]

I just experienced this bug and had to delete (presumably some 2000) ACLs from my ext4.vhdx file to get WSL working again. Is there some update process I need to apply to get this fix?

[ggodool]

I just experienced this bug too. And I also had to delete GUID ACLS from my ext4.vhdx too.
Could you fix this bug?

[darkzbaron]

Have the same issue, the fix works but it's annoying.