kipuije,
When I was initially trying to solve this problem I found that disabling HIPS in Comodo did not help in getting the ESET service to start in protected mode. The only way I could get it to load reliably was to either:
1) Take the protection off the ESET service or
2) Add the ESET service (ekrn.exe) and gui (egui.exe) into the exclude list in Comodo as I stated in a post before.
I don't know why disabling HIPS in Comodo does not work but make sure you do either of the above and you should be good to go. My ESET came up after the updates yesterday fine. This is just my experience.
BTW (in answer to itman's question ) I am under Windows 10 64bit Anniversary update.