Hi -- I hope I have the right forum -- if not please let me know where I should be posting this. My company's IT has recently switched us from MS ForeFront to ESET NOD32 188.8.131.52 and I have been experiencing some problems with Visual Studio under certain circumstances. The bottom line is that ESET (ekrn.exe) seems to be locking certain EXE and DLL files for up to a couple minutes occasionally. There are two specific scenarios I have identified that are causing issues with ESET that were not a problem with ForeFront: #1: After build, exe gets locked for a couple minutes: Create a small console application in Visual Studio, build it, and use CTRL-F5 to run it in a console. After it opens, close the console again. Try and rebuild the project immediately (e.g. with CTRL-SHIFT-B), and an error occurs that the exe file to build to is locked (Access Denied) after 10 tries. Try again and get the same error. Wait a couple minutes and the file will finally be freed up even though it was no longer being used anyway. Using ProcMon from SysInternals Suite from Microsoft, I was able to determine that ESET (ekrn.exe) is locking the exe file when you run it from Visual Studio, and does not seem to be unlocking it again in a timely manner – e.g. at least 60-120 seconds if not longer in some cases. #2: (More complicated scenario, but probably a similar cause) Create a new solution, SQL 2008 Database project, and SQL 2008 CLR project. Reference the SQL CLR project from the database project. The SQL CLR project compiles to a DLL. Deploy the SQL CLR project to a SQL database somewhere. Doing a Schema Compares between the project referencing the SQL CLR DLL and the database where it was deployed to will intermittently crash Visual Studio and the embedded exception is Access Denied in SQL Server Compact Edition -- indicating most likely that ESET has the SQL CLR DLL file locked (or a temporary copy of a DLL of the CLR assembly from the remote server used in the schema compare). In this solution scenario, sometimes Visual Studio will crash simply when it opens and build the database project in the background. Also, deploys will sometimes fail with the same error (Access Denied to file). In all of the above three cases, using a tool like ProcessHacker to kill ekrn.exe right before the operation will allow the operation to complete without crashing or errors. What is the best way to resolve this issue? I need to get our IT dept some help so they can fix this and we can get back to some level of productivity.