Protractor: spawn cmd ENOENT error when issue we run the "webdriver-manager start" command on Windows7

Created on 26 Feb 2016  路  9Comments  路  Source: angular/protractor

Hi there!

Thanks for submitting an issue to Protractor.

To help us help you better, please do the following before submitting an issue:

  1. Review the questions section of CONTRIBUTING.md
  2. Make sure you are not asking a usage or debugging question. If you are, use StackOverflow, Google Group discussion list, or Gitter to get help.
  3. Fill in the information that corresponds to your type of issue below
  4. Delete this intro and any unrelated text :smile: (if you do not we'll assume you haven't read these instructions and automatically close the issue)

Bug report

  • Node Version: v4.3.1
  • Protractor Version: 3.1.1
  • Browser(s): Chrome``
  • Operating System and Version Windows7 Ultimate
  • Your protractor configuration file
  • A relevant example test
  • Output from running the test
  • Steps to reproduce the bug
  • Installed Java
  • Installed NodeJS
  • Verified versions of Node, NPM - success
  • Ran 'npm install -g protractor' command.
  • Verified version - success
  • Ran command - 'webdriver-manager update' -success.
  • Ran command 'webdriver-manager start' , observed that spawn cmd ENOENT error.

Also please check my ENV variable for PATH.
C:\Program Files (x86);C:\ProgramData\Oracle\Java\javapath;C:\Program Files (x86)\Java\jdk1.7.0\bin;C:\Program Files (x86)\nodejs;C:\Users\Administrator\AppData\Roaming\npm

Reasons for adopting new feature

  • Is this a breaking change? (How will this affect existing functionality)
    spamwn

Most helpful comment

Issue resolved after adding "C:\Windows\System32\" to your PATHs. On windows, right-click My Computer -> Properties -> Advanced system settings -> Environment Variables -> Edit... PATH and add "C:\Windows\System32\" to the end (with a semi-colon separating each variable).

All 9 comments

Issue resolved after adding "C:\Windows\System32\" to your PATHs. On windows, right-click My Computer -> Properties -> Advanced system settings -> Environment Variables -> Edit... PATH and add "C:\Windows\System32\" to the end (with a semi-colon separating each variable).

Thanks for reporting back that this is solved.

hi sekharlcann1 sir,

iam sai pruthvi i too got the same error and i changed my path by adding C:\Windows\System32\ still aim getting same error when i start webdriver manager please guideme

@saipruthvi47 The solution above did not work for me either, please let me know if you found an alternative

@larry-dalmeida you got any solution for this issue. If yes please let me know, coz i stuck at the same point.
Thanks.

@Kalpesh1650 Sorry, It was almost a year back and I am not really sure how I resolved it, but I may have tried another test framework. Just in case you didn't do this: after you update the PATH variable as shown above, CLOSE the cmd prompt and try again on a new cmd prompt instance.

@larry-dalmeida my issue resolved now by restarting CMD after updating PATH variable

Issue resolved after adding "C:\Windows\System32" to your PATHs. On windows, right-click My Computer -> Properties -> Advanced system settings -> Environment Variables -> Edit... PATH and add "C:\Windows\System32" to the end (with a semi-colon separating each variable).

Thanks.. this is worked for me

This worked for me.. Thanks man this is great

Was this page helpful?
0 / 5 - 0 ratings