Problem in Comodo start and work[V6]

I am using latest CIS 6.3.294583.2937 on Windows 7 Ultimate and I have a problem: during system reboot Comodo tray icon doesn’t appear and Comodo Diagnostics asks about checking for errors but cannot find them.

Also after power on hibernated system sometimes it is not possible to connect network and I cannot start any new process (and that’s why I cannot prepare a diagnostic report in this case). I cannot restart / power off the system in this case (possibly because new process are frozen) and the only solution is cold reboot.

These two problem are observed on two different systems with Win7Ult - one is x32 and the second is x64. It disappears with uninstalling Comodo.

Today I have a huge download using uTorrent on x32 system and I observe the problem with network/process freezing without even hibernating! So I have to cold reboot the system (because normal power off doesn’t work) and after that during system start I observe Comodo Diagnostics error again - but in this time I can obtain a report, because something was found. It is attached.

Please let me know what is wrong.

[attachment deleted by admin]

To me this sounds like something may be interfeering. Please try reinstalling CIS by following the advice I give in this topic. Be sure to run the removal tools for CIS. Also, run removal tools for any other security prorams which used to be installed on the computer, but are now uninstalled.

Once CIS is reinstalled do not change any settings or import a configuration. Leave everything default.

See if that solves the issue.

If not then please edit your first post such that it is in the format provided here, and fill out all responses after the colons.

Thanks.

Dear Sirs!

Pardon me, but this is ridiculous in some way.
Earlier, I have posted a message about possible problems with network activity with CIS. Now the problem still exists, so it looks like nobody cares about that. I am not sure the possibility to pass firewall blockage is not important issue, but as I said - it still exists.

Now you propose me to install CIS on a clean system and test it with empty configuration. Let me know - for what? Sure it will work, but I cannot imagine somebody who will use Internet Security set for pure system and without changing the configuration.

Sure there could be some interferences - but I have the only Emsisoft Anti-malware that was not reported as interfering. There is no any other firewall / HIPS or something else security-related.

Moreover the fact the problem exists both on x86 and x64 systems with different software installed shows the problem is not caused by interferences.

I will be happy to present any logs/reports etc, but the test of CIS on pure system won’t show any problem - and it doesn’t mean the problem can be forgotten.

I didn’t mean to imply that the problem should be forgotten or ignored. What I usually do is try to give advice such that if a user is seeing issues with their computer which could possibly be fixed by some action, so there computer could get back to working order, I will try that first. Also, ensuring that this does not fix the issue will help the devs as it will have ruled out many different possible scenarios which could have caused this issue. That’s why I asked that you try it.

Even if it doesn’t fix anything it will rule out many possible issues, which the devs will no longer have to check. Thus, please follow the advice in my last post and let me know how it goes. If it doesn’t make a difference, or if you find that it only happens for certain configurations, this is critical information which should be included in the report. This is all about trying to narrow down the problem such that it becomes more easily fixable.

I apologize if my previous post made it appear otherwise. I really am just trying to help.

Thank you.

Dear Chiron,

sure the problem is absent on a clean install of CIS. At least during last few hibernation-reboot cycles. Unfortunately I cannot guarantee 100% absence because above mentioned issues appeared from time to time.

Okay. What I would recommend is to start from the clean install. Then configure it however you like. If the problem returns then we can rule out a failed install or uninstall, which is very important for bugs of this nature. Also, make sure you run the removal tools for any antivirus products which used to be installed, but are now removed. These can be found on this page.

Thus, if it does return please edit your first post such that it is in the format provided here.

Thank you.

Any update on this?

PM reminder sent.

I will now move this to the Non-Format Verified board.

Topics in this board are rarely looked at by the devs, and even if they are it is unlikely the devs can fix the bugs reported. The reason is that putting bug reports in the required format, with the required files, ensures that the devs have enough information to understand and identify the bug. Thus, without this it becomes very difficult to replicate a bug such as yours.

To get your report forwarded to the devs please attach the files I requested, and modify your first post so that it is in the format I requested, with all required information filled out. Then send me a PM.

If you have any questions please do not hesitate to ask.

Thank you.

Can you please check and see if this is fixed with the newest version (7.0.313494.4115)? Please respond to this topic letting us know whether it is fixed or if you are still experiencing the problem.

Also, note that all bug reports in the Non-Format section of the forum, which is where this report currently is, are mainly not looked at by the devs. Thus, if the bug you were experiencing is still not fixed please edit your first post so that it is in the correct format (found here, with all required attachments), so I can forward this to the devs and get this problem fixed.

Thank you.

PM sent.

It was OK in latest 6th versions and it is OK now in 7th.
Actually I just installed (upgraded) it, but I cannot see any problem yet.

Thank you for checking this. In that case I will move this to Resolved.

Thanks.