horion70

I also did the background fix suggested but didn't help. This is an entirely other bug in windows 1809 version. I think the non-legit activation software unfortunatelly it not the cause of the bug. This bug also happens on my 3 retail legitimate windows 10 pro pc's in rare ocassions, mostly when notification center shows a couple of messages.

@itman Thank you very much for the reply. I can finally confirm, after extensive tests that this is NOT an eset issue. The crash happens even without any av installed. It is a windows 1809 bug only.

This warning appears until you clear the log. Maybe its a new feature. You can still click apply to disable the protection.

No. Dism commands or repair doesn't help, computer does not need to staying on all the time. it happens randomly.This is clearly a bug, maybe something change in the latest eset updates. this also happens on a fresh win install, tested on different pc. Further testing with other av or the default win defender this error does not occur.

Same issue here. It seems there is a compatibility bug with latest windows 1809. Tested on 3 windows 10 pro ver. 1809 computers with the latest eset version 12.0.31.0. The crash in ShellExperienceHost mostly happens when temporary disable and then enable eset or randomly when action center shows any message. Also when eset is disabled when clicking on windows message in notification center to enable, eset does not auto enable. The crash also showing in reliability monitor. I have temporarily unistall eset antivirus until the bug is fixed.