Trying to upgrade npm in Windows 10












0















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 ran
npm-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?










share|improve this question



























    0















    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 ran
    npm-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?










    share|improve this question

























      0












      0








      0








      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 ran
      npm-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?










      share|improve this question














      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 ran
      npm-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






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Dec 29 '18 at 10:29









      HyeonseokJungHyeonseokJung

      1




      1






















          1 Answer
          1






          active

          oldest

          votes


















          1














          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






          share|improve this answer

























            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
            });


            }
            });














            draft saved

            draft discarded


















            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









            1














            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






            share|improve this answer






























              1














              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






              share|improve this answer




























                1












                1








                1







                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






                share|improve this answer















                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







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Dec 29 '18 at 13:28

























                answered Dec 29 '18 at 13:20









                Donald L WilsonDonald L Wilson

                114




                114






























                    draft saved

                    draft discarded




















































                    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.




                    draft saved


                    draft discarded














                    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





















































                    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







                    Popular posts from this blog

                    flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

                    Mangá

                     ⁒  ․,‪⁊‑⁙ ⁖, ⁇‒※‌, †,⁖‗‌⁝    ‾‸⁘,‖⁔⁣,⁂‾
”‑,‥–,‬ ,⁀‹⁋‴⁑ ‒ ,‴⁋”‼ ⁨,‷⁔„ ‰′,‐‚ ‥‡‎“‷⁃⁨⁅⁣,⁔
⁇‘⁔⁡⁏⁌⁡‿‶‏⁨ ⁣⁕⁖⁨⁩⁥‽⁀  ‴‬⁜‟ ⁃‣‧⁕‮ …‍⁨‴ ⁩,⁚⁖‫ ,‵ ⁀,‮⁝‣‣ ⁑  ⁂– ․, ‾‽ ‏⁁“⁗‸ ‾… ‹‡⁌⁎‸‘ ‡⁏⁌‪ ‵⁛ ‎⁨ ―⁦⁤⁄⁕