Bundled Protractor Binary Not Working in 4.0.3

[Joshua Grant]

I recently posted a bug on the Protractor Github project and it was suggested my issue was a support issue and not a bug. So I'll ask my question here.

Using a Windows 10 machine with Node v4.4.4, I recently updated our Protractor test project from protractor v3.3.0 to v4.0.3. Now, when I run a globally installed instance of protractor

protractor my.conf.js

everything works as before. When I run the protractor binary installed as part of the project

cd myproj
npm install
my_project/node_modules/.bin/protractor my.conf.js

I get strange behaviour. Either the test run crashes with an error 100 or all tests pass but run nearly instantly and protractor finishes with an error 100 (see attachment).

Both protractor binaries are v4.0.3.

This behaviour did not happen with protractor v3.3.0. This occurs when using Chrome and running against an instance either on a Selenium Grid or a local instance.