DavidR
4
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