WSL2 Fails to Run with error code: Wsl/CallMsi/Install/REGDB_E_CLASSNOTREG

[bigcat26]

I'm having issues with running WSL2 on my system.

At first, when trying to run WSL2, I received the error Error code: Wsl/CallMsi/Install/ERROR_INSTALL_FAILURE.
I followed the solution provided in [this link](#11697 (comment) - 2168104220), which involved renaming a registry key. After that, when I tried to run it again, I got a new error: Error code: Wsl/CallMsi/Install/REGDB_E_CLASSNOTREG.

If I directly run the release - downloaded installation package, during the installation process, when it reaches about halfway, a prompt box pops up, saying: "An error occurred while attempting to create the directory: C:\ProgramData\Microsoft\Windows\Start Menu".

I also tried removing WSL from "Turn Windows features on or off", restarting my computer, and then adding it back. However, I still get the "REGDB_E_CLASSNOTREG" error.

I'm not sure what else I can do to get WSL2 to run properly. Any help or suggestions would be greatly appreciated.

WslLogs-2024-10-06_11-27-43.zip

[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-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
If you choose to email these logs instead of attaching to the bug, please send them to wsl-gh-logs@microsoft.com with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

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!

Closed similar issues:

• Error code: Wsl/CallMsi/REGDB_E_CLASSNOTREG (#11497), similarity score: 0.76
• Class not registered Error code: Wsl/CallMsi/REGDB_E_CLASSNOTREG (#11999), similarity score: 0.74
• Error code: Wsl/Service/CreateVm/ERROR_PATH_NOT_FOUND (#10170), similarity score: 0.74
• Unregistered class Error code: Wsl/CallMsi/REGDB_E_CLASSNOTREG (#11641), similarity score: 0.74
• Error code: Wsl/CallMsi/REGDB_E_CLASSNOTREG (#10882), similarity score: 0.74

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

[github-actions]

Diagnostic information

Issue was edited and new log file was found: https://github.com/user-attachments/files/17268046/WslLogs-2024-10-06_11-27-43.zip
Detected appx version: 2.3.24.0
Detected user visible error: Wsl/CallMsi/Install/REGDB_E_CLASSNOTREG

[github-actions]

Diagnostic information

Issue was edited and new log file was found: https://github.com/user-attachments/files/17268046/WslLogs-2024-10-06_11-27-43.zip
Detected appx version: 2.3.24.0
Detected user visible error: Wsl/CallMsi/Install/REGDB_E_CLASSNOTREG

[bigcat26]

solved after I assigned full control access to the SYSTEM account to the Start Menu folder and then re-install wsl2.