Eset flags new Visual Studio C++ Release build .EXEs with a variant of Win64/Agent_AGen.YD trojan and cleans by deleting the file.
Visual Studio compiles without errors, links without errors, then can't run the program because Eset has swooped in and deleted the file before Visual Studio can find and run it (we're talking extremely quickly)
This is a new behavior and happens even with simple one-source-file Hello World! programs.
I've scanned my computer and Eset finds nothing wrong. It DID find the same variant in a Release .EXE I built a couple of days ago and true-to-form, deleted the file. (So, this is a new behavior). I rescanned my computer after it found that older .EXE. No problems found.
Also, Eset doesn't find anything wrong with Debug .EXEs.
All Operating System, MS Store, VS Code & Extension, Visual Studio & Extension files have been checked and are up-to-date;
I even did a cold reboot because, yeah, off then on, right? No joy.