npm start problem in reactjs

pleas help me how can solve these problem? i ｢wds｣: Project is running at http://10.4.91.252/ i ｢wds｣: webpack output is served from i ｢wds｣: Content not from webpack is served from C:\Users\Enat\Desktop\React\my-app\public i ｢wds｣: 404s will fallback to / Starting the development server…

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

Error: spawn cmd ENOENT at Process.ChildProcess._handle.onexit (internal/child_process.js:267:19) at onErrorNT (internal/child_process.js:467:16) at processTicksAndRejections (internal/process/task_queues.js:84:21) Emitted ‘error’ event on ChildProcess instance at: at Process.ChildProcess._handle.onexit (internal/child_process.js:273:12) at onErrorNT (internal/child_process.js:467:16) at processTicksAndRejections (internal/process/task_queues.js:84:21) { errno: -4058, code: ‘ENOENT’, syscall: ‘spawn cmd’, path: ‘cmd’, spawnargs: [ ‘/s’, ‘/c’, ‘start’, ‘“”’, ‘/b’, ‘“http://localhost:3000”’ ] } npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! my-app@0.1.0 start: react-scripts start npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the my-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:.…\AppData\Roaming\npm-cache_logs\2020-03-12T11_19_38_702Z-debug.log

[sqal]

I finally managed to fix it, thanks to this comment - https://github.com/gatsbyjs/gatsby/issues/1767#issuecomment-546111367

I don’t know why but I didn’t have C:\Windows\System32 added to my PATH variable.

[hmhelal99]

I have fixed by adding C:\Windows\System32 to my PATH varible.