Hello @InvisibleMan, Avast path is: c:\ProgramData\AVAST Software\Persistent Data\Avast\Logs\
And a blocked popup is not a reason for reboot or a trigger for overseer to ask for a repair. Blocking Internet access to Avast UI could not cause that neither.
Btw, we did some changes to overseer, is the restart still triggered in you case?
Petr
Ah, that's it! In this directory I found different log files than in the one you gave me previously.
And one file was last updated just recently (
2022-05-23), when I had to restart my computer for the very last time, before I disabled Overseer.
It's called
AvEmUpdate.logHere are the last portion of the log on "pastebin",
which inludes ALL those reboots it caused me, related to this update file
C:\Program Files\Avast Software\Avast\setup\auup697.exe
Last log entries: https://pastebin.com/brmtVgrmIt looks like it tried to apply the same exact update
http://uupdate.avast.com/files/emupdate/avast_21_r8_697.cab
for three times and all three times the application requested me to reboot my computer (and re-created an avast shortcut on my desktop which I didn't need).
Hopefully that should help you to identify what was going on.
Btw, we did some changes to overseer, is the restart still triggered in you case?
I didn't risk to enable it just yet. But if the relevant logs you helped me to find above will confirm that the changes you made to overseer should stop it from applying the same update more than one time within a few days, please let me know, so I can enable Overseer task back to test it.
P.S. Maybe it's not even overseer issue? Maybe it's an Emergency update issue? The thing is, I disabeld BOTH tasks in Task Scheduler, including Overseer and Emergency update (just in case) to stop my avast from requesting those reboots.