Hi, the same happens to me for more than 1 year. Studio 2019 SR2 always updated. MS 365 always updated. I am using Word spellchecker.

mark seth Daniel Gebauer

I discussed this with the support team to see if they had ever come across this before and the suggestions were these:

1. make sure you are not using any other add-ins to Office which might prevent Studio from closing the Office instance that is used for the spell checker.
2. make sure you have installed all the latest updates for MS Office

Certainly we don't have any cases in support for this specific issue, and don't seem to have anything pending a fix on our side either.  It seems as though the issue really is related to Office.

I'm happy to investigate this further in case there is something here we do need to fix but you need to make sure you have addressed the two things above first.

mark seth Daniel Gebauer

I discussed this with the support team to see if they had ever come across this before and the suggestions were these:

1. make sure you are not using any other add-ins to Office which might prevent Studio from closing the Office instance that is used for the spell checker.
2. make sure you have installed all the latest updates for MS Office

Certainly we don't have any cases in support for this specific issue, and don't seem to have anything pending a fix on our side either.  It seems as though the issue really is related to Office.

I'm happy to investigate this further in case there is something here we do need to fix but you need to make sure you have addressed the two things above first.

Thank you!

Hi Paul,

Thanks, I've forgotten you. I just haven't received any work for Studio since then, so I haven't tested it yet. I couldn't really find any suspicious add ins, except maybe LB's Translation Workspace and the Nitro Pro add in (PDF software). So I've deleted the Translation Workspace and have deactivated Nitro Pro add in. I'll let you know if it works once I've had a chance to do more work in Studio.

mark seth said:

I couldn't really find any suspicious add ins, except maybe LB's Translation Workspace and the Nitro Pro add in (PDF software).

Thanks mark seth... I guess knowing what might be suspicious is tricky.  I doubt any plugin for word has ever been tested against this scenario!  Looking forward to seeing what you find.

Hi Paul,

A few jobs later and I haven't had the problem again (yet). So it looks like deactivating those two add ins have worked, probably Translation Workspace I'm guessing. Office was already up to date, so that wasn't the issue. I'll let you know if the problem reappears or if it wasn't Translation Workspace causing it.

Thank you for the help-

Mark