Installing, this may take a few minutes…WslRegisterDistribution failed with error: 0x800700b7/0x80080005The distribution installation has become corrupted.Please select Reset from App Settings or uninstall and reinstall the app.Error: 0x800700b7 Cannot create a file when that file already exists.Press any key to continue…
WslRegisterDistribution failed with error 0x800700b7 or 0x80080005
The resolution is fairly simple, and it involves restarting the LxssManager available and other services in Windows. WSL contains two modes—User Mode and Kernel Mode, including Bash, LxssManager, Lxss.sys, and lxcore.sys. LxssManager is a user-mode session manager service that launches a new instance of WSL. Here is what the description says:
Restart LxssManager Service
Press the Windows key, and type cmd until the Command Prompt appears in the list. Right-click on it, and choose to Run as administrator. Then type the following command. Once done, launch WSL, and it should not give you any problem. However, this may happen every time you restart the computer. To make sure it doesn’t happen every time, execute the following command. Next time, when you start the computer and launch WSL, it should not be an issue.
Set LxssManager Auto-Start using Registry
In case you are not able to change the service startup typing using the above-mentioned command, you can change it through the registry. The error occurs if the service is already in use and you were trying to change it.
Open Run prompt, and type regedit, and press the Enter keyIn the Registry Editor, navigate to the following path.
Double-click on the Start key to open in edit mode. Set the value as 2, and save it.
This will make sure the LxssManager is set to automatic. I hope the post was easy to follow, and you were able to resolve the WslRegisterDistribution failed error 0x80080005 or 0x800700b7 using this tip. The error is simple to resolve, and as long as you can set the service to launch automatically, you should be able to fix it. Similar WslRegisterDistribution failed with errors: 0xc03a001a | 0x80041002 | 0x80070422 | 0x80370114 | 0x80370102 | 0x80070003 | 0x80070032 | 0x8007023e | 0x800701bc | 0x8007019e and 0x8000000d.
