Eeek, questions...

What version of CM are you running? Do we know which versions are impacted?

Do we know if this is only for the 2404 O365 channel - or might it affect other patches?

It has been reported against 9.4 and 10.1. We don't think it's CM version specific, as the sites that reported the issue both hit the same Office Update.

As far as we know, this only affects O365 Office.

Great, thanks Sten28, much appreciated.

Our users have been having random Office 365 crashes/freezes since 2404.  The symptoms have been random; sometimes none of the programs run, sometimes only Word freezes or crashes, sometimes only Excel, sometimes only Outlook.  Sometimes Word will show an error about something being broken rather than crashing.

Most of the time a full uninstall then reinstall fixes it, which is why we didn't think it was the CM add-ins.  Some users (me included) haven't had any problems at all.

This is with CM 10.1.

Does anyone know if there has been an official notice about this from OpenText?  Our CM vendor has had numerous reports from other customers and say they are in contact with OpenText about it.

This issue has been quite disruptive for our Organisations. Interested if you find an official notice, for now I have just asked our applications team to stay in touch with our CM vendor for any updates...

Our CM vendor sent an email to us which had:

"We are vigorously working with OpenText on investigating and troubleshooting the issue and its effect on Content Manager."

There doesn't appear to be much vigour from OpenText though.  Does Caroline Oest know anything about this issue and what OpenText are doing to resolve it?  i understand that it is something Microsoft has changed that has broken things and it may take time for OpenText to make a fix, but even an acknowledgement that they are aware of the issue would be nice.

We have few clients reported similar issue who are on 2404 Build, the workaround we advised to change registry key of NativeUI=0.

(Computer\HKEY_CURRENT_USER\SOFTWARE\Micro Focus\Content Manager\OfficeAddins\UseNativeUI).

Interesting.  We have that set to 1, as one of our additional fields on the record entry form via office integration didn't work when set to 0.

Seems like it's expected behaviour, below is from installation doco