WSL: Bash install hangs at "Extracting Filesystem"
It’s been sitting on this for over 30 minutes

It sat there for a few hours the other day, and via this post I restarted and ran lxrun /uninstall /full before running bash again, which has repeated.
About this issue
- Original URL
- State: closed
- Created 10 years ago
- Reactions: 2
- Comments: 68 (11 by maintainers)
I ran into this same problem today (build 14366) and after waiting 30 minutes I pressed
ENTERin desperation. 😄 That immediately caused what appeared to unflushed output to print and everything was installed successfully.I had this issue today. it appears apt is trying to get updated in the background and as I am behind corporate proxy, it is unable to do so. Ideally it should timeout but here the deployment process keeps on wafting. Killed apt in task manager and it got to create default username task immediately
After much effort I was able to debug this. We have a bug in our driver if you have more than 2 NT pagefiles on your system. Any of you that are experiencing this issue could you please try disabling all but one of your pagefiles and trying to launch bash?
See #358 and #538 for more info.
This worked for me.
the bash came out of the hung state saying unix user <xyz> found.
Are you running Avast? I had the same problem, uninstalled Avast (disabling wont work) and now everything works perfectly.
How do I check if I have two or more pagefiles and how do I disable them UPDATE: So I checked , I had only 1 pagefile but had avast installed. I uninstalled it. Now, it runs perfectly
I also met the same issue. I’m using Symantec Endpoint Protection. The SEP blocks the connection to ubuntu server. What I did now is add a Firewall rule and allow traffic to the ip address: 91.189.88.162,91.189.88.149,91.189.88.152,91.189.88.149 These correspond to two server: archive.ubuntu.com and security.ubuntu.com. Hope it helps
Hi,
I am getting the same problem. Is there a fix for this yet? Is this just a pagefile.sys - is it? And are there instructions as to what exactly should be done with this file?
Microsoft has been talking about this feature for several months. Is there a release date yet?
Thanks.
Cheers,
Rich
It does seem like an IPv6 issue; I tried using
apt-getwithin Bash and it just hangs when trying to connect. I guess Comcast (or my router) isn’t very IPv6 friendly. I’ll try it on my work laptop when I get a chance - All of our internal systems and dev servers are IPv6-only so I suspect it’ll work fine there.If the installation really needs to install some packages, can you modify the installer to display the installation progress rather than having no output?
Sent from my phone.
On Aug 8, 2016 8:32 AM, “Ben Hillis” notifications@github.com wrote:
@Daniel15 https://github.com/Daniel15 as @aseering https://github.com/aseering menitone,d do you happen to have a third party firewall installed? We’ve seen lots of issues with them (Avast, Bitdefender, Kaspersky) blocking internet access to Linux processes in WSL.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Microsoft/BashOnWindows/issues/565#issuecomment-238274834, or mute the thread https://github.com/notifications/unsubscribe-auth/AAFnHbwhJajJnTdef7vhUscwD3fVpQVxks5qd0wFgaJpZM4I8LBd .
Interesting – I’m surprised that the installation is doing any
apt install’s. Would it be possible for packages to be rolled into the initial filesystem download?It looks to me like it’s not actually stuck installing `language-pack-en; it looks like it’s stuck downloading it.
@Daniel15 – is it possible that apt might have trouble connecting to the Internet in your environment? Note that apt is pretty aggressive about using IPv6 if it’s available (the official mirrors support IPv6 and IIRC apt defaults to using it if it appears to be available); that can cause problems in some environments.
I’m encountering this too. It seems like it’s stuck on installing
language-pack-en, @benhillis’ command shows:I ran
bash.exe -c "kill 34"to kill the process, which seems to have “fixed” it. Not sure if I broke anything by doing that, though 😛I confirm this issue installing Bash on build 14388, and disabling all pagefiles but one, fixed the problem.