thanks for your report, can you answer a few questions:

 - does this issue only affect 64-bit Chrome - if you try and install 32-bit chrome 58 does it work again?
 - are your users accessing Chrome via remote desktop, or on their own client machines, if latter, are they all running Windows Server 2008 R2, or Windows 7?

- Chrome 32-bit works and is a workaround we are using.
- Their own client, end-user machines (desktops and laptops), all Win7 64-bit.  40+ reported cases but not all use Chrome.  
- Backend server environment is mixed but issue is with non-virtual end-user machines.

Thanks for your quick response.

Are you using any security software products on the end user machines? - for example, there is a known incompatibility with McAfee data loss prevention and McAfee have released an advisory about this -> https://kc.mcafee.com/corporate/index?page=content&id=KB85333

Can you also try running with some logging enabled on the Chrome.exe command line:

--enable-logging=stderr --v=1 --vmodule=metrics=2 > log.txt 2>&1

Once you have the log.txt file, search the log.txt for the histogram Process.Sandbox.Launch.Error and reply with that here, or just enclose the entire log.txt (it will contain no personal information).

I ran the command and the browser launched and failed on both displaying the log file and whatever the 2nd tab was trying to do.  It also did not build the log file but I captured the data from the command window.  I searched it for 'histogram' and 'Sandbox' and there is nothing in there for those.

Deleted: log.txt 16.5 KB

log.txt 16.5 KB View Download

Hi - thanks for the log - however you appear to have missed out the > characters in your command line, so that is why logging was captured to the log file, can you try again? Also, make sure all other Chrome browser sessions are closed before running the command:

chrome.exe --enable-logging=stderr --v=1 --vmodule=metrics=2 > log.txt 2>&1

make sure you have the > between log.txt and before the &1

I just identified the conflict.  It is McAfee related.

Note a duplicate.  We do not use DLP.  In my case, the conflict is with McAfee's Solidcore.