How to install SysInternals in Powershell to allow access through CLI












1














I am currently trying to make junctions in my Windows 10 filesystem and also need to delete a directory with process-locked files in it.



SysInternals seems to have 2 great packages in the form of handle and junction. I'd love to use them if only I could figure out how to install them. I have tried:




  1. Downloading the junction source directly and using ./junction64.exe /install=agent (even though I don't know what that means, probably not wise really). This prints a promising message about the program to terminal but does not make it accessble from path.

  2. Using this article (which initially looked like a parting in the clouds) - I can download the suite but it does not work as shown, just provides
    2 PowerShell scripts. When trying to run the (presumed) install script at C:chocolateylibsysinternals.2018.12.27toolschocolateyInstall.ps1 with Set-ExecutionPolicy Bypass -Scope Process -Force | Powershell .chocolateyInstall.ps1 it comes up that a keyword "Install-ChocolateyZipPackage" is not recognised.


I am sure for such a ubiquitous tool that I am searching the nooks and the solution is hiding in plain sight, but I am not very experienced in package managers and thus I am getting a tad weary in this search



EDIT: Whilst the accepted answer below is valid for the question I have come to realise that I could have just used chocolatey for the entire process, as chocolatey quite rightly recognises it as a package: choco info SysInternals to find available packages with this name and then choco install <packageName>. All executables within SysInternals will be available from $Path










share|improve this question









New contributor




Scott Anderson is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.




















  • I'm not sure I understand correctly but as sysinternals tools are xcopy deployment, you can just download the entire suite, unzip it to wherever you like on your system and for ease of use, add that folder to your path environment variable. From then on, you can open a command prompt (cmd, powershell, …) and run junction/handle. Note that handle is deprecated in favor of processexplorer/procmon (going from memory here so this might be a bit off)
    – Lieven Keersmaekers
    Jan 4 at 7:39












  • That works like a charm thankyou - if you want to post it as an answer I'm happy to accept it
    – Scott Anderson
    Jan 5 at 14:18
















1














I am currently trying to make junctions in my Windows 10 filesystem and also need to delete a directory with process-locked files in it.



SysInternals seems to have 2 great packages in the form of handle and junction. I'd love to use them if only I could figure out how to install them. I have tried:




  1. Downloading the junction source directly and using ./junction64.exe /install=agent (even though I don't know what that means, probably not wise really). This prints a promising message about the program to terminal but does not make it accessble from path.

  2. Using this article (which initially looked like a parting in the clouds) - I can download the suite but it does not work as shown, just provides
    2 PowerShell scripts. When trying to run the (presumed) install script at C:chocolateylibsysinternals.2018.12.27toolschocolateyInstall.ps1 with Set-ExecutionPolicy Bypass -Scope Process -Force | Powershell .chocolateyInstall.ps1 it comes up that a keyword "Install-ChocolateyZipPackage" is not recognised.


I am sure for such a ubiquitous tool that I am searching the nooks and the solution is hiding in plain sight, but I am not very experienced in package managers and thus I am getting a tad weary in this search



EDIT: Whilst the accepted answer below is valid for the question I have come to realise that I could have just used chocolatey for the entire process, as chocolatey quite rightly recognises it as a package: choco info SysInternals to find available packages with this name and then choco install <packageName>. All executables within SysInternals will be available from $Path










share|improve this question









New contributor




Scott Anderson is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.




















  • I'm not sure I understand correctly but as sysinternals tools are xcopy deployment, you can just download the entire suite, unzip it to wherever you like on your system and for ease of use, add that folder to your path environment variable. From then on, you can open a command prompt (cmd, powershell, …) and run junction/handle. Note that handle is deprecated in favor of processexplorer/procmon (going from memory here so this might be a bit off)
    – Lieven Keersmaekers
    Jan 4 at 7:39












  • That works like a charm thankyou - if you want to post it as an answer I'm happy to accept it
    – Scott Anderson
    Jan 5 at 14:18














1












1








1







I am currently trying to make junctions in my Windows 10 filesystem and also need to delete a directory with process-locked files in it.



SysInternals seems to have 2 great packages in the form of handle and junction. I'd love to use them if only I could figure out how to install them. I have tried:




  1. Downloading the junction source directly and using ./junction64.exe /install=agent (even though I don't know what that means, probably not wise really). This prints a promising message about the program to terminal but does not make it accessble from path.

  2. Using this article (which initially looked like a parting in the clouds) - I can download the suite but it does not work as shown, just provides
    2 PowerShell scripts. When trying to run the (presumed) install script at C:chocolateylibsysinternals.2018.12.27toolschocolateyInstall.ps1 with Set-ExecutionPolicy Bypass -Scope Process -Force | Powershell .chocolateyInstall.ps1 it comes up that a keyword "Install-ChocolateyZipPackage" is not recognised.


I am sure for such a ubiquitous tool that I am searching the nooks and the solution is hiding in plain sight, but I am not very experienced in package managers and thus I am getting a tad weary in this search



EDIT: Whilst the accepted answer below is valid for the question I have come to realise that I could have just used chocolatey for the entire process, as chocolatey quite rightly recognises it as a package: choco info SysInternals to find available packages with this name and then choco install <packageName>. All executables within SysInternals will be available from $Path










share|improve this question









New contributor




Scott Anderson is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











I am currently trying to make junctions in my Windows 10 filesystem and also need to delete a directory with process-locked files in it.



SysInternals seems to have 2 great packages in the form of handle and junction. I'd love to use them if only I could figure out how to install them. I have tried:




  1. Downloading the junction source directly and using ./junction64.exe /install=agent (even though I don't know what that means, probably not wise really). This prints a promising message about the program to terminal but does not make it accessble from path.

  2. Using this article (which initially looked like a parting in the clouds) - I can download the suite but it does not work as shown, just provides
    2 PowerShell scripts. When trying to run the (presumed) install script at C:chocolateylibsysinternals.2018.12.27toolschocolateyInstall.ps1 with Set-ExecutionPolicy Bypass -Scope Process -Force | Powershell .chocolateyInstall.ps1 it comes up that a keyword "Install-ChocolateyZipPackage" is not recognised.


I am sure for such a ubiquitous tool that I am searching the nooks and the solution is hiding in plain sight, but I am not very experienced in package managers and thus I am getting a tad weary in this search



EDIT: Whilst the accepted answer below is valid for the question I have come to realise that I could have just used chocolatey for the entire process, as chocolatey quite rightly recognises it as a package: choco info SysInternals to find available packages with this name and then choco install <packageName>. All executables within SysInternals will be available from $Path







windows-10 command-line powershell packages






share|improve this question









New contributor




Scott Anderson is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











share|improve this question









New contributor




Scott Anderson is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this question




share|improve this question








edited Jan 6 at 21:36







Scott Anderson













New contributor




Scott Anderson is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked Jan 4 at 2:23









Scott AndersonScott Anderson

84




84




New contributor




Scott Anderson is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





Scott Anderson is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






Scott Anderson is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.












  • I'm not sure I understand correctly but as sysinternals tools are xcopy deployment, you can just download the entire suite, unzip it to wherever you like on your system and for ease of use, add that folder to your path environment variable. From then on, you can open a command prompt (cmd, powershell, …) and run junction/handle. Note that handle is deprecated in favor of processexplorer/procmon (going from memory here so this might be a bit off)
    – Lieven Keersmaekers
    Jan 4 at 7:39












  • That works like a charm thankyou - if you want to post it as an answer I'm happy to accept it
    – Scott Anderson
    Jan 5 at 14:18


















  • I'm not sure I understand correctly but as sysinternals tools are xcopy deployment, you can just download the entire suite, unzip it to wherever you like on your system and for ease of use, add that folder to your path environment variable. From then on, you can open a command prompt (cmd, powershell, …) and run junction/handle. Note that handle is deprecated in favor of processexplorer/procmon (going from memory here so this might be a bit off)
    – Lieven Keersmaekers
    Jan 4 at 7:39












  • That works like a charm thankyou - if you want to post it as an answer I'm happy to accept it
    – Scott Anderson
    Jan 5 at 14:18
















I'm not sure I understand correctly but as sysinternals tools are xcopy deployment, you can just download the entire suite, unzip it to wherever you like on your system and for ease of use, add that folder to your path environment variable. From then on, you can open a command prompt (cmd, powershell, …) and run junction/handle. Note that handle is deprecated in favor of processexplorer/procmon (going from memory here so this might be a bit off)
– Lieven Keersmaekers
Jan 4 at 7:39






I'm not sure I understand correctly but as sysinternals tools are xcopy deployment, you can just download the entire suite, unzip it to wherever you like on your system and for ease of use, add that folder to your path environment variable. From then on, you can open a command prompt (cmd, powershell, …) and run junction/handle. Note that handle is deprecated in favor of processexplorer/procmon (going from memory here so this might be a bit off)
– Lieven Keersmaekers
Jan 4 at 7:39














That works like a charm thankyou - if you want to post it as an answer I'm happy to accept it
– Scott Anderson
Jan 5 at 14:18




That works like a charm thankyou - if you want to post it as an answer I'm happy to accept it
– Scott Anderson
Jan 5 at 14:18










1 Answer
1






active

oldest

votes


















0














Using package managers is great and I use Chocolatey myself but the downside (impov) is that you don't need to use them regular enough to get it engrained in memory.
It's kind of figuring it out all over again the next time you use it.



As for the Sysinternals tools, this is just an xcopy deployment so you just download the entire suite and unzip it to wherever you like on you system.



For ease of use, you can add the folder where you've copied the tools to the path environment variable. From then on, you can open your favorite command line shell and run any tool Sysinternals provides.






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


    }
    });






    Scott Anderson is a new contributor. Be nice, and check out our Code of Conduct.










    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1390356%2fhow-to-install-sysinternals-in-powershell-to-allow-access-through-cli%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









    0














    Using package managers is great and I use Chocolatey myself but the downside (impov) is that you don't need to use them regular enough to get it engrained in memory.
    It's kind of figuring it out all over again the next time you use it.



    As for the Sysinternals tools, this is just an xcopy deployment so you just download the entire suite and unzip it to wherever you like on you system.



    For ease of use, you can add the folder where you've copied the tools to the path environment variable. From then on, you can open your favorite command line shell and run any tool Sysinternals provides.






    share|improve this answer


























      0














      Using package managers is great and I use Chocolatey myself but the downside (impov) is that you don't need to use them regular enough to get it engrained in memory.
      It's kind of figuring it out all over again the next time you use it.



      As for the Sysinternals tools, this is just an xcopy deployment so you just download the entire suite and unzip it to wherever you like on you system.



      For ease of use, you can add the folder where you've copied the tools to the path environment variable. From then on, you can open your favorite command line shell and run any tool Sysinternals provides.






      share|improve this answer
























        0












        0








        0






        Using package managers is great and I use Chocolatey myself but the downside (impov) is that you don't need to use them regular enough to get it engrained in memory.
        It's kind of figuring it out all over again the next time you use it.



        As for the Sysinternals tools, this is just an xcopy deployment so you just download the entire suite and unzip it to wherever you like on you system.



        For ease of use, you can add the folder where you've copied the tools to the path environment variable. From then on, you can open your favorite command line shell and run any tool Sysinternals provides.






        share|improve this answer












        Using package managers is great and I use Chocolatey myself but the downside (impov) is that you don't need to use them regular enough to get it engrained in memory.
        It's kind of figuring it out all over again the next time you use it.



        As for the Sysinternals tools, this is just an xcopy deployment so you just download the entire suite and unzip it to wherever you like on you system.



        For ease of use, you can add the folder where you've copied the tools to the path environment variable. From then on, you can open your favorite command line shell and run any tool Sysinternals provides.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Jan 6 at 10:18









        Lieven KeersmaekersLieven Keersmaekers

        854616




        854616






















            Scott Anderson is a new contributor. Be nice, and check out our Code of Conduct.










            draft saved

            draft discarded


















            Scott Anderson is a new contributor. Be nice, and check out our Code of Conduct.













            Scott Anderson is a new contributor. Be nice, and check out our Code of Conduct.












            Scott Anderson is a new contributor. Be nice, and check out our Code of Conduct.
















            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.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • 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%2f1390356%2fhow-to-install-sysinternals-in-powershell-to-allow-access-through-cli%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

            How to reconfigure Docker Trusted Registry 2.x.x to use CEPH FS mount instead of NFS and other traditional...

            is 'sed' thread safe

            How to make a Squid Proxy server?