DavidR
2
The aswAR range of file names relate to the avast anti-rootkit scan (presumably the aswAr.run would run the anti-rootkit scan), so when it is checking for rootkits it has to work at a low level and may well be hidden. This is the sort of thing you get when digging into your system with other security software.
The fact that it hasn’t happened before could either be coincidence, an avast AR scan running when you checked or changes in the scan method of the 3rd party security scan.
I would leave the aswAr.run file alone.