nvidiaProfileInspector
nvidiaProfileInspector copied to clipboard
Release 2.4.0.4 detected as virus by Windows Defender
As the title says, release 2.4.0.4 is detected as a virus by Windows Defender. 2.4.0.3 is fine. Can you try rebuilding?
does not happen to me using windows defender too
also virustotal has just one false positive finding https://www.virustotal.com/gui/file/1233487ea4db928ee062f12b00a6eda01445d001ab55566107234dea4dc65872
Windows 11 Defender detects it as: Trojan:Win32/Wacatac.B!ml
re-checked with win10 and win11 latest virusdefinitions and manual scan all fine
I'm also having the same issue, but in win 10. Windows defender tags the .exe file as "Trojan:Win32/Wacatac.B!ml".
Go to Windows update, update Windows Defender Now update to Security Intelligence for Microsoft Defender Antivirus to KB2267602 (version 1.385.672.0) or higher.
The warning about Trojan:Script/Wacatac.H!ml disappears!!!
https://www.microsoft.com/en-us/wdsi/threats/malware-encyclopedia-description?Name=Trojan:Script/Wacatac.H!ml
I have this same issue it says on virustotal some malware so im gonna use older version
A solution would be to do the build and deploy to releases page using github actions, then it would be publicly visible what is being put there (transparent), all that is in the repo, no manual process involved.
Should be easy to do. @Orbmu2k
https://learn.microsoft.com/en-us/dotnet/architecture/devops-for-aspnet-developers/actions-build https://patriksvensson.se/posts/2020/03/creating-release-artifacts-with-github-actions
Another thing you could do in the process, is, make it a single exe, no external project files like .xml or .config
https://learn.microsoft.com/en-us/dotnet/core/deploying/single-file/overview?tabs=cli
A third thing would be to have checksum, generate sha256 for each file you build, those would be included/output in the github actions log as well as release notes in releases page. That way, no chance of reupload fake files. Therefore it's another assurance of truth.