Jump to content

KIS blocking my .net 5.0 blazor application from running


Go to solution Solved by Berny,

Recommended Posts

Posted

Hi,

KIS started blocking .net 5.0 blazor application from running. it says it is a trojan.

object name: VHO:Trojon.Win32.Sdum.gen.

 

 

I think it as a false positive.

Is this normal

Posted

Dear Berny,

I have submitted the file for analysis nothing was there. So, I resubmitted with my info.

All I have to do now is wait.

Thanks for your prompt reply.

cheers

Posted

Hello,

I have the same problem with a .NET 5.0 Worker Service application (not Blazor).

Kaspersky removes it after compilation, I also cannot upload it for false positive review (the link above) because Kaspersky is blocking connection due to transmitting virus.

The app is just a template app created using Visual Studio→New Project→Worker Service (C#)→(type any name)→Select .NET 5.0→ Create, right after creating click “Compile” (no code added), Kaspersky will throw 2 viruses: 1st is projectname.exe, 2nd is apphost.exe.

The same steps with .NET Core 3.1 works fine (does NOT throw virus)

Adding exceptions for these files work fine but is less than ideal when creating multiple new apps.

Regards,
Dawid

Posted

@DawidIzydor Welcome. Only if you  really trust the application you could eventually disable the recommended automatic actions , then restore and trust the quarantined object  and re-enable the interactive protection.

Posted

@Berny please fix this. .NET 5 is a major new release and you will have a lot of .NET programmers blocked by KIS. For me, I cannot figure out which executable KIS does not like, I've whitelisted several, but I ended up disabling protection completely because KIS interferes so much in the communication processes that I do not know if I have a bug in my code, if .NET 5 is broken, or if the AV is blocking some executable I do not know about.

By turning KIS completely off everything works, so it will stay that way so I can do my work. Please fix this.

  • 2 weeks later...
Posted

I have had the same issue, this started with the latest update from Kaspersky. Adding exclusions does not resolve the issue.

Guest
This topic is now closed to further replies.


×
×
  • Create New...