Maybe I could believe that if the software reports were only for machines other than my own: but no-one else logs on to this PC. The scans can be actively run while I'm logged on (as they were this morning) and still show deviant results. The PC is often left running 24*7 with an active login (for remote work from home), so some of the automatic scans are at odd times in the morning when no-one else would be near the machine.
In any event, the only other user profile on the PC belongs to the installation account, last used in December of last year. Sure, the security isn't 100% foolproof, but it's unlikely that anyone else in the organisation would have means, motive and opportunity to perform such a hidden login.
I'll grant that the exceptions do seem to be for user-specific software, but it's not quite as simple as someone else being logged in - and, if I recall correctly, it's only started happening since a recent Lansweeper update (sorry, the old database got junked in December when we migrated to a new environment, so I cannot prove this). We will need to try a few experiments with software explicitly installed for a single user, see how that affects things.