Page MenuHome

Newest Build 2.81 (29.08.2019 - 33cd0535a0d3) is blocked by antivirus. Other 2.81 builds are still fine. Antivirus and its database is the same.
Closed, ArchivedPublic

Description

System Information
Operating system: Windows-10-10.0.17134 64 Bits
Graphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 419.17

Blender Version
Broken: version: 2.81 (sub 3?), branch: master, commit date: 2019-08-29 17:51, hash: 33cd0535a0d3
Worked: ()

Short description of error
[A small observation. Antivirus (Avast) prevents the latest version from running. You can't see the commandline or anything. As in other bulds, it didn't detect the publisher, but this time it recognizes that the file can be dangerous... Maybe this is not a big deal.. I didn't update antivirus so it is older than other 2.81 builds that I run normaly and its virus database is allso unupdated. So maybe something inside this build is different? Previous versions of 2.81 still work without the interference of AV and I did not have to set anything in it to allow Blender to work. :) ]

Exact steps for others to reproduce the error
[Just try to run 2.81 - 33cd0535a0d3 with Avast ]
[Based on the default startup or an attached .blend file (as simple as possible)]

Event Timeline

jeremy joe (blenderjoe) renamed this task from Newest Build 2.81 from 29.08.2019 is blocked by antivirus. Other 2.81 are fine. Antivirus and its database is the same. to Newest Build 2.81 (29.08.2019 - 33cd0535a0d3) is blocked by antivirus. Other 2.81 builds are still fine. Antivirus and its database is the same..Aug 30 2019, 12:33 AM
jeremy joe (blenderjoe) created this task.
jeremy joe (blenderjoe) edited projects, added BF Blender (2.81); removed BF Blender.
Brendon Murphy (meta-androcto) lowered the priority of this task from 90 to 50.Aug 30 2019, 2:11 AM

I'll confirm this, had to uninstall AVG anti virus.
Adding confirmed medium as it's an issue.

Ray Molenkamp (LazyDodo) changed the task status from Unknown Status to Unknown Status.Aug 30 2019, 2:28 AM
Ray Molenkamp (LazyDodo) claimed this task.

The build this was reported on is no longer on the build bot, but this is today's build run through virus total

squeaky clean.

https://www.virustotal.com/gui/file/98d48cad7593f6f260d31cb151fb1b0a7df0610b6e235f83cf3498250b9c44ee/detection

Once we sign the build bot builds the unknown publisher warns should go away, but that is already tracked on the platform module, no need to keep this ticket around given there's nothing we can do

Ok :) Of course :) This time for them it was not a matter of unknown publisher cause every build has unknown publisher and antivirus never blocks any 2.81 build. I got a respond from Avast. I uploaded this buid to their data labs. I knew it was clean :), it was only a problem tu run it. They checked it and lebeled it as a safe file so probably for all Avast users it would be easier for now to avoid this problem. If other build would have similar problems - Avast gives the same option to send them the file to analisys and addiction to safe list. For AVG users it could be different.