I am facing issues with 2.3 when I use the -h flag. With 2.2 worked fine! Since yesterday update of the package this issue came up...
Is Psexec 2.30 buggy - I cannot use it to get a SYSTEM prompt any more? (2.20 is fine)
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.
5 answers
Sort by: Most helpful
-
-
Eric Huggins 1 Reputation point
2021-01-12T16:34:33.743+00:00 I just had the same problem with 2.3.
Fortunately had a copy of 2.2 handy.
Deleted psexecsvc using powershell and then ran 2.2.
Works find now. -
Paul T 1 Reputation point
2021-01-12T19:42:23.427+00:00 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.
In my post above I was trying to stop the service using PSKill so I am guessing there was an issue with that so I finally had the idea to stop the service by opening the services app as admin and stopping it. Yeah, should have done that from the beginning..
-
Alex Mihaiuc 716 Reputation points
2021-01-13T11:29:41.337+00:00 For interactive sessions the -i flag (with no session number) is now necessary.
-
Vafin, Sergei 1 Reputation point
2021-01-13T14:49:23.04+00:00 I got "access denied error" with the version 2.30. With the version 2.2 it worked fine.
The previous version of pstool 2.45 (with psexec 2.2) can be downloaded from https://www.computerbild.de/?dl=1&dlcid=WjgzVUUuVFpGLlAsTShTLVY5IihbPEZVSi5PKEgsMyhDLFA8RihQWkYuUFFNKFQxVjs2NUY9JiVaPCIoWwouOjNVRC1QJEMtMzBELDM0Si5KR2AKYAo%3D