0 Members and 1 Guest are viewing this topic.
Thanks for the pointer - I was able to add C:\Windows\System32\bash.exe allow all in/out as a packet rule which did the job for me.
It has been confirmed on the official Microsoft's git repository that Avast causes the issue:https://github.com/Microsoft/BashOnWindows/issues/718Uninstalling Avast allows to run bash.
Quote from: Abj on August 04, 2016, 07:37:33 AMIt has been confirmed on the official Microsoft's git repository that Avast causes the issue:https://github.com/Microsoft/BashOnWindows/issues/718Uninstalling Avast allows to run bash.You don't have to uninstall. Just pause the firewall while using bash. Of course, this is a workaround not a solution.
Quote from: Lisandro on August 05, 2016, 02:12:39 AMQuote from: Abj on August 04, 2016, 07:37:33 AMIt has been confirmed on the official Microsoft's git repository that Avast causes the issue:https://github.com/Microsoft/BashOnWindows/issues/718Uninstalling Avast allows to run bash.You don't have to uninstall. Just pause the firewall while using bash. Of course, this is a workaround not a solution.I disagree. I am only using avast antivirus (not the firewall component) and just disabling it is not enough, it needs to be uninstalled. (EDIT: I am using the latest version)
Quote from: tarkio on August 05, 2016, 03:31:35 PMQuote from: Lisandro on August 05, 2016, 02:12:39 AMQuote from: Abj on August 04, 2016, 07:37:33 AMIt has been confirmed on the official Microsoft's git repository that Avast causes the issue:https://github.com/Microsoft/BashOnWindows/issues/718Uninstalling Avast allows to run bash.You don't have to uninstall. Just pause the firewall while using bash. Of course, this is a workaround not a solution.I disagree. I am only using avast antivirus (not the firewall component) and just disabling it is not enough, it needs to be uninstalled. (EDIT: I am using the latest version)Avast Free AntivĂrus should not block any connection, it's not a firewall. Besides, I'm using the Premier version and just disabling the firewall is enough.Which firewall do you use?Sometimes, the interaction between Avast and other product is bringing the error.
Tarkio, can you be more specific on your problems? Do you also have problems with programs connecting to the network from inside WSL, such as wget, or do you have problems installing the subsystem (as mentioned on the links you've posted) ? Thanks.