npm start throws ELIFECYCLE error with error code 1 when run in Windows while node is working fine

[Vineettiwaridev]

C:\Users\Vineet\Desktop\sam\sam>npm start

sam@0.1.0 start C:\Users\Vineet\Desktop\sam\sam
react-scripts start

internal/fs/utils.js:312
throw err;
^

Error: ENOENT: no such file or directory, lstat 'C:\Users\Vineet\AppData\Local\Temp;C:'
at Object.realpathSync (fs.js:1796:7)
at Object. (C:\Users\Vineet\Desktop\sam\sam\node_modules\temp-dir\index.js:9:13)
at Module._compile (internal/modules/cjs/loader.js:1068:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1097:10)
at Module.load (internal/modules/cjs/loader.js:933:32)
at Function.Module._load (internal/modules/cjs/loader.js:774:14)
at Module.require (internal/modules/cjs/loader.js:957:19)
at require (internal/modules/cjs/helpers.js:88:18)
at Object. (C:\Users\Vineet\Desktop\sam\sam\node_modules\tempy\index.js:5:17)
at Module._compile (internal/modules/cjs/loader.js:1068:30) {
errno: -4058,
syscall: 'lstat',
code: 'ENOENT',
path: 'C:\Users\Vineet\AppData\Local\Temp;C:'
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! sam@0.1.0 start: react-scripts start
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the sam@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\Vineet\AppData\Roaming\npm-cache_logs\2021-05-18T04_19_57_574Z-debug.log

[ghost]

aly0506

[stale]

This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in 5 days if no further activity occurs.