write access denied: problem?

[REDACTED]

Aloha,

I noticed that my selfdef.log is made up entirely of this:

2/9/2017 1:28:05 AM   Write access to file \Device\HarddiskVolume4\ProgramData\AVAST Software\Avast denied. [PID 4]
2/9/2017 1:28:16 AM   Write access to file \Device\HarddiskVolume4\ProgramData\AVAST Software\Avast denied. [PID 4]
2/9/2017 1:28:23 AM   Write access to file \Device\HarddiskVolume4\ProgramData\AVAST Software\Avast denied. [PID 4]
2/9/2017 1:28:24 AM   Write access to file \Device\HarddiskVolume4\ProgramData\AVAST Software\Avast denied. [PID 4]
2/9/2017 1:28:45 AM   Write access to file \Device\HarddiskVolume4\ProgramData\AVAST Software\Avast denied. [PID 4]
2/9/2017 1:28:54 AM   Write access to file \Device\HarddiskVolume4\ProgramData\AVAST Software\Avast denied. [PID 4]
2/9/2017 1:29:00 AM   Write access to file \Device\HarddiskVolume4\ProgramData\AVAST Software\Avast denied. [PID 4]
2/9/2017 1:29:19 AM   Write access to file \Device\HarddiskVolume4\ProgramData\AVAST Software\Avast denied. [PID 4]
2/9/2017 1:29:22 AM   Write access to file \Device\HarddiskVolume4\ProgramData\AVAST Software\Avast denied. [PID 4]
2/9/2017 1:29:30 AM   Write access to file \Device\HarddiskVolume4\ProgramData\AVAST Software\Avast denied. [PID 4]

But thousands of them, going back to when I installed Avast.  I looked up PID 4 in the Task Manager. Name: "System" and description: "NT Kernel & System"

Seems like the OS is trying to access the Avast directory a couple of times a minute and gets denied every time. Is this normal? A problem?

Also event_manger.log is made up entirely of:

[2017-02-09 00:22:08.242] [info   ] [burger     ] [ 3996: 4000] Storage path was not set so neither stored FFL key nor stored events are read.
[2017-02-09 00:22:08.258] [info   ] [burger     ] [ 3996: 4784] Storage path was not set so loading of stored events is skipped.
[2017-02-09 00:22:08.820] [info   ] [burger     ] [ 3996: 4784] Storage path is not set so storing of FFL key is skipped.
[2017-02-09 00:22:28.277] [info   ] [burger     ] [ 4824: 4832] Storage path was not set so neither stored FFL key nor stored events are read.
[2017-02-09 00:22:28.277] [info   ] [burger     ] [ 4824: 3792] Storage path was not set so loading of stored events is skipped.
[2017-02-09 00:22:40.826] [info   ] [burger     ] [ 4824: 3792] Storage path is not set so storing of FFL key is skipped.
[2017-02-09 04:23:05.338] [info   ] [burger     ] [ 4688:  340] Storage path was not set so neither stored FFL key nor stored events are read.
[2017-02-09 04:23:05.345] [info   ] [burger     ] [ 4688: 7340] Storage path was not set so loading of stored events is skipped.
[2017-02-09 04:23:05.674] [info   ] [burger     ] [ 4688: 7340] Storage path is not set so storing of FFL key is skipped.
[2017-02-09 08:23:11.080] [info   ] [burger     ] [ 9632: 7416] Storage path was not set so neither stored FFL key nor stored events are read.
[2017-02-09 08:23:11.086] [info   ] [burger     ] [ 9632:11212] Storage path was not set so loading of stored events is skipped.
[2017-02-09 08:23:11.561] [info   ] [burger     ] [ 9632:11212] Storage path is not set so storing of FFL key is skipped.

I'm also wondering about that.

Thanks for your collective thoughts.

[REDACTED]

Aloha,
[...]
Also event_manger.log is made up entirely of:

[2017-02-09 00:22:08.242] [info   ] [burger     ] [ 3996: 4000] Storage path was not set so neither stored FFL key nor stored events are read.
[2017-02-09 00:22:08.258] [info   ] [burger     ] [ 3996: 4784] Storage path was not set so loading of stored events is skipped.
[2017-02-09 00:22:08.820] [info   ] [burger     ] [ 3996: 4784] Storage path is not set so storing of FFL key is skipped.
[...]
I'm also wondering about that.

Thanks for your collective thoughts.

I have the same thing dating all the way back to 2016-04-10
There was a debugging entry in the logfile that displayed some hardware info. That extra info was included until 2016-07-01 at which time the hardware info ceased getting written into the logfile. Was an update from AVast installed around then???

Since there are just a few files that trigger this event (in my case, I'd be more than happy  to find the offenders, clean them up, and go on my merry way if I only knew why and how). Hoping to see some action on this from AVast Tech Support . It generally appears benign, but you never really know unless a technically knowledgeable person does the evaluation.

[bob3160]

Reported to Avast.