运行npm start、npm run或npm run-script失败，并出现npm ERR! errno 3221225781
我的节点是干净安装的稳定版本10.16.3 LTS与npm 6.9.0在Windows 10上。一切都安装在C：上的默认路径。
我的示例是使用当前文件结构的最小设置：

node_modules/ <empty>
index.js
package.json

字符串
node_modules文件夹为空。
index.js：

console.log("Hello world..");

型
package.json：

{
  "name": "testnpm",
  "version": "1.0.0",
  "main": "index.js",
  "scripts": {
    "start": "node index.js"
  }
}

型
运行npm start

H:\dev\javascript\testnpm>npm start

> [email protected] start H:\dev\javascript\testnpm
> node index.js

npm ERR! code ELIFECYCLE
npm ERR! errno 3221225781
npm ERR! [email protected] start: `node index.js`
npm ERR! Exit status 3221225781
npm ERR!
npm ERR! Failed at the [email protected] 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! <Path to logs>\_logs\2019-10-19T13_24_15_158Z-debug.log

型
预期的输出将是“Hello World..”，但会失败，如上所示。
直接运行相同的命令会得到预期的结果：

H:\dev\javascript\testnpm>node index.js
Hello world..

型
以下是失败后的日志：

0 info it worked if it ends with ok
1 verbose cli [ 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli   'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli   'start' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle [email protected]~prestart: [email protected]
6 info lifecycle [email protected]~start: [email protected]
7 verbose lifecycle [email protected]~start: unsafe-perm in lifecycle true
8 verbose lifecycle [email protected]~start: PATH: C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;H:\dev\javascript\testnpm\node_modules\.bin;...
9 verbose lifecycle [email protected]~start: CWD: H:\dev\javascript\testnpm
10 silly lifecycle [email protected]~start: Args: [ '-c', 'node index.js' ]
11 silly lifecycle [email protected]~start: Returned: code: 3221225781  signal: null
12 info lifecycle [email protected]~start: Failed to exec start script
13 verbose stack Error: [email protected] start: `node index.js`
13 verbose stack Exit status 3221225781
13 verbose stack     at EventEmitter.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\index.js:301:16)
13 verbose stack     at EventEmitter.emit (events.js:198:13)
13 verbose stack     at ChildProcess.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack     at ChildProcess.emit (events.js:198:13)
13 verbose stack     at maybeClose (internal/child_process.js:982:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
14 verbose pkgid [email protected]
15 verbose cwd H:\dev\javascript\testnpm
16 verbose Windows_NT 10.0.18362
17 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "start"
18 verbose node v10.16.3
19 verbose npm  v6.9.0
20 error code ELIFECYCLE
21 error errno 3221225781
22 error [email protected] start: `node index.js`
22 error Exit status 3221225781
23 error Failed at the [email protected] start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 3221225781, true ]

型
需要说明的是，npm install等可以工作。用node启动脚本也可以工作。唯一不工作的是用npm运行package.json中定义的任何脚本。

编辑：
1.使用npm i -g npm更新npm后出现相同错误
1.提示：错误代码3221225781恰好是.NET中缺少dll的代码
1.我已经删除了所有的开发库，IDE的，分布式的，并根据github上npm的安装说明重新安装。仍然是同样的错误。
1.在Git Bash中运行！但是在CMD和PowerShell中仍然是同样的错误。它让我怀疑PATH，手动添加CMD中的所有Git Bash路径来尝试，仍然是同样的错误。
1.完成Windows的完整安装，运行节点安装，现在安装chocolatey，然后安装以下依赖项：

- chocolatey-dotnetfx.extension v1.0.1
 - python2 v2.7.17
 - kb3033929 v1.0.5
 - visualstudio2017buildtools v15.9.17.0
 - chocolatey-windowsupdate.extension v1.0.4
 - vcredist140 v14.23.27820
 - kb2999226 v1.0.20181019
 - visualstudio-installer v2.0.1
 - kb2919355 v1.0.20160915
 - chocolatey-core.extension v1.3.3
 - kb2919442 v1.0.20160915
 - visualstudio2017-workload-vctools v1.3.2
 - chocolatey-visualstudio.extension v1.8.1
 - dotnetfx v4.8.0.20190930
 - kb3035131 v1.0.3

型
1.它现在起作用了，实际问题是什么可能仍然是一个谜。