Good morning,

As I tried to set up a new project just now, I found that my termbase was being rejected. I have used that termbase for a couple of years, as recently as earlier this week. An attempt to open it in Studio 2017 threw a 'General error'. MultiTerm refused to open it with the message that it "had been created with an earlier version of MultiTerm". That may well be true, but that was not a problem until earlier this week.

Then I remembered that in today's issue of Windows Secrets, it was written that this month's Microsoft Patch Tuesday update has a side effect: "The 1703 release includes a side effect whereby it may change Czech and Arabic languages to English for Microsoft Edge and other applications."
Although I am still on 1607, I renamed the name of my termbase anyway from Arabic to a name with Latin characters. Lo and behold, that solved the problem. The termbase became accessible again.

I have posted this in Studio and not in MultiTerm, because relevant users will most likely be confronted with it in Studio.

Just for information.

Best regards,