-
Notifications
You must be signed in to change notification settings - Fork 802
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
Error code: Wsl/CallMsi/REGDB_E_CLASSNOTREG #11497
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:
|
The log file doesn't contain any WSL traces. Please make sure that you reproduced the issue while the log collection was running. Diagnostic information
|
Get-WindowsOptionalFeature: C:\dev\collect-wsl-logs.ps1:56
Line |
56 | Get-WindowsOptionalFeature -Online > $folder/optional-components.txt
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| Klasa niezarejestrowana.
Log collection is running. Please reproduce the problem and once done press any key to save the logs.
Saving logs...
100% [>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>]
Logs saved in: C:\dev\WslLogs-2024-04-22_21-47-38.zip. Please attach that file to the GitHub issue. |
@malezjaa: Did you reproduce the issue while log collection was running ? There's no WSL traces in the logs. /logs |
I reproduced this error, I ran collection log again. |
Diagnostic information
|
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?
Diagnostic information
|
Thank you! It works |
I have the same problem, I tried running the command and got the following error: .\install-latest-wsl.ps1
You cannot call a method on a null expression.
No C:\Users\icaro\install-latest-wsl.ps1:10 caractere:5
+ if ($systeminfo.contains('x64'))
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (:) [], ParentContainsErrorRecordException
+ FullyQualifiedErrorId : InvokeMethodOnNull |
Windows Version
Microsoft Windows [Version 10.0.22631.3447]
WSL Version
Doesn't work
Are you using WSL 1 or WSL 2?
Kernel Version
No response
Distro Version
No response
Other Software
No response
Repro Steps
When I try to install wsl command with
wsl --install
I get this error:Error code: Wsl/CallMsi/REGDB_E_CLASSNOTREG
Same with any other command
Expected Behavior
To install wsl
Actual Behavior
Error
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: