Endpoint Protector Notifier service is not running after EPP client installation\update

Products Endpoint Protector Ideas
,
1

What is a one sentence summary of your feature request?

Adjust the behavior of the Endpoint Protector Notifier after EPP client installation\update

Please describe your idea in detail. What is your problem, why do you feel this idea is the best solution, etc.

Hi Everyone!

We would like to share the feedback regarding the Endpoint Protector Notifier behavior on the latest EPP client for Windows (6.2.5.3) and Linux (2.4.5.1):
After a fresh install or update from a previous version, the Endpoint Protector Notifier is not launching automatically.
It means that after the EPP client updated, the EPP tray icon is missing, and no notification from the EPP appears after a file transfer block.
If restart the service manually, the EPP notifier is enabled and works as expected; PC reboots help as well.
We also know that a PC reboot after installing\uninstalling EPP client is recommended, but in a large environment it cannot always be done, and moreover, it is inconvenient in most cases.
In the previous EPP client versions, the issue with the EPP notifier was not observing.
We were able to reproduce this issue after the manual EPP client installation and also after installation via PuppetManager.

Our suggestion in this feature request is to adjust the EPP client so the EPP notifier service will start automatically after every client update\install to prevent the inconveniences.
We are absolutely certain that making EPP client installation\update independent from the PC reboot will make Endpoint Protector much more convenient to use, especially in large environments.

How do you currently solve the challenges you have by not having this feature?

Only a manual EPP notifier service restart or PC reboot helps.

1 Like
2

Hi Danylo,

Thank you for your request. I can confirm that the behavior you’re asking about - EPP Notifier starting automatically - is indeed our expected behavior, with no need for manual service start or computer reboot.
However, IT best practices still recommend restarting the system for various reasons, such as reloading drivers or restarting services, especially on busy machines. This is often a foundational step in troubleshooting, ensuring the system behaves consistently before escalating any issues. An exception in our case relates to the print browser plugin, which requires a “fresh web browser start” after deployment or upgrade, as browser instances may remain running in the background. Therefore, a computer restart can sometimes be the simplest option.

For your situation, I suggest registering a Netwrix support ticket. If possible, set EPP to debug mode on EPP Client to be upgraded, to collect more logs.
Additionally is worth to check if any third-party applications, such as AV/EDR solutions, might be blocking the service startup. Please refer to the relevant User Manual chapter for further guidance.

Best regards, Krzysiek