Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot execute MSI files stored on WSL filesystem #12657

Closed
1 of 2 tasks
printfn opened this issue Mar 5, 2025 · 4 comments
Closed
1 of 2 tasks

Cannot execute MSI files stored on WSL filesystem #12657

printfn opened this issue Mar 5, 2025 · 4 comments
Labels
emailed-logs Logs have been emailed

Comments

@printfn
Copy link

printfn commented Mar 5, 2025

Windows Version

Microsoft Windows [Version 10.0.26100.3323]

WSL Version

2.4.10.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

Linux version 5.15.167.4-microsoft-standard-WSL2 (root@f9c826d3017f) (gcc (GCC) 11.2.0, GNU ld (GNU Binutils) 2.37) #1 SMP Tue Nov 5 00:21:55 UTC 2024

Distro Version

Ubuntu 24.04

Other Software

No response

Repro Steps

  1. Download an MSI (e.g. the Firefox installer MSI from https://www.mozilla.org/en-US/firefox/all/desktop-release/win64-msi/en-US/) and store it in the WSL filesystem
  2. In Windows Explorer, navigate to \\wsl.localhost\Ubuntu-24.04\path\to\msi and double-click the MSI

Expected Behavior

The MSI should open as expected

Actual Behavior

It fails with the error message "This package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package"

Diagnostic Logs

No response

Copy link

github-actions bot commented Mar 5, 2025

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

@printfn
Copy link
Author

printfn commented Mar 5, 2025

/emailed-logs

Copy link

github-actions bot commented Mar 5, 2025

Diagnostic information
Found '/emailed-logs', adding tag 'emailed-logs'

@github-actions github-actions bot added the emailed-logs Logs have been emailed label Mar 5, 2025
@OneBlue
Copy link
Collaborator

OneBlue commented Mar 6, 2025

Thank you for reporting this @printfn. Unfortunately this is a limitation from MSI which doesn't support running from a \wsl.localhost path.

Closing since this can't be fixed from the WSL side

@OneBlue OneBlue closed this as completed Mar 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
emailed-logs Logs have been emailed
Projects
None yet
Development

No branches or pull requests

2 participants