ELOGA

Yesterday (2024-02-28), for the first time, I installed Malwarebytes on our laptop computer(OS = Microsoft Windows 10), and which already is running ESET NOD32. This AM I saw this same error message for the first time. As Mr. Goldberg states, I also clicked the 'restart device' link, and the laptop computer took much longer to restart, and the issue did not recur; also I checked the advanced setup, and AMSI is enabled. In our case, and possibly for others also, this seems like might be a possible conflict between Malwarebytes and ESET? However, note that we already have both ESET NOD32 and Malwarebytes running on our "tower" computer (OS = Microsoft Windows 10), for many years and this issue has never arisen on that computer.