My laptop is running 24/7, and while asleep, I got Microsoft Defender update, and just seeing just the usual:
I refer to the following post, made October 15, by @wat0114...
Webroot glory days, no longer ...it would seem.
My first OSArmor event logged:
Date/Time: 21/10/2020 11:31:45 PM
Went all the way, testing that is...
I first reported a CPU resource issue for "SecureAge UniversalAV Service" with my post back in Feb 22, 2018
Finally, more than 2.5 years later...
I refer to an earlier [page 13] post ...And, your reply here
I just got another Alert, but this time for a different path, i.e....
I have said before that you are the Wise One ...
I am just curious. Are you saying, that I can install the ISO, and then delete it [without the need to create installation media] ?
I don't see point of doing that, since it would probably in the order of 4 GB's
From that link, that you posted:
Create Windows 10 installation media
If I went that route, I would most probably bork my...
Since, I got this Surface Book 1 laptop, I have never used an ISO file, just the [old] Windows Updates route. :D
So, just before next month's Patch Tuesday, I will get the updates for October...:cool:;) Pays to wait, methinks.
Thanks, but I am still on Build 1909. :)
Edit: I see that we just cross-posted. ;)
Edit: Also, a few hours before, @Triple Helix , if you look carefully at my screenshot of VS logs that I posted, you will see that...
I tried to create a [new] topic at Voodooforums, about this file Local Security Authority Process, after Glasswire alerted that it had updated to...
Just updated: v22.214.171.1243
I purchased, but I might not want to install this straightaway.
However, the clock is ticking, and it says [automatic] renewal is due on 11...
Thank you. :) I was annoyed when earlier it downloaded Whiteboard, and Glasswire showed that an outward bound connection was made.
I took control and now I know what is in this folder, and the size, of it.
Just like the first time that I ran this, SecureAplus popped:
Anyhow, this is what I get with build 1884:
Not for me to deduce. I just report what I see. :)
I forgot to advise that it popped for me the very first time, but I ignored it. Still, all is good, because I ignored it again with build 1883....
Just trying Build 1883, and note this difference:
Separate names with a comma.