Haruhiko Nishida 

Sounds funny but the solution is don't save any files on OneDrive... or see if this works when you set OneDrive to always ensure the files remain in local even though they may also be saved in the cloud.

My recommendation would be to not use OneDrive for any Studio or MultiTerm files.  I appreciate the default location goes there, I have experienced this myself recently with my home laptop, and I think this needs to be addressed.  But I just changed my OneDrive settings for now so that all files are always local and cloud.  Unfortunately OneDrive doesn't seem to let me choose which folders so it's all or nothing.

Paul, thanks for your reply. I currently save/create termbase on local (even though its on windows 365, means cloud...). 

 Haruhiko Nishida 

ok… and what settings do you have for your “office 365”? Is it set for files to be moved to cloud when you don’t use them or is it set to always be available locally?

what do you mean "office 365" setting?

what I currently doing (as tentative solution) is create termbase with multiterm on (so-called) local file system like C:\Users\xxxxxx\Documents\Termbases\xxxx.sdltb, then set it as termbase in trados project.

Office 365's default "Document" directory seems assigned to onedrive. I didn't try to change it to local disk yet.

Haruhiko Nishida 

Haruhiko Nishida said:

what do you mean "office 365" setting?

ok - I see this now says "windows 365".  I was just trying to use your terminology in an effort to help you understand.  What I am referring to is OneDrive.  If you are putting the files on OneDrive and they are set to be cloud only then this is problematic for Trados Studio and Multiterm.

So don't use cloud drives for these files.

OK, I understand that current (at least) multiterm seems doesn't work if the termbase file is on OneDrive.

OK, I understand that current (at least) multiterm seems doesn't work if the termbase file is on OneDrive.