I don't know what is happening, but now my antivirus is putting down my VEDA when trying to use it. At the same time, other programs and applications are working fine.
My version is 3.0.2.0. For now, I am using it by putting it in the exceptions list, I am not sure others have the same issue. Tried to check the .exe file with the Virustotal service and it gives a different report.
(12-03-2024, 05:26 PM)BSR Wrote: Hi VEDA developers,
I don't know what is happening, but now my antivirus is putting down my VEDA when trying to use it. At the same time, other programs and applications are working fine.
My version is 3.0.2.0. For now, I am using it by putting it in the exceptions list, I am not sure others have the same issue. Tried to check the .exe file with the Virustotal service and it gives a different report.
What do you think, if reinstallation can help me?
Thanks,
Bakytzhan
Dear Bakytzhan,
You can reinstall Veda 2.0 and after reinstalling, completely delete the Veda folder so that no threat remains.
OR
You have the option to exclude the Veda folder from both custom or scheduled scans and add it to the whitelist, preventing McAfee from scanning it for potential threats.
(12-03-2024, 05:26 PM)BSR Wrote: Hi VEDA developers,
I don't know what is happening, but now my antivirus is putting down my VEDA when trying to use it. At the same time, other programs and applications are working fine.
My version is 3.0.2.0. For now, I am using it by putting it in the exceptions list, I am not sure others have the same issue. Tried to check the .exe file with the Virustotal service and it gives a different report.
What do you think, if reinstallation can help me?
Thanks,
Bakytzhan
Dear Bakytzhan,
You can reinstall Veda 2.0 and after reinstalling, completely delete the Veda folder so that no threat remains.
OR
You have the option to exclude the Veda folder from both custom or scheduled scans and add it to the whitelist, preventing McAfee from scanning it for potential threats.
I already added it to exclusions. I am just curious is there something inside the VEDA that is causing this, since Virustotal service also finding something? Maybe you can try to explore what is causing this and potentially address it in the next releases.