Error 0xffffffff starting WSL from WT

[angelog0]

Windows Version

Microsoft Windows [Versione 10.0.19045.2788]

WSL Version

ersione WSL: 1.1.3.0 Versione kernel: 5.15.90.1 Versione WSLg: 1.0.49 Versione MSRDC: 1.2.3770 Versione Direct3D: 1.608.2-61064218 Versione DXCore: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp versione Windows: 10.0.19045.2788

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.90.1

Distro Version

Ubuntu 22.04

Other Software

No response

Repro Steps

I used WSL since it was added to W10 and followed its evolution migrating from WSL1 to WSL2 when it was added. I enabled systemd a few months ago and all worked just fine until today.

Now when I start WSL fro Windows Terminal (WT) it prints

[processo terminato con codice 4294967295 (0xffffffff)]

and in WT prints the message It is possible to configure termination... bla bla

I upgraded WT 1.16.230126001 on January from the msixbundle package and worked just fine

Now I get the above error: it occurs only when I start WSL from WT!!! If I start it using MinTTY, with a link (lnk) whose target is

C:\msys64\usr\bin\mintty.exe -c C:\msys64\home\user\.minttyrc -t "WSL Terminal" --position 20,450 /usr/bin/wslbridge2.exe -d Ubuntu -W "~"

WSL starts without error. As workaround, to start it from WT, I have to reboot but I can only start it once: if I close the Ubuntu tab and restart it the error reappears...

I did not change anything in the configuration: both in Windows and in WSL or WT. May be a Windows upgrade? there was one few days ago.. but until yesterday all worked.. I did also a windows cleaning (System - Archive - temp files etc..) but I worked with WSL up to March 29 21:47 (a timestamp of a file produced by TeXLive) so it is a mistery why now it does not work from WT but only with MinTTY...

Expected Behavior

It should start

Actual Behavior

Error. see above

Diagnostic Logs

No response

[angelog0]

It seems that something was corrupted in my system. Running

sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth

seems to have fixed the issue. Closing this..