Avast firewall blocking Bash Ubuntu on Windows 10

[Lisandro]

Thanks a lot. Interesting as it goes well here with avast free on the box.

And Premium too, I have no issues installing/uninstalling bash.
My problem is on using "git" and "repo sync" commands.

[REDACTED]

Same issue here, unable to extract the filesystem while Avast! Free is installed.

I uninstalled Avast! and let it finish installing, then re-installed Avast, however now it will not connect (Just gives me an empty terminal that I can type in and nothing happens).

Without Avast! Free installed it logs in and lets me correctly use the feature.

Note: Disabling the service or the shields is not enough. It has to be fully uninstalled.

[Lisandro]

Ok, I surrender.
As I'm not using Avast Free I can't say why the Premier version is working and the Free one is not.
By the way, all this are workarounds, we really want a final solution to keep Avast on and use Ubuntu bash in Windows 10.

[REDACTED]

I am running Avast Free 12.2.2276 on Windows 10 Anniversary Update and having the same problem as tarkio has - "lxrun /install" hangs on 'extracting filesystem'. Stopping the Avast service does not resolve the issue.

[REDACTED]

Same problem in Avast IS 12.2.2276.

[lukor]

Hello guys,
It seems we might have identified some problems with the WSL (UBUNTU) subsystem (beta) related to virtualization and Avast's aswvmm.sys driver. We are working on a fix at this moment. In the meantime I'd like to ask you for more info:

- those of you who have BASH/UBUNTU working, do you have any virtualization software installed (VmWare , Virtual Box, Hyper-V) ?
- those of you who have problems - could you try disabling virtualization in the BIOS to see if that helps?

Thanks.

I can also confirm issues with firewall and PICO/WSL processes. We are also working on a fix for this problem.

Thanks a lot for your patience.
Lukas.

[REDACTED]

Bash is working on my machine with Avast Premier.
I have vmware which is installed

[Lisandro]

In the meantime I'd like to ask you for more info:
- those of you who have BASH/UBUNTU working, do you have any virtualization software installed (VmWare , Virtual Box, Hyper-V) ?

Virtualbox

- those of you who have problems - could you try disabling virtualization in the BIOS to see if that helps?

Last time I check, I cannot disable this option in the BIOS. I'm too lazy now to reboot

[bob3160]

In the meantime I'd like to ask you for more info:
- those of you who have BASH/UBUNTU working, do you have any virtualization software installed (VmWare , Virtual Box, Hyper-V) ?

Virtualbox

- those of you who have problems - could you try disabling virtualization in the BIOS to see if that helps?

Last time I check, I cannot disable this option in the BIOS. I'm too lazy now to reboot

A post after you stop being lazy and have attempted the task would be a lot more helpful 

[lukor]

Hello guys, thanks for the info and help. We have managed to fix the firewall issue. WSL processes will no longer be blocked in the next beta however still without the possibility to fine tune the rules for each Unix process. That is very tricky for us at this moment.

I'll keep you updated about the installation bug as soon as I know more.

[GautamMKGarg]

It has been confirmed on the official Microsoft's git repository that Avast causes the issue:

https://github.com/Microsoft/BashOnWindows/issues/718

Uninstalling 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.

I am using the free version of avast but still facing this issue.

[Lisandro]

Thanks Lukas.

[REDACTED]

Disabling Virtualization resulted in working bash, although bash was unable to connect to the internet.

As someone mentioned, I added "C:\Windows\System32\bash.exe allow all in/out as a packet rule", which now gives me a working ( haven't tested everything) bash.

The connection is very slow on bash for some reason.

[REDACTED]

I'm running avast premier in bootcamp attempting to use WSL too. I'm not sure about the virtualization option, but I know premier will block the bash process from working currently on my setup. Running on windows 10 anniversary.

Where would I be able to donwload the upcoming beta once it's released?

[lukor]

Hi, beta that is fixing both the installation problem and also the issue with Avast firewall blocking UBUNTU subsystem processes is already available here:

https://forum.avast.com/index.php?topic=179943.0

More info and change log:
https://forum.avast.com/index.php?topic=189694.0

Thanks for waiting!
Lukas.