Time zone settings

V 17.5.2303
Vista

Is it possible to change the time zone used in the Avast logs to my current (UK) time.
Today I booted up at 1200 hrs but the log shows 1100 hrs.
This makes it awkward when checking stuff.
If not, why not?
David

Not possible and not needed.
avast uses the time settings you have set on your system.

Not so Eddy
Here in UK we have ‘daylight saving’ and this varies the GMT by 1 hour.
My system is set to this latter.
I shut down every night and boot every day.

[2017-08-19 21:32:07.617] [info ]
[2017-08-20 11:02:18.771] [info ]

As you can see Avast log shows a start of 11:02:18

Win Event log shows Log Name: System
Source: EventLog
Date: 20/08/2017 12:01:58

I’m not entirely sure that it is avast that would set this time, but the Windows event log creation function.

Personally I keep my nose out of the Event logs, only ever venturing into them if I getting hard errors to the screen.

Are your avast logs showing the correct DTG ?
I have just updated this win10 avast free version to 17.5.2303 (I had been hanging back) and the actual avast log would appear to be using the correct DTG. This was based on around the time that I rebooted after the program update.

2017-08-20 17:15:39 AR2DEV: Stop 1 2017-08-20 17:15:39 AVAVER: 17.5.2303 AR2: 170808 defs: 17082000 2017-08-20 17:15:39 AR2CFG: 170623 2017-08-20 17:15:42 AR2DEV: Start 1 Driver: 170610 2017-08-20 17:16:41 AR2DEV: Stop 1 2017-08-20 17:17:11 AVAVER: 17.5.2303 AR2: 170808 defs: 17082000 2017-08-20 17:26:52 AR2CFG: 170623 2017-08-20 17:26:54 AR2DEV: Start 1 Driver: 170610

The avast log file is showing the correct time as DST (summertime) is +1.
At the time I write this, it is 22:19H at my place (Netherlands with DST)
So the real time would be 21:19H and that is what will be in the log files.

The Avast logs, Event & Update are using GMT.
UK time right now is BST = GMT+1 (https://greenwichmeantime.com/time-zone/europe/uk/time/)
My PC is using BST

Avast isn’t the only software that when installing takes your country and its standard zone.
Daylight Saving is a real pain in the neck and not relevant any more, it goes back a long time.

I got an error message yesterday when checking for update, something about not getting server.
Later I tried to check the logs, without thinking about zones, didn’t find anything.
Then realized about the -1 and still couldn’t find anything

No, avast is not the only software that shows this behavior.
I’ve seen it with multiple others as well.

I would have to decompile things and look at the source code to be sure (which I am not gonna do ofcourse), but I suspect it has to do with the way a application is requesting the time(zone) from Windows.

Just a simple example on what could be going on:

  • The bios/UEFI stores the time/date
  • Windows gets the time/date from there
  • Windows stores it a default time/date somewhere (or perhaps even in multiple places) *1
  • Windows stores somewhere else what timezone you have set/use and if there is DST or not. *2
    So if a application looks at *1 for the date/time it can be that it will get another date/time than when it looks at *2

As I said, I’m not sure but it seems to me something like this is going on.

About DST, sure it is old and thing have changed (a lot).
Strange thing is that there is no-one who really has calculated if it still is helping to safe energy these days.
I remember having two different prices for energy.
One was for the use between (iirc) 07:00 and 19:00
And the other was for the use between 19:00 and 07:00.
Well, the “night charge” is now only between 23:00 and 05:00
There are also a lot more electrical devices in a household nowadays and as many people are at work during the day and home at the evening/night, that also will influence the effectiveness of DST a lot.
Newer versions of old devices are using less power etc.
I would say it really is time for some scientists to have a good look at it and do the math for the different countries.

Hi Eddy,
The new bathroom is now finished and I have cleared up hence the delay.
I’m sure you are correct in every respect.

I have had troubles with Avast Pro since day 1, I should have tried first but was over confident from some years ago.
I have now resolved my issues by switching to ‘manual updates’.
I don’t actually know the cause/causes.
I have posted a couple of things on the forum, raised a ticket etc but, after all, I am on Vista so do not expect too much.
For all I know it may be IPv6/IPv4 & Terodo.
Avast is the 2nd AV with this issue and I know this from my tests with the first.
I’m fine for now
Thanks for your support
David

What is the address ?
I can use a good bath ;D

You’re welcome.