I have installed Windows 10 on two systems. One has MSE enabled and the other has Eset Nod32. Nod32 was installed on that machine under Windows 7 and after converting the OS to Windows 10 it continued to work. Windows 10 is now facilitating notifications that the Eset license needs to be renewed, but
IT IS NOT TRYING TO TRICK ME INTO USING MSE.
Also, back in the day I had an HP laptop with an AMD Duron processor, and it came with Symantec AV. I had overtemp shutdowns. I diagnosed that the AV was using most of the CPU cycles by far. So I researched the providers and somehow Nod32 came out on top across two or three different AV shootouts. I replaced Symantec with Nod32 and the laptop ran so much better. After that I only ran bundled AV on new machines until I could get around to installing Nod32. Nod32 continues to behave appropriately.
On the machine that runs MSE instead of Nod32, there was a different application chewing up the CPU cycles: The HP support assistant.
IT IS NOT TRYING TO TRICK ME INTO USING MSE.
Also, back in the day I had an HP laptop with an AMD Duron processor, and it came with Symantec AV. I had overtemp shutdowns. I diagnosed that the AV was using most of the CPU cycles by far. So I researched the providers and somehow Nod32 came out on top across two or three different AV shootouts. I replaced Symantec with Nod32 and the laptop ran so much better. After that I only ran bundled AV on new machines until I could get around to installing Nod32. Nod32 continues to behave appropriately.
On the machine that runs MSE instead of Nod32, there was a different application chewing up the CPU cycles: The HP support assistant.