MikeRigsby

Members
  • Content count

    4
  • Joined

  • Last visited

About MikeRigsby

  • Rank
    N/A

Recent Profile Visitors

39 profile views
  1. "Failed to rename file"...?

    I don't know if this will apply to anyone else, but I re-enabled the Windows Search service on the one system that was throwing this error the most, since in my case it did seem like Indexing was causing this. I then upgraded it from 6.6.2052.0 to 6.6.2064.0 and this error hasn't come back. Whatever was causing the file conflict may have been resolved in the new update by the looks of it.
  2. "Failed to rename file"...?

    Makes sense. Unfortunately "Failed to rename file" is probably just a generic error that's caused by pretty much any service or activity on the client PC that causes a file access conflict with the ESET update, at the time it was attempting to automatically update. In my specific case it appears to be the Windows Search service, but most likely there's plenty of other activities that could cause it.
  3. "Failed to rename file"...?

    After a few weeks of not getting this error on the two PCs that I had disabled the Windows Search Service on I decided to re-enable the service again to make sure it was related. Very next morning after turning the Windows Search service back on, I got the error again on those PCs so this issue is most definitely related to a conflict with Windows Indexing.
  4. "Failed to rename file"...?

    A couple weeks ago I disabled the Windows Search service on two of the PCs that this error was the most frequent on and the error hasn't happened since. I'm assuming that the Windows file Indexing is clashing with the ESET update service. I don't really consider this a 'fix' because disabling a service that is fairly important to many of my users isn't a solution.