StepEd

Hi @Marcos, Well I've just uninstalled and re-installed this morning. It works - but then again, so it should, one would hope (because otherwise that would be a separate issue). I note it's the same version as what I had previously (v14.0.22.0), which I think NOD32 had just upgraded itself to when problems begain (refer to the error messages in my first post). I think the real test is whether it will apply the next update successfully when it comes around. If the root cause from the dumps I provided hasn't been determined, then who can say, until it comes around. From what I've read about OOBE, what it is, how to invoke/configure it etc, I'm fairly sure that won't be it. Did tech support make any progress on the supplied ekrn dump and Log Collector logs? Cheers

@Marcos, sorry for the delay. I have just PM'd you a GDrive link to my "6.xml" file. Regards, Stephen

shockpoint, are you therefore saying that you get the same persistent errors reported and request to reboot which doesn't clear, except on a) ESET Internet Security and b) on 14.0.21.0 ? If so, then may or may not be the same issue. Might be worth submitting dumps as per Marcos' post above, given some of the differences, if I'm interpreting correctly. FYI, I did submit dumps via PM to him just after my post above indicating I had issues doing so.

Thankyou Marcus for your Reply. Unfortunately though, I can't do that. When I go to ESET NOD32 Antivirus > Setup > Advanced Setup > Diagnostics , I selected Dump type = Full (I wasn't sure how verbose you needed it to be), then clicked "Create" (diagnostic dump). It seemed to chug away for a while, that bit seemed fine. But I can't locate the dump. There is an "Open" link beside "Open diagnostics folder". Instead of going to the diagnostics path, it simply goes to "Computer" (ie: where you see your local C drive etc). So I tried to navigate to the path listed above it, manually in Windows Explorer, being C:\ProgramData\ESET\ESET Security\Diagnostics . I can navigate to the "ESET Security" folder and I can see the Diagnostics folder in the list, but double-clicking it to open it does nothing, no error or anything, just ignores me. It's weird. Properties on the Diagnostics folder shows it's 0 bytes. Edit : I've made a breakthrough. I tried copying the Diagnostics folder to elsewhere and got prompted to elevate access. Clicking Yes allowed the copy to proceed. Don't know why it didn't prompt me before. However you may want to check that the "Open diagnostics folder" function witin NOD32 isn't broken / bug fix / etc.

Having the same issue here. Currently on v14.0.22.0 . Which means it auto-updated some time this week (sorry, didn't notice). ESET Antivirus Home screen has two red messages (interestingly the red number circle 'badge' beside "Home" has "3" but only two action items are listed) : 1) Computer restart required - ESET NOD32 Antivirus has been updated to a more recent version. In order to ensure maxium protection, computer restart is required for all changes to take effect <Restart computer blue link> 2) Real-time file system protection is non-functional - This functionality could not be started and your computer is not protected against some types of threats. Setup has one red message because of the real-time file system protection, its switch is off and red colour and cannot be switched on. But inside its settings, it is enabled. The restart computer link works. I've tried twice now, with sufficient time between to let it do whatever it needs to do. In fact, the reboot seems to be a full reboot, not the typical fast Win 10 restore-a-snapshot sort of reboot, which is cool. But I just can't seem to make it happy. My partner has the same laptop as me (Del Inspiron 7391, Win10 x64) and a pretty similar config; I saw her update come through this week but didn't have the same issue.