Error Code 2503/2502

[adrienx33]

Windows Version

Microsoft Windows [Version 10.0.19045.6466]

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

I cannot run any installer at all without getting either environmental variable errors or 2503 or 2502 errors i ve tried every troubleshooting guide i can find and still nothing

Repro Steps

im not sure what i did

Expected Behavior

I was expecting any installer to actually work

Actual Behavior

I also cannot open task manager at all

PS C:\Windows\system32> wsl --install
The system cannot find the path specified.
PS C:\Windows\system32>

https://cdn.discordapp.com/attachments/1382152542091477035/1490159327770574899/image.png?ex=69d30a85&is=69d1b905&hm=f5caf71306dcba4912996beda83547bc77f50bc862b9a77940c37d7a0651cb49&

Diagnostic Logs

No response

[github-actions]

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-wsl-logs.ps1 -LogProfile networking instead, following the instructions in Collect WSL logs for networking issues

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

See Collect WSL logs (recommended method).

If you choose to email these logs instead of attaching them to the bug, please send them to wsl-gh-logs@microsoft.com with the GitHub issue number in the subject, and include a link to your GitHub issue comment in the message body, and reply with '/emailed-logs'.