RemoteApp window being spawned and hanging, unable to launch windows binaries from within WSL

[ElanHasson]

Environment

Windows build number: Microsoft Windows [Version 10.0.22000.434]
Your Distribution version: Ubuntu Release:        20.04
Your WSLg version: 1.0.25

WSLg ( x86_64 ): 1.0.30+Branch.main.Sha.18884f996f5e851af4842010b434db17d3caa7aa
Mariner: VERSION="1.0.20210224"
FreeRDP: 81cfc08b9c745c941be23bd8dd43b9ffeb5b6991
weston: 6a3f1f669f6e53c0db3057d4f62da3a473c07c71
pulseaudio: 2f0f0b8c3872780f15e275fc12899f4564f01bd5
mesa:

Steps to reproduce

Unknown, happened randomly.

WSL logs:

• Attach WSLg logs from /mnt/wslg
  stderr.log.gz
  pulseaudio.log
  versions.txt
  weston.log

Expected behavior

Should not have a visible RDP Window that does nothing but fail to connect.
Also, unable to launch Windows binaries from bash.

Actual behavior

msrdc.exe is running with the following command line args:

CommandLine=msrdc.exe /v:9D2CC20B-F0CA-4044-8191-6928394D97EC /hvsocketserviceid:14043FFB-FACB-11E6-BD58-64006A7986D3 /silent /wslg /plugin:WSLDVC_PACKAGE /wslgsharedmemorypath:WSL\9D2CC20B-F0CA-4044-8191-6928394D97EC\wslg "C:\Program Files\WindowsApps\MicrosoftCorporationII.WindowsSubsystemforLinux_0.51.2.0_x64__8wekyb3d8bbwe\wslg.rdp"


CommandLine=msrdc.exe /v:9D2CC20B-F0CA-4044-8191-6928394D97EC /hvsocketserviceid:14043FF1-FACB-11E6-BD58-64006A7986D3 /silent /wslg /plugin:WSLDVC_PACKAGE /wslgsharedmemorypath:WSL\9D2CC20B-F0CA-4044-8191-6928394D97EC\wslg "C:\Program Files\WindowsApps\MicrosoftCorporationII.WindowsSubsystemforLinux_0.51.2.0_x64__8wekyb3d8bbwe\wslg.rdp"


CommandLine=msrdc.exe /v:9D2CC20B-F0CA-4044-8191-6928394D97EC /hvsocketserviceid:14044005-FACB-11E6-BD58-64006A7986D3 /silent /wslg /plugin:WSLDVC_PACKAGE /wslgsharedmemorypath:WSL\9D2CC20B-F0CA-4044-8191-6928394D97EC\wslg "C:\Program Files\WindowsApps\MicrosoftCorporationII.WindowsSubsystemforLinux_0.51.2.0_x64__8wekyb3d8bbwe\wslg.rdp"

Another thing I noticed is I used to be able to run notepad.exe / code.exe:

$ notepad.exe stderr.log
bash: /mnt/c/WINDOWS/system32/notepad.exe: cannot execute binary file: Exec format error

$ code stderr.log 
/mnt/c/Users/Elan Hasson/AppData/Local/Programs/Microsoft VS Code/bin/code: 61: /mnt/c/Users/Elan Hasson/AppData/Local/Programs/Microsoft VS Code/Code.exe: Exec format error

core dumps from /mnt/wslg/dumps:
core.zip

[hideyukn88]

@ElanHasson, thanks for reporting the issue, do you see any core dump is created under /mnt/wslg/dumps? if so, please share with us. I do see, from log, msrdc.exe has been restarted repeatedly, and came to connect to weston, but it looks weston has terminated/restarted. Restarting weston causes disconnection in RDP, then WSLGd will respawn both weston and msrdc.exe again. If there is any dump created, that might help to understand why weston has been terminated. Thanks!

[ElanHasson]

@hideyukn88 Updated above!

But it seems it is from today?

[scarolan]

This just started for me today, I'm not sure why. I thought I had a virus at first. What are these and why are they spawning every time I open wsl???

[hideyukn88]

@scarolan, does the dialog box disappear once you started any Linux GUI application? thanks!

[hideyukn88]

@ElanHasson, sorry for late response, the issue causing the weston crash should be fixed in recent WSL release, but still not sure why you saw the connecting status window. Do you still the window after upgrading WSL to the recent version? thanks!

[ElanHasson]

If memory serves I got it maybe once a month or so ago.

I'm up to date on everything and haven't seen it since so I would say whatever is causing it has been resolved.

[ElanHasson]

@hideyukn88 I would say close the issue and I'll re-open if it occurs again.

[ElanHasson]

So to necromance this... same issue different look. Press OK and it happens again.

@hideyukn88, new issue?

Platform ServicePack Version VersionString

---

Win32NT 10.0.22621.0 Microsoft Windows NT 10.0.22621.0

Ubuntu 22.04

NO DUMPS EXISTED
weston.log
wlog.log
pulseaudio.log
stderr.log
versions.txt

[hideyukn88]

@ElanHasson, if you press 'OK' on that dialog, does same dialog reappear again? and would you please share a few *.etl files in %TEMP%\DiagOutputDir\RdClientAutoTrace which has timestamp close to the time when this issue occurred, thanks!

[Thealf154]

I have a similar error with the same error screen, and apps like VS Code WSL won't even open my projects from the command line. I fixed by removing all the WSL components from Apps and Feautures.

Edit: I found after running: wsl --update the error appears again

[ElanHasson]

@hideyukn88 sorry for delays.pressing OK results in same dialog.

Did a wsl terminate and it went away.

Next time it happens I'll capture traces.