Rose

Please refer to https://www.eset.com/int/business/partner/anti-malware-sdk/.

Next time this updating issue occurs, use a network connections monitor to ensure ekrn.exe has a solid connection to port 8883. You can use Eset's Network Connections tool or TCPView. I prefer TCPView since it will show if there are sync issues with the connection to port 8883, ekrn.exe is trying to establish. Eset uses port 8883 with fallback to port 443 for Push Notifications. If there are issues with getting that connection, it will cause this bork Eset updating behavior some are experiencing.

most probably those users run a beta version of the software that was just updated to 14.2.10 or they have enabled the pre-release updates in the stable version.
fear not as i have read from a moderator in another post, that it will be released soon.

To put it right, you can export and import cfg within gui in legacy versions but cfg files between v8 and v9+ are not compatible.

It is not possible.

Elaborating, Eset switched the GUI to the Win Metro interface on vers. 9+. As such, all ver. 8 custom rules and the like will have to be re-entered from scratch. This does bring back painful memories ..........................