-
Notifications
You must be signed in to change notification settings - Fork 801
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
Incorrect WSL MSI installation via CMD and Psexec #11432
Comments
Logs are required for review from WSL teamIf this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. How to collect WSL logsDownload and execute collect-wsl-logs.ps1 in an administrative powershell prompt:
The scipt will output the path of the log file once done. Once completed please upload the output files to this Github issue. Click here for more info on logging View similar issuesPlease view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it! Open similar issues:
Closed similar issues:
|
Diagnostic information
|
|
Thank you @OneBlue I tried with the latest version of the MSI, ie 2.2.2.0, I still have the same issue |
Interesting. I'd be interested to look the MSI logs for that. Can you run wsl --uninstall, and then share the msiexec logs of a new installation ? |
After more testing, it seems like the command When I start a new installation by calling install.cmd in the 2nd window opened by PsExec, the MSI is correctly installed because I can successfully run the command However, the command Concerning my first tests and the error, it seems like I had to install the MSI twice only because I didn't uninstall it correctly at first. I have an another script used for the uninstallation which basically runs the command : Do you recommend using Thanks for your answers and your time |
@soragXYZ: There is unfortunately a delay for the WSL installation to complete even after msiexec returns successfully. This issue is fixed in insider builds, but it's not fixed on older builds yet. This is most likely what you're experiencing |
@OneBlue thanks for the answer Do we have a release date planned ? |
Unfortunately not yet. Most likely in the coming months. |
This should be now available on all recent Windows builds. Closing for now. Please reopen if the issue still reproduces with the latest windows builds. |
Windows Version
Microsoft Windows [version 10.0.22631.3296]
WSL Version
2.1.5.0
Are you using WSL 1 or WSL 2?
Kernel Version
Irrelevant
Distro Version
Irrelevant
Other Software
No response
Repro Steps
Here are the install scripts:
File install.cmd
@call powershell .\installMsiWSL2.ps1
File installMsiWSL.ps1
Expected Behavior
MSI should be installed correctly
The command
wsl --version
should display the installed versionActual Behavior
The MSI is not installed: the command
wsl --version
returns the help instead of the currently installed versionI have to launch the .cmd twice in a row otherwise the MSI is not installed.
For some reason, in the logs it seems like the installation was successfull, no error whatsoever.
But the MSI is clearly not installed
Diagnostic Logs
install.txt
The text was updated successfully, but these errors were encountered: