Tyler Reilly 0 Posted May 27, 2018 Share Posted May 27, 2018 (edited) One of our clients is having a reoccurring but infrequent issue of ESET displaying the following error: "Failed to rename file" The following has been done so far: ESET products removed with uninstall tool and reinstalled ESET cache settings cleared Repair of ESET installation Procmon log collection – Error did not appear during log capture Windows Indexing Exception added The error looks to be infrequent and only show every few weeks at random, we initially thought this might be caused by an application that the client uses however they do not wish to add the application or its installation directory to exclusions. Is anyone able to confirm the following: Have you seen this error anywhere else and what was the fix for the error? Is there any way of supressing the error without disabling other alerts. Is there any native logging in ESET that would show what the cause of this error is. Edited May 27, 2018 by Tyler Reilly Adjust wording Link to comment Share on other sites More sharing options...
ESET Moderators Peter Randziak 1,168 Posted June 12, 2018 ESET Moderators Share Posted June 12, 2018 (edited) Hello @Tyler Reilly , we noticed this error as well, usually it happens when Windows indexing service touches our files during the update process, which does not happen on each update, but just on some of them. This issues is addressed in new builds 11.2.15.0+ (not yet publicly available) Edit: A colleague told me, that you are a business user, what I didn't realize, sorry for that. I will try to update this thread, when I will find out the version of EES where, it should be fixed. The easiest workaround is probably to exclude ESET folders from indexing, or just to wait for the service release. Regards, P.R. Edited June 13, 2018 by Peter Randziak Business user Link to comment Share on other sites More sharing options...
Recommended Posts