Ok, infact it happens at first install. I tried with another pc of mine after creator update. I think the problem is that at the first install, after insert activation code, eset update itself for the first time, and after that it can't deactivate the windows defender module well (it runs my cpu to 60%) and also i can't stop the first scan, because it's block everything. I managed to run it deactivating windows defender and after a reboot it's running well. I know it's strange, but also with the other computer i did the same things, Install OS, Install drivers; Install Eset (before install other applications) and i had the same issue until i fix like this, because if i don't turn off windows defender in the first reboot it's completely lock my pcs. May be other people doesn't have this problem but because i had with not just one, but two pcs i think it's good to report the problem i had. Thank you .