Hi everyone!
I already checked some similar messages with no resolution or a partial one from previous releases of Visual Studio, starting from VS2013.
I understand that those items shall be fixed.
I am using avast more than 10 years and I didn´t find any problem until now, that I start developing on Visual Studio.
Previously I program on some other platforms and there was no problem with compiling, but it seems a problem with VS2022.
Step 1: I installed VS2022 with some Microsoft add-ins for C#.
Step 2: I started my first project from zero with the designer and code.
Step 3: As soon as I started debugging or compiling, Avast find everything suspicious. I report it llike 10 times with zero replies. So I stopped reporting and I excluded the folder from scanning. (And that shouldn´t be an option)
Step 4: I continue working with less problems with Avast but randomly is continuing with the suspicious file message when the folder is already excluded. (This is a non sense)
Step 5: After a few days, without notifications, and after last Avast Premium Security update to program version 25.5.10141a (build 25.5.10141.762), with virus definition 250617-4 and UI version 1.0.839, now Avast is corrupting some of my Visual Studio Cache files so I need to delete: .vs folder, bin folder, obj folder, cache files; Clean the project, Rebuild the project… and as soon as I create another form… Another Catastrophic error by file corrupted.
Is there any solution to this or I should cancel my subscription to Avast after 10 years???
The symptom that newly build binaries got sandboxed and blocked for some seconds is, afaik, the same for years since the introduction of DeepScreen or CyberCapture. Only way to avoid that is to exclude build directories for CyberCapture.
If you still see the alerts after adding exceptions, then exceptions might be wrongly set. If you post screenshots of the alerts and exceptions, I may be able to shed some light for it.
I’m not sure about file corruptions unfortunately.
Thanks for your reply. I already fixed the corruption issues. (this is happening as soon as Cybercapture stop a debugging or compiling process, that prevents some files to save, and then I am getting log differences between files) At least, that is my though because Cybercapture is not following exceptions.
Regarding exceptions, I already added and explicitally place to not to use Behavior Shield, File Shield and Cybercapture… but no way, Cybercapture is stopping debugging or compiling around 40 seconds each time that I tried to later show the message that everything looks safe.
Although exception itself looks fine, what I’m concerning is, debug binary may run from different directory which is not covered by exceptions. IIRC debug binaries run from project directory, usually under Documents.
If you don’t have screenshots, there may be debugging logs for CyberCapture below: C:\ProgramData\Avast Software\Avast\log\autosandbox.log
