Unverified50% confidenceSolutionExact time
The common reason npm -v errors out on first run on Windows is that PowerShell's script execution policy restricts unsigned scripts by default; entering the prompted command and confirming releases the restriction, so this is a configuration issue rather than a corrupted installation.
1
Sources
50%
Confidence
Long-term
Relevance
10/30/2026
First Seen
Sources
A Step-by-Step Vibe Coding Tutorial: Get Started with AI Programming in 3 Steps
bilibili马里奥AI大模型10/30/2026
Related Entities
Related Claims
UnverifiedPowerShell does not support cmd-style & command chaining and will throw an AmpersandNotAllowed error.66% similarUnverifiedQwen3.8-27B generated a complete PowerShell cleanup script with a pre-boot check feature enabled by default.65% similarUnverifiedThe engines field of an npm package merely declares the compatible range and by default does not forcibly block installation unless engine-strict is enabled.65% similarUnverifiedThe PowerShell permission check on Windows auto-approved some `Set-Location` or `cd` commands pointing at the current directory with extra arguments prior to v2.1.309.63% similarUnverified一键脚本通常是 Shell 脚本或 PowerShell 脚本，能够在无图形界面情况下静默执行系统级操作，包括写入系统配置、创建开机启动项、修改环境变量、下载并运行额外可执行文件61% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1116935API
curl https://kongchang.com/api/v1/knowledge/claims/1116935MCP
get_claim(id=1116935)