-
Notifications
You must be signed in to change notification settings - Fork 852
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
[WSL Error: "Class not registered" (Error Code: Wsl/CallMsi/Install/REGDB_E_CLASSNOTREG)] #12459
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 script will output the path of the log file once done. If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here 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! Closed similar issues:
|
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 script will output the path of the log file once done. If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here 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:
|
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 script will output the path of the log file once done. If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here 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
|
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! |
Title
[WSL Error: "Class not registered" (Error Code: Wsl/CallMsi/Install/REGDB_E_CLASSNOTREG)]
Description
While attempting to install WSL using the
wsl.exe --install
command, the following error message is displayed:This prevents WSL from being installed or used on the system, effectively blocking the ability to run Linux distributions via WSL.
Steps to Reproduce
Example:
PS> wsl.exe --install Class not registered Error code: Wsl/CallMsi/Install/REGDB_E_CLASSNOTREG
Expected Behavior
WSL should install without any errors, enabling the use of Linux distributions on Windows.
Actual Behavior
The installation process fails with the following error:
System Details
Troubleshooting Steps Attempted
regsvr32 MSI.DLL
Logs and Debugging Information
The logs from the diagnostic script have been attached to this issue for review.
collect-wsl-logs.ps1
script in an administrative PowerShell prompt:Attached Log File:
WslLogs-2025-01-21_09-31-20.zip
Additional Context
This issue prevents the installation and usage of WSL, effectively blocking access to Linux environments on this system. Any guidance or fixes would be appreciated.
Similar Issues
The text was updated successfully, but these errors were encountered: