Viruscope and crushed application in Windows 10

I installed the CIS ver. 8.4.0.5076. However Explorer and other applications crashing. If Iturn off Viruscope just they do not crashing. What’s the problem?

When I used Visuocope i got errors in EventViwer. Eg.:

Log Name: COMODO Internet Security Trace
Source: cmdagent
Date: 28. 08. 2016 23:22:33
Event ID: 1
Task Category: cisVScopeMonitor
Level: Error
Keywords: Classic
User: N/A

Description:
Too long process chain: pid=22240 m_dwParentPid == 932

Event Xml:



1
2
24
0x80000000000000

926
COMODO Internet Security Trace
<



Too long process chain: pid=22240 m_dwParentPid == 932


Why? How to repair this issue?

I think it has not been fixed yet

https://forums.comodo.com/bug-reports-cis/viruscope-errors-in-windows-event-log-t115011.0.html

Hello,

I am sorry for bumping an old topic but I noticed the following errors in my EventViewer in the last few days.

What does this mean?

cisVScopeMonitor

Fail to open XML doc in CreateRecognizers. Error Code: 0x80070002 (The system cannot find the file specified.)

I am using Windows 8.1 x64 and I tried to repair the installation but Comodo Diagnostics didn’t find any issues.

Thanks!

Regards,
Georgi

What version of CIS/CFW/CAV do you have installed? Do you have viruscope enabled and is the recognizer dll listed in viruscope settings?

Hi,

Thank you for the reply. I am using the latest version of CIS - 10. And yes I have VirusScope enabled.

I unchecked “Monitor sandbox applications only” long time ago but the problem appeared in the last few days (probably because so far I’ve used HIPS as I wanted full control of my system behaviour and Auto-Sandbox was disabled). However I decided it is time to start using Auto-Sandbox since I became a bit lazy and a little tired of messages and turned it on but I didn’t disable HIPS just in case and because I am not afraid of additional messages and I didn’t notice any performance issues. I know that Auto-Sandbox takes precedence over HIPS.

Could this be the reason?

Thanks!

I’m not sure what caused the error. But if everything works as expected then I guess you can safely ignore it.