======================================================== NOTE: Network profiles control the settings that determine how strictly Firewall protects your PC. Each time you access a known network, Avast remembers and applies the applicable Firewall profile (as previously set by you). Each time you connect to a new network, Avast prompts you to select the appropriate profile. The default profile setting when no profile is selected is Public. The network profiles are:
Private: a lower level of security suitable for when your PC is connected to a trusted network such as your home or work network. This profile enables better connectivity, and permits all communication within the network.
Public: a higher level of security suitable for when your PC is connected to a public network such as in a cafe or airport. Because public networks present greater security risks, no incoming communication is permitted when this profile is set.
“Avast is blocking Team Foundation Server” are you getting an avast alert ?
I am not receiving any alert, that’s why I thought it was a problem with TFS server or firewall, so the tec guys told me to test disabling anti virus.
“For now the only workaround I have found is disable Avast.” Are you disabling all of avast or a specific component ?
I am disabling all Avast shields.
You could first start by disabling the more obvious possible conflict, such as the web shield, but I would have expected it to give an alert. The next option would be to try disabling just the firewall component.
Having the visual studio folder wouldn’t have any impact as that is only blocking scans on that folder, not the actions of any process running from that folder.
You could also try adding the Team Foundation URL to the exclusions.
Whilst I don’t use Avast Internet Security, can you check the Firewall and see if there any notifications of blocked processes or locations.