UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36

Steps to reproduce the problem:
A job in a Windows Server 2008 R2 VM is running the following command line for karma tests in headless chrome:

C:\Program Files (x86)\Google\Chrome\Application\chrome.exe --user-data-dir=C:\Users\_HUDSO~1\AppData\Local\Temp\karma-46941119 --no-default-browser-check --no-first-run --disable-default-apps --disable-popup-blocking --disable-translate --disable-background-timer-throttling --disable-renderer-backgrounding --disable-device-discovery-notifications http://localhost:9876/?id=46941119 --headless --disable-gpu --remote-debugging-port=9222

Chrome will launch but NOT in headless mode.

If the order is changed so that --headless is at the end it works:
C:\Program Files (x86)\Google\Chrome\Application\chrome.exe --user-data-dir=C:\Users\_HUDSO~1\AppData\Local\Temp\karma-46941119 --no-default-browser-check --no-first-run --disable-default-apps --disable-popup-blocking --disable-translate --disable-background-timer-throttling --disable-renderer-backgrounding --disable-device-discovery-notifications http://localhost:9876/?id=46941119 --disable-gpu --remote-debugging-port=9222 --headless

I can verify that chrome launches by looking at resource monitor (I am making the assumption that it being in the process monitor means it is functioning nominally).

I can't figure out why but this only happens on some machines even though they all have the same chrome version installed.

What is the expected behavior?
Headless will launch regardless of the order of the command line options

What went wrong?
Chrome is starting up the UI and is not launching in headless mode on some machines. It seems that this happens only when --headless comes before --disable-gpu

Did this work before? N/A 

Chrome version: 62.0.3202.62  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: 

Chrome was installed using the enterprise msi installer. These are build machines so normally chrome is not used by end users but rather from builds on the command line.

I have tried --enable-logging with --v=1 but the chrome_debug.log is empty