All wsl commands return Wsl/CallMsi/Install/E_INVALIDARG

[kvpbldsck]

Windows Version

Microsoft Windows [Version 10.0.22631.4112]

WSL Version

0.0.0.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

No response

Distro Version

No response

Other Software

No response

Repro Steps

1. Run wsl --install --web-download
2. Restart pc
3. Run wsl -v

This command, as far as any other, return:

parameter is incorrect.
Error code: Wsl/CallMsi/Install/E_INVALIDARG

Disabling/enabling wsl feature haven't helped

Maybe helpful information: before this problem I was trying to install Docker Desktop (4.34.0) and installation process stuck at the deploying components: install docker cli plugins stage

Expected Behavior

wsl commands work fine

Actual Behavior

wsl commands fail with message:

The parameter is incorrect.
Error code: Wsl/CallMsi/Install/E_INVALIDARG

Diagnostic Logs

WslLogs-2024-09-02_23-34-31.zip

[github-actions]

View similar issues

Please 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:

• "The parameter is incorrect" when launching wsl (#8129), similarity score: 0.77

Closed similar issues:

• Error: 0x80070057 The parameter is incorrect (#10287), similarity score: 0.78
• Error code: Wsl/Service/CreateInstance/CreateVm/E_INVALIDARG (#10544), similarity score: 0.77
• wsl install failed with error 0x80240438 (#10226), similarity score: 0.75
• Error code: Wsl/CallMsi/REGDB_E_CLASSNOTREG (#11497), similarity score: 0.75

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

Diagnostic information

Detected appx version: 2.2.4.0
Detected user visible error: Wsl/CallMsi/Install/E_INVALIDARG

[OneBlue]

Thank you @kvpbldsck.

Does manually installing the latest MSI solve the issue ?

[manuth]

@OneBlue I have the very same issue.
I can confirm that this workaround fixes the issue on my machine.

[microsoft-github-policy-service]

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

Thank you!