So yes, I have closed MultiTerm and tried again three times.

I run Bitdefender and Zonealarm, these being very current/possibly even most up to date versions. I  run Windows 10 on an Intel Core i7 4770 machine with 16 GB RAM and an SSD. 

I think this https://community.sdl.com/product-groups/translationproductivity/f/studio/19917/error-telemetry link to the Knowledge Base might help. -- The error reported above did not occur anymore for a few hours, a simple PC reboot helped. I successfully imported into an existing termbase. EDIT 11/26/2019: However, the problem keeps reoccurring all the time. I would appreciate help with this. Or is this something for SDL Support to look into using remote access software?

EDIT 11/26/2019: Unfortunately, the problem persists.

I believe this can be 'controlled' from within Studio. Go to the Add-Ins in the ribbon and then click on Plug-ins. In Studio 2019 apparently you no longer see the telemetry plug-in, but it is available in Studio 2017 (the version you are running, right?). Once you find it, you uncheck it. Then restart Studio and next restart Multiterm. It may work. However you will have to go back and check the plug-in again, otherwise your Studio may not start. Try this at your own risk. Just my advice. On the other hand, whenever you need to explore your Multiterm termbases without opening MultiTerm Desktop, you can use Tb-Scout (found in the SDL appstore). appstore.sdl.com/.../ and if you can access your termbases from within Studio, that's good enough, unless you are doing bulk updates. Also, and this is my very personal advice based on experience and knowledge: do not waste your time resetting, reinstalling Studio, MultiTerm. Bad idea. Whenever you have problems with, for instance, Microsoft Office, you need not reinstall Office, and that goes for any software. If you have to reinstall any software program it means that software program is buggy. That is not the case here. As simple as that.

Thanks very much, Ozzie. I haven't found any Telemetry plug-in in that plug-in list yet. Also, Studio version is 2019, and 2019 only (running short of licences). MultiTerm version is 2017 and 2019 (because 2019 sometimes would not do a thing upon opening it I keep MultiTerm 2017 operational).

Hi, Astrid. It shouldn't be a problem if you have different versions of MultiTerm in the same computer. I, for one, have 4 MultiTerm versions (2019, 2017, 2015 and 2014) installed because I need them to test the app Tb-Scout.

I would think, though, that running Studio 2019 and (just) MultiTerm 2017 should be a problem. My suggestion, install MultiTerm 2019 as well, and keep MultiTerm 2017.

If you happen to be in the US, happy Thanksgiving Day!

Hello Astrid Elke Witte ,

Just to add to this for clarity- although its possible to have multiple versions of Studio and MultiTerm installed  these must be both on the latest stand.

ie- If you update Studio 2019, you need to check for updates in MultiTerm as well- which might explain why....

Astrid Elke Witte said:

(because 2019 sometimes would not do a thing upon opening it I keep MultiTerm 2017 operational).

Having 'out of synch' versions is a common issue (but easily rectified).