Psexec Version 2.20 ((BETTER)) Download
Marissa Albero
I think the newly released Psexec 2.30 has a bug. On Windows 7/10 (but not XP), whenever I now try to run: psexec -i -s cmd.exe to get a SYSTEM command prompt, I see: "No process is on the other end of the pipe." This occurs even if I delete the old psexesvc.exe Psexec 2.20 is fine.
I was finally able to get this (psexec.exe -i -s cmd.exe to work by opening the services app on windows 10 as an admin and stopping the service, PSExeSVC. I then tried this psexec.exe -i -s cmd.exe and it worked. Sorry I could not be more help.
The previous version of pstool 2.45 (with psexec 2.2) can be downloaded from =1&dlcid=WjgzVUUuVFpGLlAsTShTLVY5IihbPEZVSi5PKEgsMyhDLFA8RihQWkYuUFFNKFQxVjs2NUY9JiVaPCIoWwouOjNVRC1QJEMtMzBELDM0Si5KR2AKYAo%3D
Help documentation is the most important thing for getting started with any tool. If you run the psexec command without any switch, you will see detailed help, including its usage syntax and all the supported switches. The following screenshot shows what the help section looks like.
If you do not see this help page but instead see an error that says 'psexec' is not recognized as an internal or external command, operable program or batch file, it means you did something wrong while setting up the Path environment variable.
pstools from microsoft sysiternals team (psexec in this particular case) are also one option to consider for remote installing software or doing other batch changes to computers. psexec can even copy the executable file to remote computers c: drive and isn't limited to installing msi files (you need to run installer with silent install options though since you can't interact with the installer).
df19127ead