Hello,
I've experienced the identical problem (although the list of disabled components was slightly different because of the configuration I use).
The problem appears to be caused by an update published today which should have, but didn't prompt for a re-boot. Note that this update was not flagged as a software update, it was one of the regular definition updates (version 17097 to 17083) or some component update delivered with these.
The problem disappears if the computer is re-started.
The really crazy part is that, depending on where I looked, the ESET software gave conflicting opinions as to whether there was a problem. For example:
Inserting a CD/DVD brings up the usual scan-on-demand window which showed the problem.
The configuration screens in Set-up showed no problems.