search

microsoft / WSL

Issues found on WSL
https://docs.microsoft.com/windows/wsl
MIT License
17.39k stars 819 forks source link

Error: 0x800703fa - Press any key to continue #2576

Closed tuannguyenthe closed 6 years ago

tuannguyenthe commented 7 years ago

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] image

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 commented 7 years ago

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 commented 6 years ago

With the exactly the same problem on my notebook. 17025.1000

MrSimsek commented 6 years ago

image

I am also having the exact problem.

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

YihaoPeng commented 6 years ago

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 commented 6 years ago

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

friedwm commented 6 years ago

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.

BtheDestroyer commented 6 years ago

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

quic0 commented 6 years ago

@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 commented 6 years ago

@quic0 Open services as administrator and try again.

quic0 commented 6 years ago

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

bharadwajpro commented 6 years ago

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

Rockstar04 commented 6 years ago

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

ngetchell commented 6 years ago

Running as admin gets past this problem.

jm33-m0 commented 6 years ago

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

panda2134 commented 6 years ago

@jm33-m0 Same issue after updating to 1803

WSLUser commented 6 years ago

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 commented 6 years ago

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 commented 6 years ago

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 commented 6 years ago

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 commented 6 years ago

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

benhillis commented 6 years ago

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 commented 6 years ago

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

hwo411 commented 6 years ago

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 commented 6 years ago

@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 commented 6 years ago

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 commented 6 years ago

@Rockstar04 in https://github.com/Microsoft/WSL/issues/2576#issuecomment-383907890

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 https://github.com/Microsoft/WSL/issues/2576#issuecomment-387569534

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 commented 6 years ago

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 commented 6 years ago

@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 commented 6 years ago

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.

sonnetmia commented 6 years ago

Works after LxssManager restart. open and search this services under services.msc

kyranet commented 6 years ago

In my case, I got this after restarting Windows. I have Ubuntu 18.04.

Installing, this may take a few minutes...
WslRegisterDistribution failed with error: 0x800703fa
Error: 0x800703fa Attempt of illegal operation in a registry key that was marked for elimination.

Press any key to continue...

EDIT: I got it fixed, it was an issue with an environment variable in Hyper, got solved by removing it.

zupalex commented 6 years ago

I'm ecperiencing the same issue with me having to start LxssManager by hand in order for Ubuntu to start without throwing the error. This started to occur after the latest big Windows Update from Monday.

deveth0 commented 6 years ago

zupalex: same here. I also noticed, that the WSL is starting on several boots but sometimes requires a manual restart of the LxssManager (thanks for this idea!!)

seerwright commented 6 years ago

Reboot fixed me a well - that was scary.

mloskot commented 6 years ago

Folks, clearly, the reboot fix works just by a flux. There's high chance it won't work again next time you reboot. It is not a fix. The LxssManager service is simply not starting, or completing startup procedure too late or starting up into an incomplete state.

Instead of spamming the ticket about "reboot fixed", simply up vote previous alike comment.

benc-uk commented 6 years ago

This has started happening since the April 1803 update. I'm not on an insider build, this is main Windows 10 channel. I thought my WSL was totally borked. Restarting LxssManager fixes it but I run a lot of demos and this looks BAD, as in WSL is beta/flaky/not for real use

xtoolkit commented 6 years ago

@kyranet how fix it?

ozen commented 6 years ago

@xtoolkit Please note that kyranet had a different error.

simoncpu commented 6 years ago

I've experienced this error twice now. Restarting LxssManager solves the problem, although I don't know why I need to restart the service in the first place.

jomocag commented 6 years ago

My two cents...

When trying to launch Ubuntu on my system I have seen both errors "Installation failed" and "WslRegisterDistribution failed" since last W10 big update. Since then it has always failed when I tried to launch it just after boot&login, as @mloskot said. Today I just waited some time before trying it again and it has launched normally.

Till now I have been using a little batch file on the desktop in order to restart Lxss service (last sc command is just to confirm it is starting): sc stop LxssManager pause
sc start LxssManager
pause
sc queryex LxssManager
pause

If you want to follow the uninstall/install path (I haven't tested it), look into this post at issue #3054 in order to avoid losing your files & setup.

ghost commented 6 years ago

This issue only seems to happen when you shutdown with Fast startup on. It never occours after restarts, and neither after Shift+shutdown. Disabling Faststartup is for me a better fix.

simoncpu commented 6 years ago

I had my suspicion that something like this was causing the problem (i.e., other services like DNSCrypt have trouble starting on my laptop too), but I didn't know what it's called in Windows. Googling "fast startup" now... thanks for the tip... :)

On Tue, May 29, 2018 at 9:21 PM Ioan Moldovan notifications@github.com wrote:

This issue only seems to happen when you shutdown with Fast startup on. It never occours after restarts, and neither after Shift+shutdown. Disabling Faststartup is for me a better fix.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/Microsoft/WSL/issues/2576#issuecomment-392773380, or mute the thread https://github.com/notifications/unsubscribe-auth/AAH2UZ4Ow1hf73EGqNb_uo4w0Jge0-pXks5t3UtUgaJpZM4P-kqZ .

ghost commented 6 years ago

Yeah if I turn off OpenVPN service and then fast-shutdown, when I turn PC back on, it stays disconnected from VPN.

Fast startup can be disabled in Power Options

On Tue, May 29, 2018, 5:27 PM Simon Cornelius P. Umacob < notifications@github.com> wrote:

I had my suspicion that something like this was causing the problem (i.e., other services like DNSCrypt have trouble starting on my laptop too), but I didn't know what it's called in Windows. Googling "fast startup" now... thanks for the tip... :)

On Tue, May 29, 2018 at 9:21 PM Ioan Moldovan notifications@github.com wrote:

This issue only seems to happen when you shutdown with Fast startup on. It never occours after restarts, and neither after Shift+shutdown. Disabling Faststartup is for me a better fix.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/Microsoft/WSL/issues/2576#issuecomment-392773380, or mute the thread < https://github.com/notifications/unsubscribe-auth/AAH2UZ4Ow1hf73EGqNb_uo4w0Jge0-pXks5t3UtUgaJpZM4P-kqZ

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/Microsoft/WSL/issues/2576#issuecomment-392796635, or mute the thread https://github.com/notifications/unsubscribe-auth/AMfwcCaorB1Sq90fXqao1pBjvwb6eEkSks5t3VrOgaJpZM4P-kqZ .

simoncpu commented 6 years ago

I had the same issue too. I thought it was just normal to manually connect to OpenVPN on boot. Disabling fast startup solved a lot of other issues! Thanks, @ioanmoldovan

benhillis commented 6 years ago

I'll try playing around with fast startup on.

ghost commented 6 years ago

Fast startup is a great idea, but it causes a lot of software/hardware issues. Especially when dual-booting.

On Tue, May 29, 2018, 5:37 PM Simon Cornelius P. Umacob < notifications@github.com> wrote:

I had the same issue too. I thought it was just normal to manually connect to OpenVPN on boot. Disabling fast startup solved a lot of other issues! Thanks, @ioanmoldovan https://github.com/ioanmoldovan

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Microsoft/WSL/issues/2576#issuecomment-392800338, or mute the thread https://github.com/notifications/unsubscribe-auth/AMfwcGM1aFrf-44XHqU0XqXzUY_2qHaFks5t3V0zgaJpZM4P-kqZ .

endiliey commented 6 years ago

Happened to me. Restarted LxssManager and it works fine now

benhillis commented 6 years ago

I've identified the issue and am currently working on a fix.

ghost commented 6 years ago

I’m curious, can you explain what exactly caused the issue?

By the way, why isn’t WSL open source, I mean, it’s nice to have issues page, but please, release the source code!

From: Ben Hillis Sent: Wednesday, May 30, 2018 7:47 PM To: Microsoft/WSL Cc: Ioan Moldovan; Mention Subject: Re: [Microsoft/WSL] Error: 0x800703fa - Press any key to continue(#2576)

I've identified the issue and am currently working on a fix. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

benhillis commented 6 years ago

Essentially the issue is that with fast reboot the LxssManager service is not stopped when the user's session exits and when the machine restarts some registry keys that were opened in the previous session are now invalid.

WSL is part of Windows, and Windows itself is not open source. It would be nice if all or parts of the project could be open sourced but nothing new to report on that front.