Apologies for the double post. Upon further investigation, if there is no .exe file created by VS code and I run VS code, ESET will not detect anything and will allow VS code to create the .exe file and run normally. If I try to run VS code again when there already exists the .exe file from the previous compilation then ESET will detect the (ML/Augur) issue and delete the .exe. If I repeat the cycle, I run VS code again when there is no .exe file because it has been deleted by ESET, ESET will not detect anything and the .exe file will be created and the compilation run as normal. And again if I run VS code then ESET will detect the (ML/Augur) issue and delete the .exe file.