AndrewC

It doesn't affect any functionality, it's just a minor bug in internal reporting. However, you can suppress the notification by disabling it in the application statuses setup:

The first check will suppress it on the client while the other (Send) will suppress it in the ESET PROTECT console.

Thanks, pre-release channel did it. 🙂 Trouble with stateless VDI for this, a reboot only temporarily clears the notification since reboots also cause the update to revert back to the template state. Got to make changes to the template VM for them to stick.

Right now you can force module update by switching to the pre-release update channel in the update setup or wait a few more days until all computers receive it automatically from the standard release update channel.
On clients where the driver / module has been updated, the notification should be cleared after a computer restart.

It's caused by a bug in an internal notification system triggered by installation of a new version of the eelam driver by a module that is being gradually released in batches. The bug in the internal notification system will be fixed in the next Endpoint v8. Rebooting the machine should clear the notification.