I do not know what you are trying to achieve. This works normally why import setting that is coming from the old instalaltion? Let me remind you, we are not eset buying client. So do not expect something similar to the buying client of eset.
leading up to my comment there have been many other people having issues with this. I'm sharing my insight to hopefully help others who are still struggling with this issue.
As for your questions
What am i trying to achieve? - Hoping to provide information to others with this issue and hoping there is someone smarter than me who's figured out which part of the xml file to manipulate in order to get the basic feature to work with the patched release.
Why import settings? - I'm pretty sure this is self explanatory. The software learns habits, user input, has settings including: exceptions, ignore lists, block/allow lists etc. If you can't import your existing settings you have to retrain it and remember all of the settings you've had in the past to reset manually.
For someone who's using this with a computer they use as word processor, that's no big deal. But for someone who's blocking or not blocking numerous program, windows features, phone homes, or settings up stuff to work from within or outside of their network - the import settings feature becomes quite useful.
no one expects the customer service of eset here... that's why we are all here to help each other.