Instead I would have expected something like: Will ONLY forego scanning the executable but still scan all files it interacts with - more secure but UNWANTED APPROACH So from what I observed so far when Visual Studio (or any application in that matter) is added as an exception, then MBAM:
and thats just for a SINGLE project.Īpply that to a hundred projects now. If I use the vs hosting process while debugging I also need to add. Turns out I not only need to add the final path to the executable but the one in the obj\. The process cannot access the file 'bin\x86\Debug\bin86.exe' because it is being used by another process.Įrror Could not copy "obj\x86\Debug\bin86.exe" to "bin\x86\Debug\bin86.exe".
#Is awave studio malware code#
This behavior is quite troubling especially with live debugging and rapid code changes.Įrror Unable to copy file "obj\x86\Debug\bin86.exe" to "bin\x86\Debug\bin86.exe".
To unlock I need to force close the file handle to the executable opened by MBAM. Although I've excluded both devenv.exe (Visual Studio 2017) and the executable of my program - every subsequent time I try to debug or recompile my VS project - after the first - it fails as MBAM Service has locked the files and won't release them so they can be replaced by the compiler.
0 kommentar(er)
