Firstly, 2 different problems with possibly the same cause are described here. The Passolo Translator Edition can run macros, but does not have a macro development environment itself. This would explain the first error. However, only the Xbench developers know why the Xbench add-in reports a macro-based error. It is possible that macros are called in the Xbench add-in.

Has this ever worked before? I would first make sure that the latest version of the 2018 Translator Edition is loaded and used from the RWS site. The macro engine itself is a component that must be registered properly within the Windows operating system. If that fails, it would explain both errors. My first approach would be to install the latest 2018 Translator Edition again so that the Basic engine component is registered correctly. Another approach would be to install the Translator Edition on another computer and test it.

Hello, thank you for your answer! This hasn't worked before on my laptop, given that I haven't needed it before. It works on my colleague's laptop and I followed the same installation and setup process for Passolo and specific macros as they did. Could you clarify what exactly you mean by "macro engine"? Thank you!

Hello, thank you for your answer! This hasn't worked before on my laptop, given that I haven't needed it before. It works on my colleague's laptop and I followed the same installation and setup process for Passolo and specific macros as they did. Could you clarify what exactly you mean by "macro engine"? Thank you!

The "macro engine" are the Passolo components that are loading, interpreting and running the macros. BTW, the first error message above, when does it appear, so which menu function are you calling?

Hey, Achim! Thanks for answering.

It shows up immediately when I try to run the macro check.