Ah, I see. Well, I'm glad I accidentally installed it on my system so I could tell you it works. :)
When I started to check out Avast, I was quite surprised at how much improvement has happened in the years since I used it on my machines.
I'm going to check it out further now that I see the improvements.
Has anyone found with this build an issue after logging into the system of a blank screen with no desktop interface? First I've experienced in any insider build. After logging in, black screen with cursor -- only options are ctrl-alt-del with logout / switch user to get back to login prompt. Rolling back to previous build seems to be the only way around this.
Hello, citrixscu. Welcome to Windows TenForums.
Yes, someone mentioned that. If I remember correctly it was a video driver. We'd have to read back to find it. Not even sure if the member ever got it resolved. And of course in that predicament there's hardly a way to resolve unless you inject a different driver in the ISO. If, of course, that is the issue.
Thanks, Tony. I'm going to give it one more shot and then just roll back if things don't resolve. I suspected it may be an nvidia driver issue. Oddly enough, even booting to safe mode does causes the desktop to hang as well.
Hmm. I guess someone finally made up their mind: Defender antimalware client update Solved - Windows 10 Forums
Use what you may, but roll the crapps dice one more time. You may get lucky. Some may think because it installs that it’s working correctly. Not necessarily so. And who is to think they are above the warning or statements of any Avast forum members? If anyone should know, they would. And has anyone contacted their AV concerning IPs?
I know WD has more of odds that it’s working properly on my IP system, for it’s tested by the OS creator itself. Also runs at kernel level. Why? Because MS has the source code.
A slew of tools there one can use as well.Quick scan versus full scan
Quick scan looks at all the locations where there could be malware registered to start with the system, such as registry keys and known Windows startup folders.
Combined with always-on real-time protection capability - which reviews files when they are opened and closed, and whenever a user navigates to a folder - a quick scan helps provide strong coverage both for malware that starts with the system and kernel-level malware.
Also, some are delusional to think there is a perfect AV. There's no such animal. Machines with other AVs get infected as well. Thing is, if the new threat isn't in the definition file, then a machine will get infected. That's the crux of them all. If anything, manually update morning, noon, and night. Either that or configure it to update more often.
Also, a browser and real-time must keep up with malicious sites and threats as well. That's the first line of defense. There are more than "those" sites out there. And, of course, using good sense is most important. I know I'm preaching to the choir, but we all need to be reminded.
More reading about AV and IPs. A little dated, but the warnings still apply: Anti-Virus for Windows 10 Technical Preview - Microsoft Community
In addition, after 4 days, even with a reboot just now, it's completely convinced that it's using about 30% CPU for itself, when it's not. And the Details tab doesn't show any CPU usage for anything, so it's really messed up. Since the icon is permanently bluer than it should be because of the false CPU usage, which is completely misleading, I'm not going to use it anymore in this build. I could take the 100MB thing, but I mainly use it for CPU usage alerting.
If anyone hasn't heard of Process Hacker, check it out. It can do some amazing things.
Quote
:)
