I've rolled this change out to around 3000 machines in NZ, Australia and throughout Asia. I think the risk is quite low as when they user go to the links the browser action will still take effect.
I'f you are concerned, then I would look at placing a copy of the chart.dll in the syswow64 or system32 folder to work around the issue until McAfee Engineering have had time to diagnose and resolve the issue
Thank you all for reporting this issue. Apologies for the delayed intervention. This forum is being monitored and the issue is acknowledged from our end to have been widely seen with other Customers as well. However, we are awaiting logs that we require to investigate this fully and hence we request you to create Service Requests with us in order to do the same.
Involving Microsoft from your end would also be a good idea here as we have seen in some reported cases where the issue has come up after an Outlook application update was installed to it, however we are seeing reports only with ENS 10.6 Feb update installed.
This issue, however, is not very consistently noticed around owing to which we are struggling to reproduce the issue at will and hence we request your kind help in raising this via a Service Request.
I have Outlook 2016 installed from Office Standard. I had recently updated my 10.7 install to the StandAlone 10.7.0.753.8 version. Previously was at 10.7.0.667.6. With the newer version I was getting the chart.dll error 2 or 3 times a day.
After finding the thread in the top post, I removed the newer 10.7 and went to the older. I did not put in a ticket because I need my Outlook working and didn't want to wait on McAfee support. Plus I couldn't reproduce it on demand. I just couldn't afford to be down while troubleshooting.
We have EPO 5.10. But we haven't pushed out the 10.7 edition due to the minor issues that keep cropping up. I'm just testing 10.7 on a few machines.
We are seeing this issue on a number of systems. 10.7 feb is Deployed on 9500 systems out of 12000 and as we are an NHS organisation, we really do not need this at the moment! Is there any sign of a solution other than uninstall and go back to December release? This is a non-starter on 9500 system. 😞 .
xpader's fix seems to have fixed the issue for us. Haven't seen it since I made those changes.
Also supporting NHS users, but hadn't rolled out the Feb update to more than a handful of PCs.
Have you tried the solution mentioned earlier, or the work around? These have resolved the issue for my customer who is a global logistics firm, and the work around arrested the issue on 3 machines prior to the fix being rolled out.
If these do not resolve the issue then your likely best option is to roll up to Office 2019 or uninstall Web Control.
Thank you for posting on the Community. Our Engineering Team are currently still investigating this issue. We ask anyone experiencing this issue to raise a Service Request with us, so we can collect the necessary data to assist us with our investigation. Sadly, we've been unsuccessful in reproducing this in-house.
We've had various feedback from customers so far in regards to what resolves the issue. This feedback includes reinstalling/ repairing Outlook as well as implementing the workaround noted in this KB article: https://kc.mcafee.com/corporate/index?page=content&id=KB89946 > might be worth trying these options if you are experiencing the issue.