Since 6/25, BDA 2011 now starts scanning at 11:50AM instead of midnight.
The scheduler still shows the task is scheduled for midnight (12:00AM) but it starts at 11:50AM regardless.
I believe this has been caused by an automatic update that required rebooting.
This already happened to me mid April, also caused by an automatic update. I provided all the logs and screenshots by email as requested back then (Ticket ID:201104031003286) with never any answer about this issue.
Here's the summary and screenshot from the last mail:
- View Logs|Antivirus|On-demand Tasks: Typo in "Scan task finished successfuly"
- View Logs|Antivirus|On-demand Tasks|Double-click on a task|Task schedule: Typo, missing space after "scheduled for:"
- View Logs|Antivirus|On-demand Tasks|Double-click on a task|Task schedule: Wrong date/time format. It is using French format and French day names when the previous line "Date" is in the correct English-US locale. The only thing French in my system is the default keyboard layout, my location is US, time zone Pacific GMT-8, user locale and display language English-US, and everything was set this way at the time of BDA installation and scan task scheduling.
- View Logs|Antivirus|On-demand Tasks|Double-click on a task|Task schedule: Wrong scheduled time. The log says the next scheduled scan is in 7 hours instead of 24 (scan scheduled daily), plus the start time for the next scan task is actually using the minutes and seconds of the end time of the past task. Possibly linked to the above format issue.
- Random start time of the scheduled tasks: This happens every time a scheduled task is interrupted manually. BitDefender Antivirus will then try to re-run the task a few hours later, or shortly after a reboot. It's totally random and unexpected: If the task is stopped, not paused, then BitDefender should try to run it at next scheduled time, not out of schedule.
- If the scan is not stopped manually, then the next scan starts on schedule.
I'll uninstall and reinstall again since that got rid of the schedule corruption bug the last time, but there is definitely something wrong with the update process that you might want to look at, since this has now happened repeatedly with exactly the same symptoms.
