Logitech vs Outpost
05 Jan
i am unhappy about outpost because it blocks my browser, messenger and also other application when i use any special function of my logitech mouse/keyboard because it uses a third application to influence for expample mozilla or IE to go back by pressing a special button of the mouse ...
outpost tells me each time that it has blocked kem.exe etc because it tried to take action on the other software to access the internet. but that is not what i want!
how can i stop outpost blocking these processes?
thank you for help!
Here's how:
Settings > Host Protection > Exclusions > Add the Logitech executable and anything else it might need > set permission to Allow for Critical Object Change
Regards,
Nash58
You need to uncheck the box under Open Process Control (see attached screenshot).
It depends on the prompt received from OP. What message do you get from Outpost?
network access blocked for firefox.exe becauseits memroy was changed by another process.
process overwrote memory stack WEBCOLCT.EXE
if i activate the checkbox 'never promt...' it does not change anything for the next time!
Regards,
chris
Best of luck to you.
Indeed. By following your recommendation I have found that only is required to add to the list the SetPoint.exe.
Somehow I felt that I was not doing the right thing by disabling the entire protection, but I was not well aware about the exclusion list, so the workaround at least gave me some break.
Thank you very much.
Regards,
Mauro
The setting to disable is in Host Protection -> Critical Systems Object Control -> Active Desktop.
Background:
I had similar case - as discussed here - yesterday and today when trying to use my new Logitech MX Revolution mouse using Logitech Setpoint v4.40.88 software.
Logitech Support suggested me to initiate with a Clean Boot of my OS (Windows Vista Ultimate) to check if it was the source of the problem. I did the test and I found that the mouse and the companion software were working fine.
Next step was to do a normal boot and I have started to disable services; when I disabled OP2008, my mouse started to work without problems. Then I dedicated my-self to find the feature in OP2008 that was interfering with Setpoint by disabling and enabling the Host Control settings; finally I found the workaround for my problem by disabling the Active Desktop of Critical Systems Object Control.
Enjoy!!
#If you have any other info about this subject , Please add it free.# |