After win10 installs node, npm cannot use

after win10 system installs node successfully, node-v can publish this number, but npm cannot be used. Error:

Error: spawn D:\nodejs\node.exe ENOENT
    at _errnoException (util.js:1031:13)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:201:19)
    at onErrorNT (internal/child_process.js:389:16)
    at _combinedTickCallback (internal/process/next_tick.js:138:11)
    at process._tickCallback (internal/process/next_tick.js:180:9)
    at Function.Module.runMain (module.js:684:11)
    at startup (bootstrap_node.js:191:16)
    at bootstrap_node.js:613:3
D:\nodejs\node_modules\npm\lib\npm.js:51
      throw new Error("npm.load() required")
      ^

Error: npm.load() required
    at Object.get (D:\nodejs\node_modules\npm\lib\npm.js:51:13)
    at process.errorHandler (D:\nodejs\node_modules\npm\lib\utils\error-handler.js:205:18)
    at process.emit (events.js:159:13)
    at process._fatalException (bootstrap_node.js:382:26)
5.5.1

events.js:136
      throw er; // Unhandled "error" event
      ^

Error: spawn D:\nodejs\node.exe ENOENT
    at _errnoException (util.js:1031:13)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:201:19)
    at onErrorNT (internal/child_process.js:389:16)
    at _combinedTickCallback (internal/process/next_tick.js:138:11)
    at process._tickCallback (internal/process/next_tick.js:180:9)
    at Function.Module.runMain (module.js:684:11)
    at startup (bootstrap_node.js:191:16)
    at bootstrap_node.js:613:3

just use the npm command to report this error, and ask the boss to tell me what the problem is and how to solve it.

Npm
Feb.27,2021

just downgrade the version of node. Test the link description


the new version of npm-v encountered the same error. In the C:WindowsSystem32 location, find cmd, and the administrator runs the cmd, paste input sfc/scannow command to repair the operation. Wait for dozens of minutes to repair and install the new version of nodejs and solve all the problems.


I also reinstalled win10 some time ago. The problem is node-v can. npm-v shows that it is not an internal command, but should be the problem of environment variables. Later, I reset the win10 system, which is inexplicable. For reference only,


Stack overflow has a similar problem . I hope I can help you.


I don't know what version you installed, I have tried: node-v8.9.4-win-x64 version, after installation is to report your kind of error. Later, it was uninstalled and replaced with the version of node-v6.12.3-x64.msi, and after installation, you can use npm. I am also the win10 system


finally reinstalled the system to solve.


I encountered the same problem. All the solutions to the posts have been tried and have not been solved. In the end, I did not give up and resolutely did not use the second skills of network management to redo the system.
correct handling, download clean registry software, uninstall node.js, to delete related folders, and then use the software to strongly clean the registry, restart the system update, and install node.js, again to solve the problem. If you encounter a problem in the
process, you can: tianeternal@sina.com @ me


I also suddenly have this problem in win10. Later, I updated the system and reinstalled the new version of node

.
Menu