Visual Studio 2022 generates virus?

Michael Frandsen 16 Reputation points
2021-12-22T06:46:13.877+00:00

I was just now following a tutorial and asked to run my code.
The execution failed because it did not have access to the file, and my virus scanner then reported the file had been quarantined as it detected Gen:Variant.Cerbu.123013
Anyone else experiencing this behavior?

Developer technologies | C#
{count} vote

3 answers

Sort by: Most helpful
  1. Karen Payne MVP 35,586 Reputation points Volunteer Moderator
    2021-12-22T16:33:21.05+00:00

    Any anti-virus software that is reputable has one or more exclusion list which in your case (no knowledge of Chili Security) should be able to excluded the folder for your executable under the debug folder which includes the executables and also should be able to grant access to the any other resource via Chili Security or Active Directory. And if by chance running AD under an organization you may need to work with their engineers.

    And as mentioned by @Anonymous Visual Studio is used by countless developers thus not a Visual Studio issue.

    1 person found this answer helpful.

  2. Michael Frandsen 16 Reputation points
    2021-12-22T17:34:28.213+00:00

    Not installing the update "ML.NET Model Builder 2022" and it was not detected as a threat.

    1 person found this answer helpful.
    0 comments No comments

  3. José Feitosa de Andrade Filho 0 Reputation points
    2024-06-06T12:52:58.2266667+00:00

    I had the same problem, however when updating a project with VS2022, originally done in VS2015 and using VB. After compiling and taking the executable to the installation folder, a few seconds after replacing the old executable, Windows Defender detected a virus (Win32/Nuqel!pz), removed it from the run folder and quarantined it. My client, who needed to use the new version, had to put the executable as an exception, which is a reduced security condition.

    After a few hours of research and testing, I came up with a solution: I selected Sign Assembly and then chose a strong-named key file. I recompiled it and there was no more problem.

    Prior to this, as soon as I put the project into VS2022, I selected Sign ClickOnce manifests and created a valid certificate. But this was not enough.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.