In an environment that uses McAfee ePO. The most recent Chrome update is not wanting to play nice. They use SCCM to push out the package and it throws a side-by-side configuration error. Then they have to manually disable McAfee to get it to install. In a large environment, this is not a viable solution. We can't be the only people having this issue. Support is saying this isn't related to McAfee products because there is nothing in any of the logs anywhere about it. Any help is appreciated. Everything is pointing back to Visual C++ library conflicts, but I don't even know where to begin with that.
Do you have a Service Request number for this issue? What McAfee products are installed on the machines having issues? Will Chrome install without being deployed by SCCM? Where is the error seen -- on the server or on the client machines?
You need to first find out what McAfee module or process in causing this. You need to try disabling modules or components one by one so you can find out what block the installation. Start with Access Protection, Exploit Prevention, On-Access scan and so on.
For example if it comes out that it is Firewall module of ENS, you can define Chrome package as a trusted executable: