Panayiotis Zezos

Hello to all community here. We have a policy in ESET Protect Cloud to disable "rundll32.exe". Users are complaining because are getting several times in a day the notification that the specific executable file tried to open but its blocked due to ESET Policies. We disabled the notify button on the policy but users still get it. Can anyone please assist what is the actual case here? Rule is on prepend fyi. Thank you, Panayiotis

Greetings to everyone, and I appreciate your prompt response. We have made an attempt to execute the MSI package using the aforementioned command, but it yielded no results. Within the Application logs, we encountered two entries pertaining to the issue: Initiating a Windows Installer Transaction: \\this_is_my_fs\GoogleDrive\googledrive.msi Client Process ID: 11960 Concluding a Windows Installer transaction: \\this_is_my_fs\GoogleDrive\googledrive.msi Client Process ID: 11960 Both entries were recorded simultaneously at 11:08:50.

Greetings, We would like to inform that we are currently utilizing ESET Protect Cloud as our chosen security platform. As part of our operational requirements, it has become necessary to deploy Google Drive to our Windows agents. Upon conducting extensive research, we discovered that the deployment necessitates the utilization of a .msi file format. To achieve this, we employed the services of MSI Wrapper, a freely available tool, to convert the existing .exe file into a suitable .msi format. Furthermore, it is important to note that we refrained from incorporating any additional parameters during the conversion process. Subsequently, we proceeded to transfer the resulting msi file to a designated folder on our file server. It is worth mentioning that this particular folder does not require any user authentication for accessibility. To facilitate the installation of the aforementioned file on Windows devices, a task has been generated within the ESET Console, utilizing the following configuration: file://\this_is_my_fs\GoogleDrive\googledrive.msi Regrettably, we have encountered an obstacle, as the task is unable to run on the agents. Furthermore, we are currently unable to proceed with the remote deployment. Thank you for your attention on this matter.