Replies

Uninstalling “Web Control” from the client machine via Windows’ program manager did stop the error here, despite what a user in the McAfee thread said, so it does seem to be Web Control causing the issue.

We can’t deploy 10.7 yet because McAfee hasn’t released it onto ‘Cloud ePO’ which is how we manage Endpoint, rather than on-premises. I suppose I’ll have to open a ticket with them to see how long they’re going to wait.

Thanks again for the help, everyone. Hopefully a firm solution can be found. Between Windows’ ‘Wild West Updates’ and McAfee, my hair is going grey.

1 user thanked author for this post.

b

anonymous wrote:

I also have the issue, with 2 customers. I you uninstall mcafee virusscanner (10.6  endpoint protection) problem is resolved. On mcafee site nothing to find. Now I need to find what exactly in mcafee I have to turn off.

Aha! We also use Mcafee Endpoint 10.6. It will have to be Threat Prevention I think, *maybe* Web Control if it interacts with Outlook somehow; because we do not deploy the Firewall product to some machines on the internal network and 2 of those machines were having the issue.

 

I can also confirm that your reproduction steps and workaround work here as well. I  would note that I can no longer cause the issue to occur on the machine in my office that I fully patched with Outlook updates (now running 16.0.4966.1000) but it wasn’t reliably producing the error like the live cases I have, so I can’t confirm that Outlook patches helps yet.

Thanks for the update, I’ll also begin investigating McAfee for specifics.

We don’t have Chart Tools installed, though something obviously installs it since the file is there. I may try deploying it out anyway to see if it works.

Before that I am pushing out all of the missing Office updates, the two machines I could get quick hands on both had “Other MS Product updates” disabled for some reason so a thorough patching may do the trick.

I had read about the Path changes a bit but it didn’t seem to exactly apply since it seems to solve the “failure to launch” case of the error; It may come to trying that out, but I’d rather not risk it as a bandaid solution until I have exhausted everything else.

Thanks for the help so far, I’ll update as I discover more.

32 Bit (16.0.4266.1001)

Chart.dll (and most files in that folder)  are  dated: July 31, 2015

Our environment is unchanged since roughly October 2017 outside of the normal updates, and I have not encountered this error.