Closed ccovey closed 2 hours ago
Your WSL installation appears to be in a bad state. Can you try running the following command to reinstall WSL (elevated powershell) and see if that solves the issue?
Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/triage/install-latest-wsl.ps1" -OutFile install-latest-wsl.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\install-latest-wsl.ps1
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!
Note: You can give me feedback by thumbs upping or thumbs downing this comment.
Detected appx version: 2.0.14.0
Detected user visible error: Wsl/CallMsi/REGDB_E_CLASSNOTREG
The bots suggestion worked. If that was in docs or somewhere I should've noticed, sorry :)
Windows Version
Microsoft Windows [Version 10.0.22631.4391]
WSL Version
0.0.0.0
Are you using WSL 1 or WSL 2?
Kernel Version
No response
Distro Version
No response
Other Software
No response
Repro Steps
run wsl.exe --install
Expected Behavior
WSL2 installs successfully.
Actual Behavior
Class not registered Error code: Wsl/CallMsi/REGDB_E_CLASSNOTREG
Diagnostic Logs
WslLogs-2024-11-15_12-33-03.zip