I uninstalled and reinstalled several times to be sure and yes CIS is the culprit. I’m assuming it has something to do with Sandboxing since I don’t have any problems with v3 but I couldn’t solve it. Selecting “Do not sandbox this application” didn’t help either…
If you select the “Run a Program in the Sandbox” option for a “run once” action (run as “Unrestricted”), Windows Live Messenger compatibility settings are correctly honoured. If you make a permanent rule though, they’re not. (What the hell? This is a serious inconsistency bug.)
If you permanently disable Defense+ (by checking the box that says so), and reboot, WLM will work correctly without further aid. You will, however, lose Defense+ AND Sandbox.
ANY OTHER combination of settings will fail. No exceptions. As long as Defense+ is not “permanently disabled”, it keeps poking its nose into the business of executables for no reason, even if Sandbox, Defense+, or BOTH are “Disabled” on the slider. It doesn’t matter. The code is still alive no matter where you put the sliders, and it knocks over the messenger program.
For pity’s sake, include an option in the setup to SKIP installing the Sandbox component. I believe that code is the source of these issues.
Alternatively, fix the component - clearly, the “run once” command works, but rule creation doesn’t, as evidenced by WLM’s behaviour.
Why is the compatibility setting the business of Sandbox anyway? It should leave the properties of my programs alone.
I hope I helped. If you have problems with WLM, then reinstall an older version of Comodo, or disable Defense+ permanently until an update is available.
I have set the sandbox level to disabled and I have set the Defense plus level to disabled.
This does not fix the problem.
What I have noticed is this.
If I turn on windows user account control, the problem is fixed (even without disabling anything).
But when I turn user account control off, something happens with comodo that it stops messneger running in the compatibility mode when user account control is off.
When user account control is enabled (and you have to click yes to start messenger, it works ok).
There is certainly a bug in the product here, because even if you turn everything off in Comodo (all levels) and have the program closed down, messenger still doesn’t run in compatibility mode when UAC is turned off.
It seems the only way to stop COMODO interfering is to uninstall it., or to turn on UAC (which is very annoying)
Can anyone else confirm this behaviour? That when you turn UAC on it works, but if you disable UAC, COMODO is somehow messing with something it shouldn’t be?
I have exactly same problem. Windows 7 Ultimate x64.
Windows live messenger 2009 icon is gone after installing Comodo Internet security, reboot and running msnmsgr.exe normal (not in sandbox) and I show two taskbar boxes. Stupid thing - I hade tring many solution (install messenger to another computer and paste windows live folder to here, disabling comodo before reboot after comodo install and more), but nothing work.
I use messenger Windows Vista compatibilty mode (tried XP, Vista sp1 and sp2 too).
PLEASE, this problem should be fixed!!! If i must choose between comodo and messenger, I choose messenger, but I want use both without problem.
I don’t want disable comodo component (guard64.dll), only want add trusted area for notification area.