worker process failed [pid:undefined] in win 10

am facing the below error when i am trying to run the example media soap project. in win 10
.

worker process failed [pid:undefined]: spawn D:\mediasoup-demo-3\server\node_modules\mediasoup\worker\out\Release\mediasoup-worker ENOENT +0ms
(node:5740) UnhandledPromiseRejectionWarning: Error: spawn D:\mediasoup-demo-3\server\node_modules\mediasoup\worker\out\Release\mediasoup-worker ENOENT
at Process.ChildProcess._handle.onexit (internal/child_process.js:267:19)
at onErrorNT (internal/child_process.js:469:16)
at processTicksAndRejections (internal/process/task_queues.js:84:21)
(node:5740) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise
which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_un
handled_rejections_mode). (rejection id: 1)
(node:5740) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero
exit code.

It did not even install properly. The C++ mediasoup-worker build failed. You may have noticed that during the installation.

Look here for Windows related issues: https://github.com/versatica/mediasoup/issues

after adding the python and c ++…getting below wrror

PS D:\mediasoup-demo-3\server> npm i
npm WARN deprecated fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.

mediasoup@3.6.19 postinstall D:\mediasoup-demo-3\server\node_modules\mediasoup
node npm-scripts.js postinstall

npm-scripts.js [INFO] running task “postinstall”
npm-scripts.js [INFO] executing command: C:\Python27 ./worker/scripts/configure.py --format=msvs -R mediasoup-worker
‘C:\Python27’ is not recognized as an internal or external command,
operable program or batch file.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.2.7 (node_modules\chokidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:"win32
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! mediasoup@3.6.19 postinstall: node npm-scripts.js postinstall
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the mediasoup@3.6.19 postinstall 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\LENOVO\AppData\Roaming\npm-cache_logs\2020-09-09T06_18_07_831Z-debug.log
PS D:\mediasoup-demo-3\server> npm i
npm WARN deprecated fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.

mediasoup@3.6.19 postinstall D:\mediasoup-demo-3\server\node_modules\mediasoup
node npm-scripts.js postinstall

npm-scripts.js [INFO] running task “postinstall”
npm-scripts.js [INFO] executing command: C:\Python27 ./worker/scripts/configure.py --format=msvs -R mediasoup-worker
‘C:\Python27’ is not recognized as an internal or external command,
operable program or batch file.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.2.7 (node_modules\chokidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“win32”,“arch”:“x64”})

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! mediasoup@3.6.19 postinstall: node npm-scripts.js postinstall
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the mediasoup@3.6.19 postinstall 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\LENOVO\AppData\Roaming\npm-cache_logs\2020-09-09T06_22_50_287Z-debug.log

unable to find the pyhon path