New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Install not working after upgrade to 14361 #538

Closed
N00byEdge opened this Issue Jun 15, 2016 · 60 comments

Comments

Projects
None yet
5 participants
@N00byEdge

N00byEdge commented Jun 15, 2016

I went and upgraded to build 14361, now there is a bash process running at 100% CPU usage on one of my cores. I am unable to exit this process using any tools, and it can sit there for hours. It doesn't cause any disk/network activity, only CPU. I get the following error when attempting an uninstall:

C:\Users\N00byEdge>lxrun /uninstall /full /y
This will uninstall Ubuntu on Windows.
This will remove the Ubuntu environment as well as any modifications, new applications, and user data.
Uninstalling...
Error: 0x80080005

The error takes about a minute until it appears. This install was very unstable on the last build, but it was at least working. No modifications made to the install, and Windows is running on a real PC, no VM.

@N00byEdge

This comment has been minimized.

Show comment
Hide comment
@N00byEdge

N00byEdge Jun 15, 2016

I just realized there is a new preview build. I'm installing it as I write this, and will report back if that fixed it. I thought I'd keep the issue open, as I haven't seen this reported before.

N00byEdge commented Jun 15, 2016

I just realized there is a new preview build. I'm installing it as I write this, and will report back if that fixed it. I thought I'd keep the issue open, as I haven't seen this reported before.

@benhillis

This comment has been minimized.

Show comment
Hide comment
@benhillis

benhillis Jun 16, 2016

Member

Thanks for reporting this, I'll be curious to see if this issue goes away when you upgrade.

Member

benhillis commented Jun 16, 2016

Thanks for reporting this, I'll be curious to see if this issue goes away when you upgrade.

@N00byEdge

This comment has been minimized.

Show comment
Hide comment
@N00byEdge

N00byEdge Jun 16, 2016

The issue persists. The only difference it that I can no longer ctrl+c a cmd trying to start Bash. What error info do you want me to collect?

N00byEdge commented Jun 16, 2016

The issue persists. The only difference it that I can no longer ctrl+c a cmd trying to start Bash. What error info do you want me to collect?

@N00byEdge

This comment has been minimized.

Show comment
Hide comment
@N00byEdge

N00byEdge Jun 16, 2016

I of course tried to uninstall the feature and install it again (and yes, it was uninstalled after the first reboot), but it still wouldn't start. This makes me think that it's the Ubuntu install that is broken.

N00byEdge commented Jun 16, 2016

I of course tried to uninstall the feature and install it again (and yes, it was uninstalled after the first reboot), but it still wouldn't start. This makes me think that it's the Ubuntu install that is broken.

@N00byEdge

This comment has been minimized.

Show comment
Hide comment
@N00byEdge

N00byEdge Jun 16, 2016

Wow, in the latest build the Bash process was not running on startup(which it was on the last build), which enabled me to do the uninstall. The uninstall is still unresponsive after the bash process has been opened.

However, it still seems like the issue is there. Maybe it's hardware related? Screenshot

N00byEdge commented Jun 16, 2016

Wow, in the latest build the Bash process was not running on startup(which it was on the last build), which enabled me to do the uninstall. The uninstall is still unresponsive after the bash process has been opened.

However, it still seems like the issue is there. Maybe it's hardware related? Screenshot

@benhillis

This comment has been minimized.

Show comment
Hide comment
@benhillis

benhillis Jun 16, 2016

Member

Did your install eventually succeed? We do launch some commands as part of post install, I suspect that's what's happening in your screenshot.

There are instructions here how on collecting tracing information. I would suggest uninstalling, rebooting, then starting the trace and running install.

Tracing instructions: #410 (comment)

Member

benhillis commented Jun 16, 2016

Did your install eventually succeed? We do launch some commands as part of post install, I suspect that's what's happening in your screenshot.

There are instructions here how on collecting tracing information. I would suggest uninstalling, rebooting, then starting the trace and running install.

Tracing instructions: #410 (comment)

@N00byEdge

This comment has been minimized.

Show comment
Hide comment
@N00byEdge

N00byEdge Jun 16, 2016

@benhillis I didn't quit the process after taking that screenshot and all, but as I am writing this, the process is still running. I think that we should call a 7 hour wait good enough, right? I'll go ahead and follow those instructions.

N00byEdge commented Jun 16, 2016

@benhillis I didn't quit the process after taking that screenshot and all, but as I am writing this, the process is still running. I think that we should call a 7 hour wait good enough, right? I'll go ahead and follow those instructions.

@N00byEdge

This comment has been minimized.

Show comment
Hide comment
@N00byEdge

N00byEdge Jun 17, 2016

Is there an update to this issue? The files that were collected were very small, and I do not know if it was even able to start. Anyways, at that state it just sits there and babysits one of my cores at all times. It has started running at startup again. If you want to look at this through TeamViewer or something, I could possibly arrange that.

N00byEdge commented Jun 17, 2016

Is there an update to this issue? The files that were collected were very small, and I do not know if it was even able to start. Anyways, at that state it just sits there and babysits one of my cores at all times. It has started running at startup again. If you want to look at this through TeamViewer or something, I could possibly arrange that.

@benhillis

This comment has been minimized.

Show comment
Hide comment
@benhillis

benhillis Jun 17, 2016

Member

I got your traces but, as you mention, they are quite small and there aren't any useful breadcrumbs in them. Above you mention reinstalling the feature, did you do that via the "Turn Windows features on or off" page or by the below commands?

lxrun.exe /uninstall /full
lxrun.exe /install

If you haven't already, I'd suggest this. Reboot, then run the above commands.

Member

benhillis commented Jun 17, 2016

I got your traces but, as you mention, they are quite small and there aren't any useful breadcrumbs in them. Above you mention reinstalling the feature, did you do that via the "Turn Windows features on or off" page or by the below commands?

lxrun.exe /uninstall /full
lxrun.exe /install

If you haven't already, I'd suggest this. Reboot, then run the above commands.

@N00byEdge

This comment has been minimized.

Show comment
Hide comment
@N00byEdge

N00byEdge Jun 18, 2016

@benhillis I reinstalled the feature only when I wrote that and I reran those commands before starting the capture.

N00byEdge commented Jun 18, 2016

@benhillis I reinstalled the feature only when I wrote that and I reran those commands before starting the capture.

@N00byEdge

This comment has been minimized.

Show comment
Hide comment
@N00byEdge

N00byEdge Jun 21, 2016

That means I did that before sending the files.

N00byEdge commented Jun 21, 2016

That means I did that before sending the files.

@N00byEdge

This comment has been minimized.

Show comment
Hide comment
@N00byEdge

N00byEdge Jun 22, 2016

Issue still present on 14367

N00byEdge commented Jun 22, 2016

Issue still present on 14367

@benhillis

This comment has been minimized.

Show comment
Hide comment
@benhillis

benhillis Jun 22, 2016

Member

This sounds very similar to #358. @N00byEdge by chance was this an upgrade from an earlier version of Windows (not an earlier Windows 10 Insider flight, like the release version of Windows 10).

The following information would be useful to help me try to repro this:

  1. Which Windows build number are you running?
  2. What Windows locale is your install?
  3. What is your Windows username?
  4. Any other configuration differences you can think of from a fresh Windows install.
Member

benhillis commented Jun 22, 2016

This sounds very similar to #358. @N00byEdge by chance was this an upgrade from an earlier version of Windows (not an earlier Windows 10 Insider flight, like the release version of Windows 10).

The following information would be useful to help me try to repro this:

  1. Which Windows build number are you running?
  2. What Windows locale is your install?
  3. What is your Windows username?
  4. Any other configuration differences you can think of from a fresh Windows install.
@N00byEdge

This comment has been minimized.

Show comment
Hide comment
@N00byEdge

N00byEdge Jun 22, 2016

  1. Build 14367
  2. 1033 en-US English (United States)
  3. Orion\N00byEdge, local user. Computer is on a domain. Computer name is Orion.
  4. Upgraded from W7 -> W10 Release -> W10 IP

Computer joined domain after W7 upgrade, I'm pretty sure. May or may not have been before going IP.

N00byEdge commented Jun 22, 2016

  1. Build 14367
  2. 1033 en-US English (United States)
  3. Orion\N00byEdge, local user. Computer is on a domain. Computer name is Orion.
  4. Upgraded from W7 -> W10 Release -> W10 IP

Computer joined domain after W7 upgrade, I'm pretty sure. May or may not have been before going IP.

@N00byEdge

This comment has been minimized.

Show comment
Hide comment
@N00byEdge

N00byEdge Jun 22, 2016

I tried doing the same thing with a domain user with only letters in the username, same issue.

N00byEdge commented Jun 22, 2016

I tried doing the same thing with a domain user with only letters in the username, same issue.

@benhillis

This comment has been minimized.

Show comment
Hide comment
@benhillis

benhillis Jun 22, 2016

Member

Thanks for the info, I will try to reproduce this.

Member

benhillis commented Jun 22, 2016

Thanks for the info, I will try to reproduce this.

@benhillis

This comment has been minimized.

Show comment
Hide comment
@benhillis

benhillis Jun 22, 2016

Member

@N00byEdge To confirm, you're using the en-US version of Windows not sv-SE? Originally you said you were using Swedish so that's what I installed.

Member

benhillis commented Jun 22, 2016

@N00byEdge To confirm, you're using the en-US version of Windows not sv-SE? Originally you said you were using Swedish so that's what I installed.

@N00byEdge

This comment has been minimized.

Show comment
Hide comment
@N00byEdge

N00byEdge Jun 23, 2016

Sorry, maybe I should have typed out this in the last post. I have English language with Swedish input, and a Swedish language pack for spelling and hand writing, but I am using English as Windows and UI language:

CurrentCulture   : sv-SE
CurrentUICulture : en-US

from Get-Host in powersell

N00byEdge commented Jun 23, 2016

Sorry, maybe I should have typed out this in the last post. I have English language with Swedish input, and a Swedish language pack for spelling and hand writing, but I am using English as Windows and UI language:

CurrentCulture   : sv-SE
CurrentUICulture : en-US

from Get-Host in powersell

@benhillis

This comment has been minimized.

Show comment
Hide comment
@benhillis

benhillis Jun 28, 2016

Member

Unfortunately I'm still unable to reproduce this locally. If you would be able to take a sample profile trace so we can identify where /bin/bash is getting stuck that'd be very useful. I have instructions in another thread: #358 (comment)

Let me know if you have any questions.

Member

benhillis commented Jun 28, 2016

Unfortunately I'm still unable to reproduce this locally. If you would be able to take a sample profile trace so we can identify where /bin/bash is getting stuck that'd be very useful. I have instructions in another thread: #358 (comment)

Let me know if you have any questions.

@N00byEdge

This comment has been minimized.

Show comment
Hide comment
@N00byEdge

N00byEdge Jun 28, 2016

C:\WINDOWS\system32>xperf.exe -on PROC_THREAD+LOADER+INTERRUPT+DPC+PROFILE -stackwalk profile -minbuffers 16 -maxbuffers 1024 -flushtimer 0 -f tmp.etl
xperf: error: NT Kernel Logger: Cannot create a file when that file already exists. (0xb7).

There is not a single tmp.etl on my system. What should I look for?

N00byEdge commented Jun 28, 2016

C:\WINDOWS\system32>xperf.exe -on PROC_THREAD+LOADER+INTERRUPT+DPC+PROFILE -stackwalk profile -minbuffers 16 -maxbuffers 1024 -flushtimer 0 -f tmp.etl
xperf: error: NT Kernel Logger: Cannot create a file when that file already exists. (0xb7).

There is not a single tmp.etl on my system. What should I look for?

@N00byEdge

This comment has been minimized.

Show comment
Hide comment
@N00byEdge

N00byEdge Jun 28, 2016

I don't know if it's worth mentioning, but when it was running, I was getting #143.

N00byEdge commented Jun 28, 2016

I don't know if it's worth mentioning, but when it was running, I was getting #143.

@benhillis

This comment has been minimized.

Show comment
Hide comment
@benhillis

benhillis Jun 28, 2016

Member

@N00byEdge The above error means you're already collecting a trace, use xperf.exe -d profile.etl to stop.

Member

benhillis commented Jun 28, 2016

@N00byEdge The above error means you're already collecting a trace, use xperf.exe -d profile.etl to stop.

@N00byEdge

This comment has been minimized.

Show comment
Hide comment
@N00byEdge

N00byEdge Jun 28, 2016

That did not work.

C:\WINDOWS\system32>xperf.exe -d profile.etl
xperf: error: Merge ETL: The system cannot find the path specified. (0x3).

C:\WINDOWS\system32>xperf.exe -on PROC_THREAD+LOADER+INTERRUPT+DPC+PROFILE -stackwalk profile -minbuffers 16 -maxbuffers 1024 -flushtimer 0 -f tmp.etl
xperf: error: NT Kernel Logger: Cannot create a file when that file already exists. (0xb7).

N00byEdge commented Jun 28, 2016

That did not work.

C:\WINDOWS\system32>xperf.exe -d profile.etl
xperf: error: Merge ETL: The system cannot find the path specified. (0x3).

C:\WINDOWS\system32>xperf.exe -on PROC_THREAD+LOADER+INTERRUPT+DPC+PROFILE -stackwalk profile -minbuffers 16 -maxbuffers 1024 -flushtimer 0 -f tmp.etl
xperf: error: NT Kernel Logger: Cannot create a file when that file already exists. (0xb7).
@benhillis

This comment has been minimized.

Show comment
Hide comment
@benhillis

benhillis Jun 28, 2016

Member

This is probably because you're running out of System32. Can you change to a different directory like your desktop?

Member

benhillis commented Jun 28, 2016

This is probably because you're running out of System32. Can you change to a different directory like your desktop?

@N00byEdge

This comment has been minimized.

Show comment
Hide comment
@N00byEdge

N00byEdge Jun 28, 2016

F:\>mkdir dmp

F:\>cd dmp

F:\dmp>xperf.exe -on PROC_THREAD+LOADER+INTERRUPT+DPC+PROFILE -stackwalk profile -minbuffers 16 -maxbuffers 1024 -flushtimer 0 -f tmp.etl
xperf: error: NT Kernel Logger: Cannot create a file when that file already exists. (0xb7).

F:\dmp>xperf.exe -d profile.etl
xperf: error: Merge ETL: The system cannot find the path specified. (0x3).

F:\dmp>mkdir C:\Users\N00byEdge\Desktop\dmp

F:\dmp>cd /d C:\Users\N00byEdge\Desktop\dmp

C:\Users\N00byEdge\Desktop\dmp>xperf.exe -on PROC_THREAD+LOADER+INTERRUPT+DPC+PROFILE -stackwalk profile -minbuffers 16 -maxbuffers 1024 -flushtimer 0 -f tmp.etl
xperf: error: NT Kernel Logger: Cannot create a file when that file already exists. (0xb7).

C:\Users\N00byEdge\Desktop\dmp>xperf.exe -d profile.etl
xperf: error: Merge ETL: The system cannot find the path specified. (0x3).

N00byEdge commented Jun 28, 2016

F:\>mkdir dmp

F:\>cd dmp

F:\dmp>xperf.exe -on PROC_THREAD+LOADER+INTERRUPT+DPC+PROFILE -stackwalk profile -minbuffers 16 -maxbuffers 1024 -flushtimer 0 -f tmp.etl
xperf: error: NT Kernel Logger: Cannot create a file when that file already exists. (0xb7).

F:\dmp>xperf.exe -d profile.etl
xperf: error: Merge ETL: The system cannot find the path specified. (0x3).

F:\dmp>mkdir C:\Users\N00byEdge\Desktop\dmp

F:\dmp>cd /d C:\Users\N00byEdge\Desktop\dmp

C:\Users\N00byEdge\Desktop\dmp>xperf.exe -on PROC_THREAD+LOADER+INTERRUPT+DPC+PROFILE -stackwalk profile -minbuffers 16 -maxbuffers 1024 -flushtimer 0 -f tmp.etl
xperf: error: NT Kernel Logger: Cannot create a file when that file already exists. (0xb7).

C:\Users\N00byEdge\Desktop\dmp>xperf.exe -d profile.etl
xperf: error: Merge ETL: The system cannot find the path specified. (0x3).
@benhillis

This comment has been minimized.

Show comment
Hide comment
@benhillis

benhillis Jun 28, 2016

Member

And you're running this in an Admin command prompt?

Can you run "which xperf.exe"?

Member

benhillis commented Jun 28, 2016

And you're running this in an Admin command prompt?

Can you run "which xperf.exe"?

@N00byEdge

This comment has been minimized.

Show comment
Hide comment
@N00byEdge

N00byEdge Jun 28, 2016

Yes.

C:\WINDOWS\system32>which xperf.exe
'which' is not recognized as an internal or external command,
operable program or batch file.

N00byEdge commented Jun 28, 2016

Yes.

C:\WINDOWS\system32>which xperf.exe
'which' is not recognized as an internal or external command,
operable program or batch file.
@benhillis

This comment has been minimized.

Show comment
Hide comment
@benhillis

benhillis Jun 28, 2016

Member

Sorry I mean "where xperf.exe". Linux is creeping into my world :)

Member

benhillis commented Jun 28, 2016

Sorry I mean "where xperf.exe". Linux is creeping into my world :)

@N00byEdge

This comment has been minimized.

Show comment
Hide comment
@N00byEdge

N00byEdge Jun 28, 2016

Ah, thought so.

C:\WINDOWS\system32>where xperf.exe
C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\xperf.exe

I don't know what kind of voodoo magic you are working, though.

N00byEdge commented Jun 28, 2016

Ah, thought so.

C:\WINDOWS\system32>where xperf.exe
C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\xperf.exe

I don't know what kind of voodoo magic you are working, though.

@N00byEdge

This comment has been minimized.

Show comment
Hide comment
@N00byEdge

N00byEdge Jun 28, 2016

Huh, that's interesting. I literally uninstalled the Windows 10 kit when I installed the W8.1 kit you requested me to install. Will retry install.

N00byEdge commented Jun 28, 2016

Huh, that's interesting. I literally uninstalled the Windows 10 kit when I installed the W8.1 kit you requested me to install. Will retry install.

@benhillis

This comment has been minimized.

Show comment
Hide comment
@benhillis

benhillis Jun 28, 2016

Member

Nope that's perfect. Thank you very much, I hope this sheds some light on the issue!

Member

benhillis commented Jun 28, 2016

Nope that's perfect. Thank you very much, I hope this sheds some light on the issue!

@N00byEdge

This comment has been minimized.

Show comment
Hide comment
@N00byEdge

N00byEdge Jun 29, 2016

Just caught this little guy in the corner of my eye in the taskbar all of a sudden for the first time since my issues started: http://puu.sh/pK5S7.png

It's frozen, I don't know how long it has been for, but at least a couple of minutes after finding it.

N00byEdge commented Jun 29, 2016

Just caught this little guy in the corner of my eye in the taskbar all of a sudden for the first time since my issues started: http://puu.sh/pK5S7.png

It's frozen, I don't know how long it has been for, but at least a couple of minutes after finding it.

@N00byEdge

This comment has been minimized.

Show comment
Hide comment
@N00byEdge

N00byEdge Jun 29, 2016

Now Bash.exe gives this:

C:\Users\N00byEdge>bash
Cannot launch bash because the LX subsystem has an install, uninstall, or servicing operation pending.

Do I reinstall at this point?

N00byEdge commented Jun 29, 2016

Now Bash.exe gives this:

C:\Users\N00byEdge>bash
Cannot launch bash because the LX subsystem has an install, uninstall, or servicing operation pending.

Do I reinstall at this point?

@benhillis

This comment has been minimized.

Show comment
Hide comment
@benhillis

benhillis Jun 29, 2016

Member

Just close that update window.

Member

benhillis commented Jun 29, 2016

Just close that update window.

@N00byEdge

This comment has been minimized.

Show comment
Hide comment
@N00byEdge

N00byEdge Jun 29, 2016

Yeah, I did.

N00byEdge commented Jun 29, 2016

Yeah, I did.

@benhillis

This comment has been minimized.

Show comment
Hide comment
@benhillis

benhillis Jun 29, 2016

Member

I received your trace and I've identified what's getting hung. I'd like to try to get a repro locally so I can validate my fix. Out of curiosity do you not have a page file on your system?

You can check this via:
Advanced system settings -> Advanced tab -> Performance Settings -> Advanced tab -> Virtual memory Change

Member

benhillis commented Jun 29, 2016

I received your trace and I've identified what's getting hung. I'd like to try to get a repro locally so I can validate my fix. Out of curiosity do you not have a page file on your system?

You can check this via:
Advanced system settings -> Advanced tab -> Performance Settings -> Advanced tab -> Virtual memory Change

@N00byEdge

This comment has been minimized.

Show comment
Hide comment
@N00byEdge

N00byEdge Jun 29, 2016

I have a page file, but not on my main drive, my ssd raid. I had one on there though up until about 4 days ago.

N00byEdge commented Jun 29, 2016

I have a page file, but not on my main drive, my ssd raid. I had one on there though up until about 4 days ago.

@N00byEdge

This comment has been minimized.

Show comment
Hide comment
@N00byEdge

N00byEdge commented Jun 29, 2016

Here is a screenshot: http://puu.sh/pKqEC.png

@benhillis

This comment has been minimized.

Show comment
Hide comment
@benhillis

benhillis Jun 29, 2016

Member

Ok but you do have multiple page files. I think I see what the issue is let me confirm my hypothesis.

Member

benhillis commented Jun 29, 2016

Ok but you do have multiple page files. I think I see what the issue is let me confirm my hypothesis.

@benhillis

This comment has been minimized.

Show comment
Hide comment
@benhillis

benhillis Jun 29, 2016

Member

@N00byEdge Thank you very much for your patience and persistence. I would not have been able to figure this out without your help!

Because of your trace file I have identified a bug in the code that is calculating the swap file size. This function is used by both the sysinfo system call and generating the contents of /proc/meminfo. This problem will happen when you have multiple pagefiles on your machine. There are three different outcomes that can happen as a result of this bug:

  1. The swapfile size will be reported incorrectly
  2. Our driver will dereference an invalid memory address and cause a bluescreen
  3. The machine will enter an infinite loop when calculating the swap file size (this is the one you are seeing)

As a temporary workaround if you remove all but one of your pagefiles you should be able to use WSL. I am coding up a fix for this right now.

Member

benhillis commented Jun 29, 2016

@N00byEdge Thank you very much for your patience and persistence. I would not have been able to figure this out without your help!

Because of your trace file I have identified a bug in the code that is calculating the swap file size. This function is used by both the sysinfo system call and generating the contents of /proc/meminfo. This problem will happen when you have multiple pagefiles on your machine. There are three different outcomes that can happen as a result of this bug:

  1. The swapfile size will be reported incorrectly
  2. Our driver will dereference an invalid memory address and cause a bluescreen
  3. The machine will enter an infinite loop when calculating the swap file size (this is the one you are seeing)

As a temporary workaround if you remove all but one of your pagefiles you should be able to use WSL. I am coding up a fix for this right now.

@N00byEdge

This comment has been minimized.

Show comment
Hide comment
@N00byEdge

N00byEdge Jun 29, 2016

Thanks, I love WSL and will temprarely disable all but one pagefile and come back with my results. Also, will you report back when this is fixed (will it be in the next build)?

N00byEdge commented Jun 29, 2016

Thanks, I love WSL and will temprarely disable all but one pagefile and come back with my results. Also, will you report back when this is fixed (will it be in the next build)?

@N00byEdge

This comment has been minimized.

Show comment
Hide comment
@N00byEdge

N00byEdge Jun 29, 2016

I can confirm that WSL yet again works with a single swapfile! Thanks for all the persistence and help!

C:\Users\N00byEdge>bash
root@ORION:/mnt/c/Users/N00byEdge#

N00byEdge commented Jun 29, 2016

I can confirm that WSL yet again works with a single swapfile! Thanks for all the persistence and help!

C:\Users\N00byEdge>bash
root@ORION:/mnt/c/Users/N00byEdge#

@N00byEdge N00byEdge closed this Jun 29, 2016

@benhillis

This comment has been minimized.

Show comment
Hide comment
@benhillis

benhillis Jun 29, 2016

Member

Great to hear, I'm going to reopen this thread until the issue is fixed in an insider build but I will tag the thread with "workaround available"

Member

benhillis commented Jun 29, 2016

Great to hear, I'm going to reopen this thread until the issue is fixed in an insider build but I will tag the thread with "workaround available"

@N00byEdge

This comment has been minimized.

Show comment
Hide comment
@N00byEdge

N00byEdge Jun 29, 2016

Okay, fair enough.

N00byEdge commented Jun 29, 2016

Okay, fair enough.

@CryptXor

This comment has been minimized.

Show comment
Hide comment
@CryptXor

CryptXor Aug 12, 2016

+1 to the install, update, upgrade/etc/etc not working. Running under sudo su

root@MSI:/home/<blabla># apt-get update
Err http://security.ubuntu.com trusty-security InRelease

Err http://archive.ubuntu.com trusty InRelease

Err http://archive.ubuntu.com trusty-updates InRelease

Err http://security.ubuntu.com trusty-security Release.gpg
  Could not resolve 'security.ubuntu.com'
Err http://archive.ubuntu.com trusty Release.gpg
  Could not resolve 'archive.ubuntu.com'
Err http://archive.ubuntu.com trusty-updates Release.gpg
  Could not resolve 'archive.ubuntu.com'
Reading package lists... Done
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/trusty/InRelease

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/trusty-updates/InRelease

W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/trusty-security/InRelease

W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/trusty-security/Release.gpg  Could not resolve 'security.ubuntu.com'

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/trusty/Release.gpg  Could not resolve 'archive.ubuntu.com'

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/trusty-updates/Release.gpg  Could not resolve 'archive.ubuntu.com'

W: Some index files failed to download. They have been ignored, or old ones used instead.

My firewall is not blocking anything because I tried with everything disabled as well. Yesterday I could ping http://archive.ubuntu.com from the powershell but not winbash and now neither works. Error with conical?

CryptXor commented Aug 12, 2016

+1 to the install, update, upgrade/etc/etc not working. Running under sudo su

root@MSI:/home/<blabla># apt-get update
Err http://security.ubuntu.com trusty-security InRelease

Err http://archive.ubuntu.com trusty InRelease

Err http://archive.ubuntu.com trusty-updates InRelease

Err http://security.ubuntu.com trusty-security Release.gpg
  Could not resolve 'security.ubuntu.com'
Err http://archive.ubuntu.com trusty Release.gpg
  Could not resolve 'archive.ubuntu.com'
Err http://archive.ubuntu.com trusty-updates Release.gpg
  Could not resolve 'archive.ubuntu.com'
Reading package lists... Done
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/trusty/InRelease

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/trusty-updates/InRelease

W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/trusty-security/InRelease

W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/trusty-security/Release.gpg  Could not resolve 'security.ubuntu.com'

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/trusty/Release.gpg  Could not resolve 'archive.ubuntu.com'

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/trusty-updates/Release.gpg  Could not resolve 'archive.ubuntu.com'

W: Some index files failed to download. They have been ignored, or old ones used instead.

My firewall is not blocking anything because I tried with everything disabled as well. Yesterday I could ping http://archive.ubuntu.com from the powershell but not winbash and now neither works. Error with conical?

@N00byEdge

This comment has been minimized.

Show comment
Hide comment
@N00byEdge

N00byEdge Aug 14, 2016

@CryptXor Wait, doesn't that imply that the install worked for you? Are you sure this is the correct issue? this issue is for WSL not installing properly, not an Internet connectivity issue like yours.

N00byEdge commented Aug 14, 2016

@CryptXor Wait, doesn't that imply that the install worked for you? Are you sure this is the correct issue? this issue is for WSL not installing properly, not an Internet connectivity issue like yours.

@ReginaldShao

This comment has been minimized.

Show comment
Hide comment
@ReginaldShao

ReginaldShao Oct 16, 2016

i solved the problem by disable the function,restart computer and enable the function again.
then,when i run bash command,it worked!
1

ReginaldShao commented Oct 16, 2016

i solved the problem by disable the function,restart computer and enable the function again.
then,when i run bash command,it worked!
1

@vitordouzi

This comment has been minimized.

Show comment
Hide comment
@vitordouzi

vitordouzi Mar 15, 2017

In my case, any mv or cp command was blocked by the windows firewall. When I cancel one of this command, the problem with the uninstall happens. Try to disable the firewall, reboot the windows and run the uninstall. That work with me.

vitordouzi commented Mar 15, 2017

In my case, any mv or cp command was blocked by the windows firewall. When I cancel one of this command, the problem with the uninstall happens. Try to disable the firewall, reboot the windows and run the uninstall. That work with me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment