lllusion 0 Posted July 24 Share Posted July 24 This makes no sense to me. The last successful update was two hours ago. What is going on? Quote Link to comment Share on other sites More sharing options...
Administrators Marcos 5,306 Posted July 24 Administrators Share Posted July 24 The only explanation that occurs me is that the system date or time has changed after the last update. If that's not the case and the issue doesn't resolve automatically soon, please raise a support ticket. Quote Link to comment Share on other sites More sharing options...
lllusion 0 Posted July 24 Author Share Posted July 24 (edited) System date and time have not changed. I'll restart and see what happens. Update: Restarting resolved the issue. Edited July 24 by lllusion Quote Link to comment Share on other sites More sharing options...
GolfPilot 1 Posted July 31 Share Posted July 31 I've just had the same issue. Last update at around 05:30 this morning, now telling me the detection engine is out of date and has not been updated for some time! I've clicked the 'Check for update' and I just get a spinning wheel as if my device can't connect to ESET. The internet connection is fine, and the date and time hasn't been changed. The only thing that's changed is yesterday I updated my mac from 14.5 to 14.6 Sonoma. GP Quote Link to comment Share on other sites More sharing options...
Administrators Marcos 5,306 Posted July 31 Administrators Share Posted July 31 Please raise a support ticket as further logs will be needed. The determination whether the engine is outdated is done by comparing the system date and time with the timestamp of the installed engine. Quote Link to comment Share on other sites More sharing options...
AnthonyQ 51 Posted August 13 Share Posted August 13 Same here. I've been encountering this issue occasionally recently. When the update problem occurs, I'm unable to perform manual file scans. A simple reboot can help resolve it. Quote Link to comment Share on other sites More sharing options...
Administrators Marcos 5,306 Posted August 13 Administrators Share Posted August 13 7 hours ago, AnthonyQ said: I've been encountering this issue occasionally recently. When the update problem occurs, I'm unable to perform manual file scans. If you're unable to run a scan there's probably something wrong with the ESET service. Please raise a support ticket for troubleshooting. Quote Link to comment Share on other sites More sharing options...
lllusion 0 Posted Saturday at 05:07 PM Author Share Posted Saturday at 05:07 PM On 7/31/2024 at 2:51 AM, Marcos said: Please raise a support ticket as further logs will be needed. The determination whether the engine is outdated is done by comparing the system date and time with the timestamp of the installed engine. I raised a support ticket (#00835901) and was asked to collect logs. Unfortunately, the Log Collector requires performing the steps that cause the issue. This is a seemingly random issue that I cannot replicate on demand. I can only resolve it by restarting the system. Quote Link to comment Share on other sites More sharing options...
Administrators Marcos 5,306 Posted Saturday at 05:50 PM Administrators Share Posted Saturday at 05:50 PM Does the last check time not update if you click Check for update? Quote Link to comment Share on other sites More sharing options...
lllusion 0 Posted Saturday at 06:47 PM Author Share Posted Saturday at 06:47 PM 57 minutes ago, Marcos said: Does the last check time not update if you click Check for update? No Quote Link to comment Share on other sites More sharing options...
Eckles 1 Posted Saturday at 09:45 PM Share Posted Saturday at 09:45 PM I can confirm I have the same issue... been happening for a few weeks and can only be resolved with a restart. No time / date changes on machine..... The timestamp for the last checked for update is correct but it still saying the engine is out of date... Current Version 7.5.74.0 AnthonyQ 1 Quote Link to comment Share on other sites More sharing options...
Administrators Marcos 5,306 Posted Sunday at 12:14 PM Administrators Share Posted Sunday at 12:14 PM Is somebody experiencing the issue with macOS 15 (Sequoia)? @GolfPilot mentioned that he has v14.6 (Sonoma). Quote Link to comment Share on other sites More sharing options...
lllusion 0 Posted Sunday at 12:16 PM Author Share Posted Sunday at 12:16 PM The issue first occurred with macOS 14. It has reoccurred with macOS 15. Quote Link to comment Share on other sites More sharing options...
palo 0 Posted Monday at 12:24 PM Share Posted Monday at 12:24 PM After upgrade to MacOS 15 occurs regularly. Temporary fix is to restart computer, after that it works few days and reoccurs again. Version 7.5.74.0 MacOS 15.0.1 Quote Link to comment Share on other sites More sharing options...
AnthonyQ 51 Posted Monday at 11:38 PM Share Posted Monday at 11:38 PM On 10/13/2024 at 8:14 PM, Marcos said: Is somebody experiencing the issue with macOS 15 (Sequoia)? @GolfPilot mentioned that he has v14.6 (Sonoma). Yes, I can confirm that this issue occurs on macOS 15, typically when the Mac restarts after entering sleep mode. The only solution for users is to restart the Mac. Quote Link to comment Share on other sites More sharing options...
blitzd 0 Posted Tuesday at 03:29 PM Share Posted Tuesday at 03:29 PM On 10/13/2024 at 8:14 AM, Marcos said: Is somebody experiencing the issue with macOS 15 (Sequoia)? @GolfPilot mentioned that he has v14.6 (Sonoma). Started running into this today, I am on Sequoia 15.0.1: Quote Link to comment Share on other sites More sharing options...
lllusion 0 Posted Tuesday at 04:25 PM Author Share Posted Tuesday at 04:25 PM It happened again this morning to me. Quote Link to comment Share on other sites More sharing options...
steand 0 Posted Wednesday at 07:33 AM Share Posted Wednesday at 07:33 AM (edited) Same here. I started facing this issue after updating to macOS Sequoia. Is there any workaround available without having to restart the system? Edited Wednesday at 07:36 AM by steand Quote Link to comment Share on other sites More sharing options...
pygocentrus 1 Posted Wednesday at 05:51 PM Share Posted Wednesday at 05:51 PM (edited) your case is similar to mine ! You, out of date, mine, obsolete... with the last detection engine available !! Edited Wednesday at 05:53 PM by pygocentrus Quote Link to comment Share on other sites More sharing options...
AnthonyQ 51 Posted 15 hours ago Share Posted 15 hours ago Happened once again... Very annoying, any plan to fix it? @Marcos Quote Link to comment Share on other sites More sharing options...
lllusion 0 Posted 4 hours ago Author Share Posted 4 hours ago Once again, I don't believe the issue is related to macOS 15. I first had the issue with macOS 14. (Notice the date of my original post.) Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.