Can not open files in WSL with double-click or Enter since Win11 24H2 update

[TCUserAndFan]

Until yesterday I was perfectly able to open any file from within Total Command 11.51, also my files inside a WSL distro.

Then I got the 24H2 update for Windows 11 (it was definitely working before, I opened files several times a day)
I can still browse my WSL, see all the files etc.

https://postimg.cc/gallery/TYBmNSg

But opening a file with mouse double-click or pressing ENTER causes an error (see Image: https://i.postimg.cc/mZp5bsSB/TC-error.png).
Entering the name in TC's command line and pressing ENTER to open it brings the same error (see Image: https://i.postimg.cc/jdWk2F8N/TC-error2.png)
The same for every folder or every file (different extensions) in my WSL.
No matter if run as admin or not.

Using F3 for Lister or F4 for my editor still works!
Richt-click on the file (inside TC) and then selecting the bold file name on top of the context menu still works!

From within the Windows Explorer everything works as normal.
I checked the file permissions, no problems there (did not expect problems here, because I can otherwise work normally).

If I open the Windows CMD (no matter if as admin or not) and enter my wsl file name (\\wsl.localhost\Ubuntu-22.04\...\constants.py) it brings the same error as TC, with a message box saying "Element nicht gefunden." (element not found) and after closing it prints "Access denied". See Image: https://i.postimg.cc/9Fvg7YSk/TC-error-CMD.png
Doing the same with the Windows Powershell works fine!

So, with the CMD behaviour it looks like Windows (or WSL) is the root cause and TC is just suffering... but I wonder, because F3 and F4 are still working when opening the file, if someone has an idea for a workaround? Some setting, so that TC can open the file in a different way?

[TCUserAndFan]

Well, the problem got fixed by running the WSL App again (by typing WSL after pressing Start-button). It does some configuration stuff, which takes around a minute. After rebooting the computer it now works. Opening the file as described from Windows CMD also works..

(I found this solution, because some users had problems with the Linux icon no longer showing up in the Windows Explorer, and they suggested calling the WSL app -- a "problem" I did not recognize as a TC-only user, but I also did not see this symbol in the Windows Explorer, so this problem was also fixed along the way).