Error: 0x800703fa - Press any key to continue

[tuannguyenthe]

When I start Bash on Ubuntu, the Bash terminal displayed:
Error: 0x800703fa
Press any key to continue...

My windows build:
Microsoft Windows [Version 10.0.17017.1000]

The only thing i did before the error was running 'jupyter notebook' and playing around with zipline. I did not update conda or apt.

[tuannguyenthe]

I restarted Windows and the problem went away. I have bash prompt now.

Can you still investigate the issue even though it went away?

[tychen5]

With the exactly the same problem on my notebook.
17025.1000

[MrSimsek]

I am also having the exact problem.

Edit: Restart indeed removes the problem. It might be related to Windows uptades.

[YihaoPeng]

I have the same issue on my notebook. I shutdown my Windows and power it again at next morning. And when I running WSL (Ubuntu, Microsoft Store version), it displayed these error messages:

Installing, this may take a few minutes...
Installation Failed!
Error: 0x800703fa
Press any key to continue...

I have to reboot to let it running as normal.

Windows 1803 build 17115.1

[jesperll]

Just had this after updating to 1803 build 17120.1 as well. An extra reboot fixed it

[friedwm]

I have the same issue on 17133.1. Ubuntu installed in Microsoft Store. A reboot does clear the error, but everytime I open a wsl, I need a reboot again. Please fix this issue ASAP !!!

wsl says:

Installing, this may take a few minutes...
Installation Failed!
Error: 0x800703fa
Press any key to continue...

UPDATE:
This error has never happened before, since I fresh Installed 1803 17133.1 recently. The only different thing is I installed gcc build tool chain and nginx.

UPDATE AGAIN:
I find a solution other than a reboot: go to services.msc, make sure service LxssManager is running, if it is running already, restart it，after turn it on I can use wsl immediately.

[Bryce-Dixon]

Same thing as @friedwm. Happened after signing out when a program wouldn't close.

[quic0]

@friedwm's solution resolved the problem for me on build 17133.

Possible cause is that the Startup Type for LxssManager is set to Manual. When attempting to set it to automatic it raises Error 5: Acces Denied.

[bharadwajpro]

@quic0 Open services as administrator and try again.

[quic0]

@bharadwajpro Same error when running services.msc as Administrator.

[bharadwajpro]

@quic0 Instead of setting it to automatic. Just restart the service as Administrator.

[Rockstar04]

I'm running into the same issue. If I wait several minutes after my system boots, ubuntu starts fine.

[ngetchell]

Running as admin gets past this problem.

[jm33-m0]

after version 1803 update, wsl starts throwing 0x800703fa error, rebooting solves the problem, but the error will still pop up on next boot

[panda2134]

@jm33-m0 Same issue after updating to 1803

[WSLUser]

So I finally hit this issue using both debian.exe and executing debian in CMD. WSL.exe reported no distros installed. I didn't reboot but reinstalled Debian from the Microsoft Store and the error went away. Build version 17134.1. I'm hoping that the issue doesn't reoccur but will update tomorrow if it reverts to the error again.

[PetterS]

Just got this after rebooting when trying to launch Ubuntu.

Installing, this may take a few minutes...
Installation Failed!
Error: 0x800703fa
Press any key to continue...

(I have the April update)

EDIT: This error turned up after shutting down the computer and then starting it again (is this hibernation?). I rebooted and now the error is gone (temporarily?).

[benhillis]

Could somebody that is experiencing this issue on 1803 collect logs and attach them here?

https://github.com/Microsoft/WSL/blob/master/CONTRIBUTING.md#8-detailed-logs

[PgAuffret]

Just to say that the same happens to me since the April Update (Microsoft Windows Version 1803 (OS Build 17134.1)). I am using wsl.exe with hyper.js.
Restarting LxssManager as @friedwm wrote works as temporary fix.

[WSLUser]

So I had the same issue again after rebooting and restarting the LXSS service did resolve the issue.

[benhillis]

Could somebody experiencing this issue please collect and share logs so I can see what's going on?
https://github.com/Microsoft/WSL/blob/master/CONTRIBUTING.md#8-detailed-logs

[danwhitston]

Same issue after applying Spring Update. LXSS service was not started for some reason. Turning it on appears to have resolved the issue.

[hwo411]

Starting/Stopping didn't fix the error for me immediately.

While running `wslconfig /list' it doesn't show any installation and after a few minutes it starts and everything works.

[diablodale]

@benhillis attached are the detailed log files you requested.
0x800703fa_error.zip

Repro

1. Launch Ubuntu

Result

Installing, this may take a few minutes...
Installation Failed!
Error: 0x800703fa
Press any key to continue...

[derekyu56]

Just did an update (KB4103721) and the problem is gone. The service LXSS is configured as Manual. Starting Ubuntu will start the service automatically.

[mloskot]

@Rockstar04 in #2576 (comment)

If I wait several minutes after my system boots, ubuntu starts fine.

I can confirm this behaviour. Despite the LxssManager service Startup Type is Manual, if I wait 3-5 minutes after booting the system, all WSL-s work: Ubuntu, Debian, Kali, even the Ubuntu 18.04.

@derekyu56 in #2576 (comment)

Just did an update (KB4103721) and the problem is gone.

I have the KB4103721 installed - I'm at Windows Version 1803 (OS Build 17134.48) - and I still observe the problem, so the KB4103721 doesn't seem to deploy any fix for it.

[steevsachs]

I have this same issue, and can also confirm that KB4103721 did not resolve the problem. Starting the LxssManager service or restarting resolves the issue.

Potentially notable: I had been experiencing the issue on about 50% of boots prior to KB4103721 and then did not experience the issue until several days after KB4103721. Could be a coincidence.

[benhillis]

@diablodale - Thanks for providing the traces. As I suspected we're getting a REG_KEY_DELETED error when trying to enumerate which distribuitons are installed. What's mysterious is that the parent key we are querying is never deleted by our service, so I suspect something fishy is going on with some other component or perhaps even the registry.

@steevsachs - Interesting. Let me know if you encounter this again with the update installed. Our service is simply enumerating subkeys to determine which distributions are installed, the key in question is never deleted by us so the error is mysterious. Seems like there may be some registry-related issue in that update that was fixed.

@mloskot - Just saw your comment. Something funny is still going on. Do you happen to see any strange errors in the Windows event log around the time distros are failing to launch? Sysinternals procmon may also help narrow this down.

[steevsachs]

Thanks for the response @benhillis. To clarify, I have encountered the issue since KB4103721. What was notable is that, whereas before KB4103721 the issue was occurring every other boot, it seems to occur with significantly lower frequency after KB4103721.

Again, this could absolutely be coincidence. I haven't been able to identify any other correlation, but happy to try things out if it'll help in the diagnosis effort.

[vctls]

Sorry for adding yet another comment on an already crowded issue.
I had the same issue with a manually installed Debian.
I solved it by first unregistering it with wslconfig then reinstalling it by running the exe.

wslconfig /u Debian
# unregistering stuff...
debian.exe

[mloskot]

#2576 (comment)

@mloskot - Do you happen to see any strange errors in the Windows event log
around the time distros are failing to launch?

I don't see any events logged around the time I launch any of WSL distro (ie. START > Ubuntu etc.), but I see lots of logs like this one around the time of OS booting:

Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards. No user action is required.  

 DETAIL - 
 7 user registry handles leaked from \Registry\User\S-1-5-21-1454471165-1326574676-682003330-10609_Classes:
Process 9768 (\Device\HarddiskVolume4\Windows\System32\lxss\wslhost.exe) has opened key \REGISTRY\USER\S-1-5-21-1454471165-1326574676-682003330-10609_Classes
Process 9768 (\Device\HarddiskVolume4\Windows\System32\lxss\wslhost.exe) has opened key \REGISTRY\USER\S-1-5-21-1454471165-1326574676-682003330-10609_Classes
Process 9768 (\Device\HarddiskVolume4\Windows\System32\lxss\wslhost.exe) has opened key \REGISTRY\USER\S-1-5-21-1454471165-1326574676-682003330-10609_Classes
Process 3860 (\Device\HarddiskVolume4\Windows\System32\conhost.exe) has opened key \REGISTRY\USER\S-1-5-21-1454471165-1326574676-682003330-10609_Classes\Local Settings
Process 9768 (\Device\HarddiskVolume4\Windows\System32\lxss\wslhost.exe) has opened key \REGISTRY\USER\S-1-5-21-1454471165-1326574676-682003330-10609_Classes\Local Settings
Process 3860 (\Device\HarddiskVolume4\Windows\System32\conhost.exe) has opened key \REGISTRY\USER\S-1-5-21-1454471165-1326574676-682003330-10609_Classes\Local Settings\Software\Microsoft
Process 9768 (\Device\HarddiskVolume4\Windows\System32\lxss\wslhost.exe) has opened key \REGISTRY\USER\S-1-5-21-1454471165-1326574676-682003330-10609_Classes\Local Settings\Software\Microsoft

By the way, I had not seen the WslRegisterDistribution failed with error: 0x800703fa for quite a while until recently, after I set up Task Scheduler to launch Ubuntu's SSH service at startup using the following action:

C:\Windows\System32\bash.exe -c "sudo /usr/sbin/service ssh --full-restart"

Now I'm seeing the error after every reboot when I launch Ubuntu console.
Perhaps that is somewhat related.

[agustinbreit]

I Had the same problem, just restart LxssManager by following this tips:
1- Run CMD as administrator and restart the LxssManager status

2- Stop it by :
sc stop LxssManager

3- Then restart it by:
sc start LxssManager

that worked for me! thanks

[xtoolkit]

@agustinbreit
fixed in1809!

[seahorseman]

I Had the same problem, just restart LxssManager by following this tips:
1- Run CMD as administrator and restart the LxssManager status
2- Stop it by :
sc stop LxssManager
3- Then restart it by:
sc start LxssManager

that worked for me! thanks

Fixed! You may see access denied, just run CMD as administrator will make it work.

Thank you!

[djensen47]

I'm experiencing this in 18272 and a reboot does NOT fix it. Restarting the LxssManager does not fix it.

[Brian-Perkins]

@djensen47 unfortunately WSL is not functional in 18272 -- see #3645. There is a fix ready for the next Insider Build and you can also rollback to restore functionality.

[djensen47]

Thanks for the update. I went ahead an rolled back. It was a lot less painful than the last time I had to rollback so that's a plus!

[lesliepoolman]

This worked for me in OS build 17134.407
Thanks!

I Had the same problem, just restart LxssManager by following this tips:
1- Run CMD as administrator and restart the LxssManager status

2- Stop it by :
sc stop LxssManager

3- Then restart it by:
sc start LxssManager

[mloskot]

Windows 10 Version 1803 (OS Build 17134.441)

Follow up to my #2576 (comment)

Something happened again, after update to Windows 10 Version 1803 (OS Build 17134.441), LxssManager startup type has got set to Manual and, despite being fully privileged Administrator, I can not re-set it to Automatic:

It happens on two up-to-date Windows 10 installations.

Windows 10 Version 1809 (OS Build 17763.194)

Today, one of my Windows 10 installations has got updatd to this version, after multiple restarts the system was ready. And, I can start WSL (e.g. Ubuntu 18.04) without any errors and without any need to restart the LxssManager service. My task to start WSL SSH at Windows startup (#2576 (comment)) runs successfully now.

[sdjulio]

Windows 10.0.17134, Build 17134 (Pro)
Same behavior but addressed issue with Regedit. Services.msc app would not let me change the startup type. Instead, changed it using Regedit.exe as Admin.

Path to registry key: Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LxssManager\Start
Set value to 2 (Automatic)

[chiro-hiro]

I've the same issue, It will be gone if i'm restart LxssManager.

[lucastakejame]

I also failed to set LxssManager service startup to automatic via services.msc (even with admin)
BUT, I managed to set to automatic with the following command on a cmd (as admin):

sc config LxssManager start=auto

now its set to automatic. Hope it helps =)!

[dpingk]

I have the same issue on 17133.1. Ubuntu installed in Microsoft Store. A reboot does clear the error, but everytime I open a wsl, I need a reboot again. Please fix this issue ASAP !!!

wsl says:

Installing, this may take a few minutes...
Installation Failed!
Error: 0x800703fa
Press any key to continue...

UPDATE:
This error has never happened before, since I fresh Installed 1803 17133.1 recently. The only different thing is I installed gcc build tool chain and nginx.

UPDATE AGAIN:
I find a solution other than a reboot: go to services.msc, make sure service LxssManager is running, if it is running already, restart it，after turn it on I can use wsl immediately.

This helped.
I found similar problem after updating Windows BIOS firmware.

[sanjanareddy5502]

after getting a message press any key, its closing by itself

[sanjanareddy5502]

Installing, this may take a few minutes...
WslRegisterDistribution failed with error: 0x80370102
Please enable the Virtual Machine Platform Windows feature and ensure virtualization is enabled in the BIOS.
For information please visit https://aka.ms/enablevirtualization

[Avliis]

Hello guys! I hope you did well!

WHAT WORK FOR ME:

1- Check the linux subsystem for windows is on, then restart!
2 - Be sure that the Lxxs Manager is auto and on COMMAND: sc config LxssManager start=auto, then restart!
3 - Install the update wsl
wsl.2.3.24.0.x64.msi

And you should be good!

Thank you all!