I go into settings and tell it specifically it is private but every reboot it decides that the wire plugged into my computer must be a public network.
i could understand a unsecured wireless network but this is really annoying that it is insisting that the same connection i’ve been using for many months is public on EVERY REBOOT!!!
Please fix this…it’s obnoxious when apps that work flawlessly have issues and I have to go figure out that my network is set to public and the firewall is silently blocking it. Even setting rules to allow those applications it just doesn’t listen to me. And before anyone goes to blame windows for it, I go into windows and change it to private and it goes right back to public…it only stays in private when I change it in the avast firewall.
I use the latest version of windows 10.
I don’t carry my mid tower around to coffee shops and plug them into strange networks…
No, this is how it changes the actual network connection for the computer to public. Each time I reboot it acts as if it is a brand new connection, which has the same mac address, and even the same connection name as the last 10 times I’ve rebooted.
I’m sorry to hear about the issues that you are experiencing.
Can you try disabling the option for “Enable automatic profile switching” in the Geek Area settings?
To access the Geek Area, please open the Settings screen (click the ‘cog’ icon on the Firewall page, or click “Menu” > “Settings”) > click “Search” in the top right of the screen > type geek:area in the text box and press enter/return > click “Search” in the top right of the screen > type firewall and press enter/return.
You should then see the Firewall settings - please disable the automatic profile switching option by un-checking the check next to it.
If this does not resolve the issue, can I ask whether the application is notifying you that you have connected to a new network via a pop-up window in the bottom corner of the screen every time you reboot, or is it switching the network profile silently?
It is the pop up window in the bottom right corner, and changing that option didn’t fix it. I still got the pop up after disabling the option and it was still setting it to public. I decided to try it again after changing all the connections (the ones that are actual ports on the pc) to private. Rebooted and didn’t get a popup, it just set it to public without any notification.
If you are running both Windows Firewall and Avast Firewall, you shouldn’t do that. You are going to get conflicts between both. I suggest turning off Windows Firewall if it is on, and rebooting. If active, what is the Windows Firewall setting? You seem to say it is set to Public, correct?
no, only avast firewall, but if you go to the network settings of windows there is a public/private switch that you can use to change the network from public to private. When I tried to change it there it would go right back, so that implied it was being changed elsewhere, and when I changed it in the avast firewall it was changed in the windows settings to match, and didn’t change.
Which is why I started looking for a solution to why avast kept changing it to public.
In order to resolve this, we need to have a deeper look at the program to identify what exactly is causing the issue. Could you please generate what we call a support file? Please follow the steps in this guide: https://support.avast.com/en-ww/article/Submit-support-file and post the file ID generated in the final step.
Tim, can you tell us if you are using a stand alone VPN
i use Nord vpn and on every boot up i get the popup window on bottom right with Avast showing public.
sometimes if left a while it will auto switch to private but not always.
annoying yes but ive got into the routine of just clicking it to private every time. once set to private it stays there so slightly different to yours which keeps switching back.
I have nord vpn, but I only use it when I have online games that are having issues staying connected. I guess the app is in the background, but I only use it to play a specific game or when a node goes out and cuts off a service I use. so maybe 5% of the time overall.
Hallo, we need log file to analyze the problem. Please copy the “c:\ProgramData\AVAST Software\Avast\log\FwServ.log” and “c:\ProgramData\AVAST Software\Avast\log\anen.log” files and send it to us. Better is pack whole log folder and send whole content to us.
Thank you
I have exactly the same problem of OP, has started since installing the MAY UPDATE 1903, so it’s related fo sure ( i have avast on all pc and they act the same after updating ).
[size=12pt]I hate to say this, but Avast has known for many weeks that this is an issue. I’m an Insider and have been running the slow ring builds for 1903 since late March. When I contacted Avast their response was that they don’t support Insider Builds and to roll back if I didn’t want to click each time I booted up.
I contacted them again and tried to get them in Early May because I knew that 1903 was about to come out publicly and there would be a lot of aggravated users if they did not get this handled. It seems they have not dealt with it. This is NOT A NEW PROBLEM!
I WOULD NOT recommend turning off the firewall as it really is a very MINOR issue to have to click one time at bootup. Of course it’s annoying, but I would rather have to click once than turn off protection for my system. I have not had this issue after sleeping or hibernating, only after a full restart.
Avast is still a very good antivirus and I still continue to recommend them to those I advise, but they seem to not have a handle on WHY it;s happening. I have been told that it is an issue with Windows assigning a “Virtual MAC address” for the network card/MB chip, but that doesn’t really make sense to me. (I’m majorly hardware, not a programmer, but it still sounds like a brushoff kinda response while they figure it out.
Again, if all I have to do is click it, no biggie as long as it continues to work, but it’s annoying and they should have fixed this. I also put it on Microsoft as they tend to do weird things without giving a full and proper heads up to developers to the strange changes. But Insiders have seen this coming. Avast was alerted months ago.
I have sent many logs and had a couple of very long and in depth phone calls with support, and as part of the troubleshooting even rolled back to 1809. Worked great. Going back to 1903 even with the very latest updates to Avast it still makes me select PRIVATE every bootup.
