Hello
I have a desktop and a laptop. The desktop has an AMD Athlon 64 X2 5200+ chip while the laptop has a Intel Mobile Core 2 Solo SU3500 1.40GHz chip.
Although the AMD chip is supposed to be faster, the exact same “Hello, world!” .Net applets take much longer to load than on the laptop.
Since the desktop has Comodo Internet Security Premium (5.9.221665.2197) installed while the laptop is empty, I’d like to turn off CIS (not uninstall) on the desktop, reboot, start the .Net applets, check if they do start faster, and re-enable CIS.
What is the safe way to do this?
FWIW, CIS is configured thusly: Antivirus and firewall are ON, and I disabled Defense+ because I was tired of the pop-ups and “Sandbox security level” is also disabled.
Thank you.
As an add-on: Considering the huge number of files a simple .Net “Hello, world!” applet loads, does CIS inspect each and everyone of them, and if yes, is there a way to mark those files as safe so that CIS ignores them and improves performance?
C:\WINDOWS\system32\advapi32.dll 5.1.2600.5755 Advanced Windows 32 Base API
C:\WINDOWS\system32\apphelp.dll 5.1.2600.5512 Application Compatibility Client Library
C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\clr.dll 4.0.30319.269 Microsoft .NET Runtime Common Language Runtime - WorkStation
C:\WINDOWS\system32\comctl32.dll 5.82.2900.6028 Common Controls Library
C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.6028_x-ww_61e65202\comctl32.dll 6.0.2900.6028 User Experience Controls Library
C:\WINDOWS\system32\comdlg32.dll 6.0.2900.5512 Common Dialogs DLL
ctype.nls C:\WINDOWS\system32\ctype.nls
C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\Culture.dll 4.0.30319.1 Microsoft Globalization Support
C:\Documents and Settings\Fred\Local Settings\Temp\eccoext.dll 4.6.1.7 Ecco Pro Extension
C:\WINDOWS\system32\fltlib.dll 5.1.2600.5512 Filter Library
C:\WINDOWS\system32\gdi32.dll 5.1.2600.5698 GDI Client DLL
C:\WINDOWS\WinSxS\x86_Microsoft.Windows.GdiPlus_6595b64144ccf1df_1.0.6002.22791_x-ww_c8dff154\GdiPlus.dll 5.2.6002.22791 Microsoft GDI+
C:\WINDOWS\system32\guard32.dll 5.9.23139.2195 COMODO Internet Security
Hello.ni.exe WindowsApplication1 1.0.0.0 C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\Hello\23dd51face09f25930ca3b6e5401b840\Hello.ni.exe
Hello.VBExpress.exe WindowsApplication1 1.0.0.0 D:\Downloads\Hello.VBExpress.exe
C:\WINDOWS\system32\imm32.dll 5.1.2600.5512 Windows XP IMM32 API Client DLL
C:\WINDOWS\system32\kernel32.dll 5.1.2600.5781 Windows NT BASE API Client DLL
locale.nlp C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\locale.nlp
locale.nls C:\WINDOWS\system32\locale.nls
C:\WINDOWS\system32\lpk.dll 5.1.2600.5512 Language Pack
C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\Microsoft.VisualBas#\f69a4dd37c018ac04d1317d6726ead72\Microsoft.VisualBasic.ni.dll 10.0.30319.1 Visual Basic Runtime Library
C:\WINDOWS\system32\mscoree.dll 4.0.31106.0 Microsoft .NET Runtime Execution Engine
C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\mscoreei.dll 4.0.30319.1 Microsoft .NET Runtime Execution Engine
C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\mscorlib\1bdf7de454340e0ea9fc455aeaec49d9\mscorlib.ni.dll 4.0.30319.269 Microsoft Common Language Runtime Class Library
C:\WINDOWS\system32\msctf.dll 5.1.2600.5512 MSCTF Server DLL
C:\WINDOWS\system32\msctfime.ime 5.1.2600.5768 Microsoft Text Frame Work Service IME
C:\WINDOWS\system32\msvcr100_clr0400.dll 10.0.30319.1 Microsoft® C Runtime Library
C:\WINDOWS\system32\msvcrt.dll 7.0.2600.5512 Windows NT CRT DLL
C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\nlssorting.dll 4.0.30319.269 Microsoft Collation Support
C:\WINDOWS\system32\ntdll.dll 5.1.2600.6055 NT Layer DLL
C:\WINDOWS\system32\ole32.dll 5.1.2600.6168 Microsoft OLE for Windows
oleaut32.dll Microsoft Corporation 5.1.2600.6058 C:\WINDOWS\system32\oleaut32.dll
C:\WINDOWS\system32\rpcrt4.dll 5.1.2600.6022 Remote Procedure Call Runtime
C:\WINDOWS\system32\secur32.dll 5.1.2600.5834 Security Support Provider Interface
C:\WINDOWS\system32\shell32.dll 6.0.2900.6242 Windows Shell Common Dll
C:\WINDOWS\system32\shlwapi.dll 6.0.2900.5912 Shell Light-weight Utility Library
sortdefault.nlp C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\sortdefault.nlp
sortkey.nls C:\WINDOWS\system32\sortkey.nls
sorttbls.nls C:\WINDOWS\system32\sorttbls.nls
C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Configuration\4b1f1878bf47391d09f9e256fde70e4b\System.Configuration.ni.dll 4.0.30319.1 System.Configuration.dll
C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Core\0ad566912479454ed9ce37fb09de2715\System.Core.ni.dll 4.0.30319.1 .NET Framework
C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Drawing\3d0c73f63305fa092666e6488634d025\System.Drawing.ni.dll 4.0.30319.282 .NET Framework
C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System\5339ecdda252537e37def11dc77c77aa\System.ni.dll 4.0.30319.269 .NET Framework
C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Runtime.Remo#\7f9313247dd8235f6d4b63672b9ae3ad\System.Runtime.Remoting.ni.dll 4.0.30319.1 Microsoft .NET Runtime Object Remoting
C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Windows.Forms\31649acbb300c306f8359f26e94572a9\System.Windows.Forms.ni.dll 4.0.30319.278 .NET Framework
C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Xml\6e70ff4b74bed30aa8751253ed8aee56\System.Xml.ni.dll 4.0.30319.1 .NET Framework
unicode.nls C:\WINDOWS\system32\unicode.nls
C:\WINDOWS\system32\user32.dll 5.1.2600.5512 Windows XP USER API Client DLL
C:\WINDOWS\system32\usp10.dll 1.420.2600.5969 Uniscribe Unicode script processor
C:\WINDOWS\system32\uxtheme.dll 6.0.2900.5512 Microsoft UxTheme Library
C:\WINDOWS\system32\version.dll 5.1.2600.5512 Version Checking and File Installation Libraries
XCMHook.dll C:\Program Files\Common Files\XCMHook.dll
It seems like the AV module explains why .Net apps take much longer to load: When choosing “Disable”, apps start right away, even after waiting several minutes since the last try to expect Windows to unload the app + framework from its cache.
And when I choose “On Access” or “Stateful”, once again, the app takes several seconds to load.
So it looks like an antivirus is a problem when running apps that load a lot of software to run.
Is there a way to sign the framework + apps so that Comodo will just load them without inspection?
Try adding the Java executables to the AV exclusions and see if that helps.
You mean, the .Net framework, not the Java executables, I assume?
With all those files, does someone know if there’s a way to tell Comodo AV to ignore any file that belongs to the .Net framework?
I meant the .NET executables. Or you may also opt to add the DOT NET folders and the folders where your project files are in to the AV exclusions.
Thanks for the tip. I’ll experiment with that feature.
In your topic start you stated you disabled D+ because you get a lot of alerts. When using a compiler it is best to give the compiler executable the Installer/Updater policy. That way the files it will create will be started without alerting the user.
Thanks for the tip.
When using a compiler it is best to give the compiler executable the Installer/Updater policy. That way the files it will create will be started without alerting the user.
You mean that, when configured that way, the binaries that the .Net compiler creates will be marked by Windows in such a way that Comodo AV will consider them safe and will not alert the user?
Or you may also opt to add the DOT NET folders and the folders where your project files are in to the AV exclusions.
Since I disabled Comodo AV and only use it to check new files manually before running them the first time, I noticed that the delay when launching .Net apps is much lower, so Comodo AV was indeed the cause of the delay.
Is there a tutorial somewhere that explains how to tell Comodo AV that the whole .Net framework is safe, along with such and such .Net application?
No, configuring the compiler as Installer/Updater will prevent D+ from alerting.
Since I disabled Comodo AV and only use it to check new files manually before running them the first time, I noticed that the delay when launching .Net apps is much lower, so Comodo AV was indeed the cause of the delay.
Is there a tutorial somewhere that explains how to tell Comodo AV that the whole .Net framework is safe, along with such and such .Net application?
You can add the installation folders of DOT NET and the folders where you keep your binaries to the
AV exclusions.