Shipon_BD 0 Posted April 22 Share Posted April 22 Once ESET Endpoint installs we’re facing an issue with all the Desktop/Laptop, the C drive is getting out of space. After checking we’ve seen that the Installer folder contains a huge amount of *tmp data and took maximum space(more than 80GB). Even the ESET antivirus is in protected status. Maybe there’s something wrong with the antivirus. Please see the attached images for better understanding. Link to comment Share on other sites More sharing options...
Administrators Marcos 5,238 Posted April 22 Administrators Share Posted April 22 From the screenshots it is not clear what are the names of the tmp files so we can't tell if they were generated by ESET or not. Please provide some name of the tmp files. ESET may created temporary files in the user or system temporary folders, not in the Installers folder. There should be just the msi installer that was used for installation of ESET. Link to comment Share on other sites More sharing options...
Shipon_BD 0 Posted April 22 Author Share Posted April 22 Please see the attach file Link to comment Share on other sites More sharing options...
Administrators Marcos 5,238 Posted April 22 Administrators Share Posted April 22 The names suggest that the files were created by Windows Installer. Is there any reason why you suspect them to be related to ESET? Link to comment Share on other sites More sharing options...
Shipon_BD 0 Posted April 22 Author Share Posted April 22 After installing ESET Endpoint that can happen...........automatically temp is generated & If uninstall ESET it stops generating temp. Link to comment Share on other sites More sharing options...
Administrators Marcos 5,238 Posted April 22 Administrators Share Posted April 22 It is for sure that the files are created by Windows Installer. Maybe ESET installation is being pushed to the machine in certain intervals. Please provide a Procmon boot log. Stop logging after a reboot only after the temp files have been created. Do not keep Procmon logging for a longer time than a few minutes. Link to comment Share on other sites More sharing options...
Shipon_BD 0 Posted April 22 Author Share Posted April 22 For this reason, seems ESET generated this temp........see the screenshot Link to comment Share on other sites More sharing options...
Administrators Marcos 5,238 Posted April 22 Administrators Share Posted April 22 It confirms my suspicion that something is continually pushing the ESET installer on the clients. Could you check in the ESET PROTECT console if you have a software install task assigned to some of the dynamic groups? Link to comment Share on other sites More sharing options...
Solution Shipon_BD 0 Posted May 19 Author Solution Share Posted May 19 (edited) Thanks, Marcos for helping resolve this issue............. It's resolved by removing the cmd task to a dynamic group. Edited May 19 by Shipon_BD Link to comment Share on other sites More sharing options...
Recommended Posts