cyberhash

@TomFace Likewise mate , always nice to keep in touch The reason i was asking about passwords on log on is that i have observed that the splash screen wont appear when you allow windows to sit on the lock screen "awaiting password" for any more than a few seconds(5-10 ish). I assume that it's because ESSP is loading prior to even reaching the lock screen (to protect from boot, as you would expect) , and the splash screen is loading (behind the lock screen) and why "in my case" that if i don't input my password when i first reach the lock screen (pretty much immediately) that i don't get to see it. I can replicate this either way 100% each time, put password in quickly and i see the splash screen or have a delay when inputting password on the lock screen and i don't get to see it. It does however load without issue and sits loaded in the system tray properly (as expected). Neither do i have any issues with it registering with windows security centre or it remembering size or location of the GUI position on my desktop (or opening closing). I'm on windows 10 x64 (for reference). What you and @SCR have happening is a different kettle of fish entirely , especially if it's affecting it loading to the system tray and not registering with windows security centre.

@TomFaceIf you have to use a password to log into windows (depending on how quick you type) , the splash screen can load and disappear before you even hit the desktop. @TomFace/ @SCR , did you both do an in product upgrade to v12

German cloud host "Hetzner" , maybe used for updates or livegrid ?

The scare stories about windows 10 are exaggerated. It's a far more secure version of the o/s than previous versions. Like every release of windows, the driver support was poor at the start but its been out so long now that these issues are all overcome. The installer in the new builds now gives you the option to disable all the things that people complained about on it's release (telemetry) . It's been a great o/s from my point of view and never had any issues whatsoever

The log files should show different types of events (for each category) , is this what you mean ??

Funnily enough, i can run any second opinion scanners or firewalls without any trouble whatsoever and without exclusions. Only a second realtime scanner will cause problems. Nothing new and was even a issue back on windows 95 lol .

Why would you need to add exclusions if the application(or associated files)are not any type of "threat" ?? If anything being detected is false then it only needs reported and if its found to be clean then its detection is reversed.

Running a scan only shows the same animation "showing that something is happening" on the system tray icon for me, but if you hover over it the text clearly states a scan is running and not an update.

Yes the user base that needed all the features of a dedicated software firewall was very slim and therefore not profitable.

Many many years back (prior to eset suites being available) i always used a 3rd party firewall along side NOD32 as there was never any compatibility issues that other vendors suffered from. Like @itman has mentioned above. Because these 3rd party firewalls are dedicated applications they will always be more flexibe when it comes to ease of use (for more complex settings). Other vendors that offer security suites have either similar or worse methods of configuration when you get to the firewall. Maybe using outpost along with NOD32 might be more to your liking .

Hi @punta30 Im guessing that this was also an issue prior to having your ESET product installed ? edevmon.sys wont be the culprit , but at first glance it will appear to be the case as its name appears there. Have you checked the MSI website for the "Intel Chipset & Intel Management Engine " driver updates for your specific motherboard. Id put money on one of those 2 being the culprit

Hi @LB-ID, When you had the black screen on boot , were you able to bring up task manager by pressing ctrl-alt-del and selecting task manager to see if anything was consuming large amounts of cpu cycles , on either the "details" or "processes" tab within task manager ?? You could also check this when your NOD32 is "not" installed and see if there is anything that looks suspicious beforehand. If it's something thats just happened in the past few months then it would suggest that there is something else causing the issue and not your Antivirus , even although removing it seems to remedy the problem. A (bad)device driver update during windows update could trigger such a behaviour, and would fit most with your timeline of it "worked then suddenly didn't".

https://www.eset.com/int/beta/