[BUG] After npm upgrade, on Windows getting error that npm.ps1 is not digitally signed #7280
Open
2 tasks done
Labels
Bug
thing that needs fixing
platform:windows
is Windows-specific
Priority 2
secondary priority issue
Is there an existing issue for this?
This issue exists in the latest npm version
Current Behavior
I upgraded npm using
npm install -g npm@10.5.0
, and then afterwards, I can't use the npm command since I get the code execution error that npm.ps1 is not digitally signedThe text was updated successfully, but these errors were encountered: