Trying to upgrade npm in Windows 10
Hello I'm trying to upgrade npm
in Windows 10 and I've searched a lot about the Scripts cannot be executed on this system problem. I ran the script
Set-ExecutionPolicy Unrestricted -Scope CurrentUser -Force
before I rannpm-windows-upgrade
but it gives me:
npm-windows-upgrade v5.0.0
Scripts cannot be executed on this system.
To fix, run the command below as Administrator in PowerShell and try again:
Set-ExecutionPolicy Unrestricted -Scope CurrentUser -Force
and I ran PowerShell as administrator too. Does anybody know what is wrong?
windows powershell
add a comment |
Hello I'm trying to upgrade npm
in Windows 10 and I've searched a lot about the Scripts cannot be executed on this system problem. I ran the script
Set-ExecutionPolicy Unrestricted -Scope CurrentUser -Force
before I rannpm-windows-upgrade
but it gives me:
npm-windows-upgrade v5.0.0
Scripts cannot be executed on this system.
To fix, run the command below as Administrator in PowerShell and try again:
Set-ExecutionPolicy Unrestricted -Scope CurrentUser -Force
and I ran PowerShell as administrator too. Does anybody know what is wrong?
windows powershell
add a comment |
Hello I'm trying to upgrade npm
in Windows 10 and I've searched a lot about the Scripts cannot be executed on this system problem. I ran the script
Set-ExecutionPolicy Unrestricted -Scope CurrentUser -Force
before I rannpm-windows-upgrade
but it gives me:
npm-windows-upgrade v5.0.0
Scripts cannot be executed on this system.
To fix, run the command below as Administrator in PowerShell and try again:
Set-ExecutionPolicy Unrestricted -Scope CurrentUser -Force
and I ran PowerShell as administrator too. Does anybody know what is wrong?
windows powershell
Hello I'm trying to upgrade npm
in Windows 10 and I've searched a lot about the Scripts cannot be executed on this system problem. I ran the script
Set-ExecutionPolicy Unrestricted -Scope CurrentUser -Force
before I rannpm-windows-upgrade
but it gives me:
npm-windows-upgrade v5.0.0
Scripts cannot be executed on this system.
To fix, run the command below as Administrator in PowerShell and try again:
Set-ExecutionPolicy Unrestricted -Scope CurrentUser -Force
and I ran PowerShell as administrator too. Does anybody know what is wrong?
windows powershell
windows powershell
asked Dec 29 '18 at 10:29
HyeonseokJungHyeonseokJung
1
1
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Changing the execution policy will only work if it's not enforced with a local or group policy. Check your local or group policy to see if there are any restrictions set, if there are no restrictions
Then, to install and use this upgrader tool, run (also from an elevated PowerShell or cmd.exe):
npm install --global --production npm-windows-upgrade
npm-windows-upgrade
Check out this article on upgrading npm on Windows:
npm-windows-upgrade
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1388701%2ftrying-to-upgrade-npm-in-windows-10%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Changing the execution policy will only work if it's not enforced with a local or group policy. Check your local or group policy to see if there are any restrictions set, if there are no restrictions
Then, to install and use this upgrader tool, run (also from an elevated PowerShell or cmd.exe):
npm install --global --production npm-windows-upgrade
npm-windows-upgrade
Check out this article on upgrading npm on Windows:
npm-windows-upgrade
add a comment |
Changing the execution policy will only work if it's not enforced with a local or group policy. Check your local or group policy to see if there are any restrictions set, if there are no restrictions
Then, to install and use this upgrader tool, run (also from an elevated PowerShell or cmd.exe):
npm install --global --production npm-windows-upgrade
npm-windows-upgrade
Check out this article on upgrading npm on Windows:
npm-windows-upgrade
add a comment |
Changing the execution policy will only work if it's not enforced with a local or group policy. Check your local or group policy to see if there are any restrictions set, if there are no restrictions
Then, to install and use this upgrader tool, run (also from an elevated PowerShell or cmd.exe):
npm install --global --production npm-windows-upgrade
npm-windows-upgrade
Check out this article on upgrading npm on Windows:
npm-windows-upgrade
Changing the execution policy will only work if it's not enforced with a local or group policy. Check your local or group policy to see if there are any restrictions set, if there are no restrictions
Then, to install and use this upgrader tool, run (also from an elevated PowerShell or cmd.exe):
npm install --global --production npm-windows-upgrade
npm-windows-upgrade
Check out this article on upgrading npm on Windows:
npm-windows-upgrade
edited Dec 29 '18 at 13:28
answered Dec 29 '18 at 13:20
Donald L WilsonDonald L Wilson
114
114
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1388701%2ftrying-to-upgrade-npm-in-windows-10%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown