Avast WEBforum

Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: twoshoes2 on February 08, 2017, 04:15:59 PM

Title: scheduled scan problem in 17.1.2286 (buils 17.1.3394.0)
Post by: twoshoes2 on February 08, 2017, 04:15:59 PM

I set a full system scan for today (Wednesday) at 13 00 hours.  Under the Run full Virus Scan there is  now a message that says: "run your scan weekly on at Invalid date".  I have tried changing the day and time and still get this message.  Do I also need to do something else to correct this?

Title: Re: scheduled scan problem in 17.1.2286 (buils 17.1.3394.0)
Post by: RejZoR on February 08, 2017, 04:21:56 PM

I can confirm this. In fact, clock is entirely broken. I've entered 1:00 to see if it's AM/PM that's borked up. And for 1:00 it shows 23:00. It just doesn't make sense... I'll forward this to devs. Thx for reporting.

Title: Re: scheduled scan problem in 17.1.2286 (buils 17.1.3394.0)
Post by: DavidR on February 08, 2017, 04:23:18 PM

It could be something as simple as the date time format of your computer and or avast, mm/dd/yyyy (Month/Day/Year) or dd/mm/yyyy (Day/Month/Year).

Also check your system date and ensure that is correct.

EDIT: as RejZoR's post, looks like the above isn't an issue.

Title: Re: scheduled scan problem in 17.1.2286 (buils 17.1.3394.0)
Post by: RejZoR on February 08, 2017, 04:25:25 PM

It's the same on my system and all my time/date parameters are correct.

Title: Re: scheduled scan problem in 17.1.2286 (buils 17.1.3394.0)
Post by: DavidR on February 08, 2017, 04:27:06 PM

Quote from: RejZoR on February 08, 2017, 04:25:25 PM

It's the same on my system and all my time/date parameters are correct.

That was my thought after seeing your post.

Title: Re: scheduled scan problem in 17.1.2286 (buils 17.1.3394.0)
Post by: lagin on February 08, 2017, 04:29:52 PM

It is reported. Thanks.

Title: Re: scheduled scan problem in 17.1.2286 (buils 17.1.3394.0)
Post by: twoshoes2 on February 08, 2017, 05:00:41 PM

Thanks All, hopefully a fix is coming soon.