React npm start con't run and open the localhost:3000

app@0.1.0 start C:\Users\mohammad ahmad\Desktop\React Projects\app react-scripts start

Starting the development server…

events.js:174 throw er; // Unhandled ‘error’ event ^

Error: spawn cmd ENOENT at Process.ChildProcess._handle.onexit (internal/child_process.js:240:19) at onErrorNT (internal/child_process.js:415:16) at process._tickCallback (internal/process/next_tick.js:63:19) Emitted ‘error’ event at: at Process.ChildProcess._handle.onexit (internal/child_process.js:246:12) at onErrorNT (internal/child_process.js:415:16) at process._tickCallback (internal/process/next_tick.js:63:19) npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! app@0.1.0 start: react-scripts start npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the app@0.1.0 start script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in: npm ERR! C:\Users\mohammad ahmad\AppData\Roaming\npm-cache_logs\2019-05-15T20_48_25_193Z-debug.log

[creativetim]

Was helping someone with this problem on their Windows box and came across the following SO article and it did the trick.

I checked system variables one more time and found the cause of the problem: missing C:\Windows\System32\ variable. I added it and that solved my problem

More detailed instructions that didn’t get labeled as the answer:

Goto > Control Panel\System and Security\System\Advance system setting\Enviroment variable and set system variables path C:\Windows\System32\ variable and restart your System.

Took a fair amount of Googling to arrive there. Hopefully this helps people out so they aren’t forced to try a particular, now outdated, version of react-scripts just to get their React app running.

[alexreu]

Finally i downgrade my react-scripts in package.json to this version : “react-scripts”: “^2.1.8” and it works for me