VanBuran

I can't get excited over this development.
AMD based motherboard users are excluded. Also, only Intel motherboard users using integrated graphics are the only ones this feature would apply to. This by large would be commercial users. Also, many Intel motherboard home desktop users have a third party graphics card installed. As such, this feature would be N/A for them.

This command is fix problem for now, but not sure what will happened with other apps like Premiere Pro, i will test later
 
cd c:\windows\system32 lodctr /R  

Sorry, misread.Thanks

I have a three  pack Premium. The two desktop update but the laptop will not. I have tried clearing the cache which did not help.

I find that eSet is always to quick to report an error that is due to the fact that it is active before the internet connection has been established. I get fed up  with getting messages about not being able to reach live servers or failed to update product when I know that if I wait a few seconds for the wi-fi to sort itself out the message will usually go away. This false error message makes users feel insecure and there is a "cry wolf" aspect that if there is a real error, it might be ignored.
The ability to set a delay on the error reporting message system to check for live internet before flashing up warnings would be helpful. Even something as simple such as "waiting for live internet connection before checking" would be better than sending unhelpful error messages.
Does anybody agree with me?

Is your Eset update profile - update type, set to "Ask before downloading update?"