The issue is almost certainly related to WSL2 not being shut down properly and has been occurring in WSL2 for months. See the descriptions in [1] and [2] which

The issue is almost certainly related to WSL2 not being shut down properly and has been occurring in WSL2 for months. See the descriptions in [1] and [2] which are both linked to from the original thread [3]. [1]: https://github.com/microsoft/WSL/issues/5026 https://github.com/microsoft/WSL/issues/5026 [2]: https://github.com/microsoft/WSL/issues/5895 https://github.com/microsoft/WSL/issues/5895 [3]: https://github.com/microsoft/WSL2-Linux-Kernel/issues/168#issuecomment-726540828 https://github.com/microsoft/WSL2-Linux-Kernel/issues/168#is...