search

microsoft / WSL

Issues found on WSL
https://docs.microsoft.com/windows/wsl
MIT License
17.32k stars 814 forks source link

WSL1 Cannot start any Windows applications anymore #6988

Closed xploSEoF closed 8 months ago

xploSEoF commented 3 years ago

Windows Build Number

Version 10.0.19042 Build 19042

WSL Version

Kernel Version

Linux version 4.4.0-19041-Microsoft (Microsoft@Microsoft.com) (gcc version 5.4.0 (GCC) ) #488-Microsoft Mon Sep 01 13:43:00 PST 2020

Distro Version

Ubuntu 20.04

Other Software

Things like Windows Explorer (standard, see windows build number) and VS Code (v1.56.2)

Repro Steps

From the WSL terminal, run explorer.exe

Expected Behavior

An explorer window should open

Actual Behavior

-bash: /mnt/c/Windows/explorer.exe: cannot execute binary file: Exec format error

Diagnostic Logs

No response

xploSEoF commented 3 years ago

Equally, running code . (which triggers VS Code to run with the current directory) errors in the same way: /mnt/c/Users/Liam/AppData/Local/Programs/Microsoft VS Code/bin/code: 61: /mnt/c/Users/Liam/AppData/Local/Programs/Microsoft VS Code/Code.exe: Exec format error

benhillis commented 3 years ago

Something specific to your environment it seems, do you have any more details that can help us diagnose?

xploSEoF commented 3 years ago

Not too sure what further information I could provide.

Everything worked a month ago, then I applied a few updates on Windows, and now I can't invoke any Windows application from within WSL1.

xploSEoF commented 2 years ago

I've just exported my WSL installation and imported it onto a new machine, and I'm still having the same issue. Perhaps there's something in the WSL instance that needs changing to be able to invoke windows applications? It's either that, or it is an issue with WSL1 and the rest of Windows since the update earlier this year.

jhwblender commented 1 year ago

Personally getting this issue myself with WSL2 after recompiling the Kernel to include some CAN bus features.

xploSEoF commented 1 year ago

@jhwblender I suspect the two are different issues. WSL2 most likely has an altered kernal to handle windows specific things, and your recompile doesn't include the alterations necessary.

My understanding is that one of the Windows updates I received changed the way the Windows side handled the request, requiring a change to WSL instances, but these changes weren't passed on to those in legacy WSL1. Unfortunately, with no easy migration from WSL1 legacy to the newer WSL1 instances and my bug report having been abandoned and forgotten (I'm surprised it hasn't been closed) I have to put up with this issue until I find the time to go through the lengthy process of starting from scratch.

microsoft-github-policy-service[bot] commented 8 months ago

This issue has been automatically closed since it has not had any activity for the past year. If you're still experiencing this issue please re-file this as a new issue or feature request.

Thank you!