Support Request: McAfee HIPS error - Antivirus blocking

Description

McAfee HIPS is detecting that SiteKiosk is trying to terminate McAfee processes during startup. How can we prevent SiteKiosk from attempting to disable McAfee or access it's processes? The error is attached to this ticket, "Access Protection - Prevent termination of McAfee processes" signature. This signature detects applications trying to terminate McAfee processes which are critical to the security of the systems. The prevents SiteKiosk from loading and we are stuck on a black screen.

Answer: (1)

Re: McAfee HIPS error - Antivirus blocking 1/18/2018 4:11 PM
See if you can make an exception for SiteKiosk in your antivirus and see if you are able to get SiteKiosk to get past the black screen. Some antivirus programs have the ability to keep SiteKiosk from fully starting and in the screen shot it looked like that's exactly what McAfee was trying to do.

SiteKiosk generally does not stop any Antivirus or other application from starting and only closes applications on Logout / Screen Saver activation that are added to the SiteKiosk configuration (-->Applications).

It is possible that a window / dialog from McAfee which is blocked by SiteKiosk?
Check the SiteKiosk log for an entry like this:
[SiteKiosk] Notification: According to the windows monitoring rule(Title:'xxxxxx' Class:'xxxx') the window (Title:'xxxxxxxx' Class:'xxxxxxxxx') will be closed
And then adjust the Windows & Dialogs Management by adding an allowed entry for that dialog (-->Access/Security-->Block system critical windows & dialog boxes-->Settings).
Further information about that feature:
- http://www.provisio.com/helpconsole/SiteKiosk%20Help/en-US/default.htm?windows___dialoge.htm
- http://www.provisio.com/helpconsole/SiteKiosk%20Help/en-US/default.htm?handling_of_windows.htm

If there is not a notification and if it “only” happens in Auto Start mode you may need to check which access rights are necessary for the McAfee process to start and adjust the access rights of the SiteKiosk user accordingly with using the System-Security-Manager.
My Account
Login
Language (Tickets):