Hello there!
As you are a first time Issuer please read our Code of Conduct.
Please also check whether your issue description is reasonable and complete. If you are having an issue always include the version you are using (WSL, this app, Windows) as well as a way to reproduce it.

Nome do aplicativo com falha: wsl2distromanager.exe, versão: 1.8.15.0, carimbo de data/hora: 0x67325468
Nome do módulo com falha: MSVCP140.dll, versão: 14.29.30037.0, carimbo de data/hora: 0x609de407
Código de exceção: 0xc0000005
Deslocamento da falha: 0x0000000000013020
ID do processo com falha: 0x680c
Hora de início do aplicativo com falha: 0x01db3a90b7ad9ccf
Caminho do aplicativo com falha: E:\Eduardo\Downloads\wsl2dm\wsl2distromanager.exe
Caminho do módulo com falha: E:\Eduardo\Downloads\wsl2dm\MSVCP140.dll
ID do Relatório: 4946b415-b035-4d62-aa48-d7f59636ff24
Nome completo do pacote com falha:
ID do aplicativo relativo ao pacote com falha:

I observed the same issue with the same logs in the event viewer.

windows11 1.8.15闪退

Crashes for me too.

Thanks @eduardotv for providing the log! That helped a lot identifying the issue.

I uploaded a fixed zip file. Could you test it:
https://github.com/bostrot/wsl2-distro-manager/releases/download/v1.8.15/wsl2-distro-manager-v1.8.15+1.zip

I tried the new zip file. It did not work :/

Can you check the event viewer if that is the same issue?

@bostrot Thanks for your reply, the new version is working fine with me 🙏🏻

@bostrot There is another non-critical issue in the new version, I will create a new separated issue, the Tabs aren't selected in each selected page

The new version is working fine also for my part !

It seems to be a different issue for you @Shaikh-Ubaid

Could you open a new issue for this? I will close this one.

Sure, AFK at the moment. Can check it in like few hours from now. How do we check the event viewer?

Also, since the app simply crashed for me, what debugging info can I share about it and how?

Hi @bostrot,

Thank you for the updated version! I tested it, but unfortunately, the issue persists.

I noticed that the MSVCP140.dll library being used during the execution (as seen in the Event Viewer logs) is not the one provided in the app's folder. Instead, it seems to be a version found via the Windows environment's PATH variable. This might be causing the conflict.

Let me know if there's anything else you'd like me to test or provide.

Thanks for your support!