WSL cannot run EXE files with added options in wslconfig

WSL Cannot Run EXE Files: Added Options and WSLconfig

Windows Subsystem for Linux (WSL) is a compatibility layer for running Linux binary executables (ELF format) natively on Windows 10 and Windows Server 2019. However, running EXE files on WSL can be a challenge. In this article, we will discuss the added options for WSL and the WSLconfig file to help you properly configure your WSL environment to run EXE files.

Understanding WSL and EXE Files

WSL is not designed to run Windows EXE files natively. Instead, it uses a compatibility layer to run Linux ELF format binaries. Therefore, when you try to run an EXE file on WSL, you may encounter errors or unexpected behavior. However, there are some workarounds to run EXE files on WSL, such as using a compatibility layer like Wine or using a Windows emulator like VirtualBox.

Added Options for WSL

When installing WSL, you can add options to the installation command to customize the WSL environment. One such option is the --executemode flag, which allows you to run EXE files on WSL. The --executemode flag accepts two values: guest and host. The guest value runs the EXE file in the WSL environment, while the host value runs the EXE file in the Windows environment.

Here is an example of how to use the --executemode flag when installing WSL:

wsl --install --executemode guest

Configuring WSL with WSLconfig

Once you have installed WSL with the --executemode flag, you can further customize the WSL environment using the WSLconfig file. The WSLconfig file is a JSON file that allows you to configure various settings for your WSL environment, such as the default username, the default shell, and the default working directory.

To configure WSL to run EXE files, you can add the following options to the WSLconfig file:

• metadata: This option allows you to run EXE files on WSL by adding metadata to the EXE file. This metadata tells WSL how to run the EXE file.
• umask: This option sets the file mode creation mask for the WSL environment. The default value is 0022.
• fmask: This option sets the default file permission mask for the WSL environment. The default value is 0111.

Here is an example of how to configure WSL to run EXE files using the WSLconfig file:

{
"default": {
"executemode": "guest",
"metadata": {
"run-exe": "true"
},
"umask": "022",
"fmask": "111"
}
}

Troubleshooting WSL and EXE Files

If you are still having trouble running EXE files on WSL, here are some troubleshooting steps you can take:

• Make sure the EXE file has the execute permission. You can set the execute permission using the chmod command.
• Check the WSL logs for any errors or issues. You can view the WSL logs using the wsl --log command.
• Try running the EXE file using a compatibility layer like Wine or using a Windows emulator like VirtualBox.

In this article, we discussed how to run EXE files on WSL using the added options and the WSLconfig file. By following the steps outlined in this article, you can properly configure your WSL environment to run EXE files. However, keep in mind that WSL is not designed to run Windows EXE files natively, so you may encounter errors or unexpected behavior.

References

• Install Windows Subsystem for Linux on Windows 10
• Troubleshooting Windows Subsystem for Linux
• Wine User's Guide
• VirtualBox Downloads